Hi,
I have the following issue from about September or longer...
In the infrastructure I have one standalone Hyper-V host with couple of VMs hosted via ISCSI and Veeam B&R 9.0 to perform backups of such VMs. At September I noticed that when Veeam create backup for VMs in the Backup Job the process of creating VSS snapshot
(with crash consistent mode - the most basic mode for backup) takes much of time. Firstly it was 1:44min, I didn't changed anything and let veeam perform the backups normaly. After a couple of days I noticed that this VSS snapshot creation process takes
2:41min, again after a couple of days it was 5 minutes, only for creating the VSS snapshot. Normaly I remember that creating VSS Snapshot took not more than 40 or 50 seconds. I started to debug this problem, because the 80% of backup time is only for creating
(now it is 5 minutes) and closing (the same value about 5 minutes) snapshot... I checked that VSS snapshot is created after Veeam starts to create it with vssadmin list shadows command. I can see the VSS snapshot when it is created. Additionally I checked
that the storage for VSS snapshot is sufficient with vssadmin list shadowstorage command - there are no any problems - much of space available, no any old snapshot only this one created by Veeam.
What is more interesting after a few weeks I noticed the same issue on my second infrastrcture where I have one Hyper-V host and Veeam too.
For now I know only one operation which reduces the VSS time to 40 seconds. It is of course reboot the host... But now I have to reboot the hosts every weekend which is not a good idea for me.
I asked Veeam support for such issue, but they don't find any problem and said me that Veeam do nothign that using the native mechanisms of VSS (in a easy words - Veeam only execute the vss commands to create the snapshots. They don't find any interesting in
logs...).
What I can add is that I tested a lot things for example:
- Try to create new Backup Job with test VM - the same result
- Place VM on the local storage of Hyper-V Host (not iscsi storage) - the same result (VSS 5 min)
- Try different distributions of VMs both windows and Linux - the same result...
Do anyone have similiar issue or have idea how to troubleshoot the issue?
Thanks.
Matt.