Veeam Backup & Replication very slow to start backup
Hi, I am testing Backup and Replication Community Edition and have a very simple test environment consisting of a single Windows Server 2022 with one boot SSD, two HDD’s and a third HDD which is my dedicated Backup Repository. When I start the job, it take over an hour before it will begin to process/transfer data. Is this normal or is stuck waiting for something before it can start the backup? The server really has no load on it as it is a test machine (physical, not virtual). Below is a screenshot:
Any thoughts would be much appreciated. Thank you!
Page 1 / 1
It is normal if you have a snapshot on a VM you're backing up. Since you have a physical server you're backing up... I can't think of anything off hand as to why it's taking so long to "process" before performing the backup
If you click on the “S2” server in the bottom left column of the statistics it will give you a breakdown of what it’s doing if you can click that and supply a screenshot please
Good catch Michael!
Thanks for the quick response. When I click on S2, it looks like the hour was spent “creating VSS snapshot.” However, what is interesting is during that time, when I looked at Performance Monitor, there was no disk access. It’s running and copying data now…
Hello @Hammer
make sure you applied the exclusion list for antivirus
This is a good catch also for AV that can slow things too.
Thanks for the quick response. When I click on S2, it looks like the hour was spent “creating VSS snapshot.” However, what is interesting is during that time, when I looked at Performance Monitor, there was no disk access. It’s running and copying data now…
Okay I’d suggest going to c:\programdata\Veeam on the S2 server and finding the logs for the backup job (should be a sub folder within backup with the job name if memory serves correctly). And you can see if Veeam is waiting for VSS responses from the OS or if Veeam is hanging on something else
Hi, thanks again for your help. Here is the section of the log file that show where things got “stuck.”
d29.11.2023 12:45:54.426] <08> Info CRL] Cleanup Before: 255, After: 14]
It seems to be doing nothing for close to two hours, but I don’t know what Destroying RPC means…
Below is a bigger section of the log.
thank you again…
RPC = remote procedure call. I’d check the windows event log for any errors. I’d also suggest trying a backup without application aware processing and see if that works
Hi, I appreciate everyone’s help on this issue. I looked in the logs but didn’t see anything that jumped to me. However, what seems to have solved the issue was reformatting one of the HDD’s I was backing up. Now, my VSS Snapshot time is down to 8 minutes…much better than the prior 1.5 hours. Anyways, I hope that was the issue and thank you again.
