[TUTORIAL] Long Replication-Time caused by Office 2019 and Microsoft VSS

OsvaldoP

Well-Known Member
Mar 30, 2020
193
23
58
45
Hello

Maybe someone can help this too

Problem was that Replication-Time on Windows RDS Hosts with installed Office 2019 took long time. About 5 to 90 minutes each job.
After some investigation i noticed, that the Replication-Log hangs after „freeze guest filesystem“.
Same time on vm, the qemu-ga.exe took about 10-12% CPU usage while looping many times Userprofiles caches (%LOCALAPPDATA%) preferred MS-Office folders.

Code:
start replication job
guest => VM 109, running => 3763041
volumes => zfs01:vm-109-disk-0
freeze guest filesystem

########### Timeout min 5 Minutes ####################

create snapshot '__replicate_109-0_1655835002__' on zfs01:vm-109-disk-0
thaw guest filesystem
…


After some research a found the following post with solved the problem
https://answers.microsoft.com/en-us...ss-error/4917c2ea-e3db-43ca-9d10-c61283f0a93c

Duplicated Entries in “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot\OfficeODC“ causes this behavior
Since cleaning up OfficeODC, my replication-jobs finishes after few seconds.

If you don’t like to cleanup manually use this (quick and dirty)script.

* Backup the current OfficeODC key
* Rename Script OfficeODC.ps1.txt to OfficeODC.ps1, save to location with write-permission.
* Start script “powershell.exe -f OfficeODC.ps1”
* Notepad opens with the optimized OfficeODC String
* Copy this string to Registrykey “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot\OfficeODC“


Also many thanks to Stoiko from Proxmox for support!!
 

Attachments

  • Like
Reactions: Stoiko Ivanov