Sometimes two great product can annoy each other in this case Data Protection Manager and Hyper-V Replica.
After enabling Hyper-V replica we saw a spike in replica volume around 8pm , and that happened to be the same time we do system protection backup with Data Protection Manager.
And on each guest we have the WindowsImageBackup that is being generated each time the systemstate backup is run, this is “only” on servers that have the agent installed , the servers where we “only” do VM backup this issue does not occur
On the VM’s create a new vhdx and assign a standard drive we use R: on our images
On the VM’s edit psdatasourceconfig.xml
and edit the FilesToProtect to R:\WindowsImageBackup\*
and while you are at it move the swap file to the R: also
And on the Hyper-V Replica settings verify that the new file is excluded from replication.
And we try to name the drive so people know not to keep their xmas shopping list on the drive
So its time to check why the images deployed didn’t have the drive assigned in the template and to edit the orchestrator job that edit the psdatasourceconfig.xml to change to the new assigned drive.