I have an agent job that I've created a "File Level" but added the volumes so I can later exclude folders I don't want backed up.
As you can see from the topic its taking too long to remove these folders/files from the VSS snap. Is there a way to adjust VSS timeouts?
Ive read a Veeam KB that simply says remove the folders if its causing this condition, in this case I can't. I could just backup the one folder but thats probably slower than a volume backup.
Hello,
hmm, that case is from 2016... could you please check again? What does support say?
I know that there are limitations in VSS which are pretty unpredictable. It depends on the amount of files in the folder you exclude + patch level + load + don't remember.
How many files do you have in the two folders? I remember that we tested something around 500k files "relatively stable"
Support wants me to adjust a registry key, he says the default timeout is 15 mins. This job is creating snapshot for an hour then throws this error message. Makes me think that the adjustment in the registry below might not work. You can see in the screenshot 15 mins is not the case, the VSS Snapshot creation is running for about an hour. This process to my understanding also deletes the files after the snapshot is created as to exclude those folders.
If the backup still fails with a timeout error, the VSS wait timeout can be extended on the Veeam Backup & Replication server.
>
> 1). Go to registry key HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Backup and Replication
>
> 2). Add a DWORD (32-bit) value named VssPreparationTimeout. The value is in milliseconds (decimal), the default timeout is 900000, which equals 15 minutes. Set the value to 1800000. This will change the timeout to 30 minutes.
>
> 3). Stop any running jobs or wait for them to complete, then restart the Veeam Backup Service.
>
Hello,
well, it does not hurt to try the support suggestion.
But I guess that it will not solve the problem. It looks exactly the same like the VSS limitation I was talking about earlier. Chances are high, that there is no workaround from Veeam side.