The software we use to apply windows updates creates a VM snapshot prior to installation. Having that snapshot on the VMs then cause the backup jobs to fail. I think this is a known issue and we have just disabled the backup jobs for a day or so until we remove the snapshot. Im just verifying that Veeam doesnt like there to be snapshot on the vm and should be avoided when possible or am I doing something wrong. We use storage integration and NOT hot add type backups.
Page 1 / 1
Veeam will work with snapshots but it is not advisable to have snapshots around for long as they can cause more problems in the long run. I think disabling it and once the snapshot is removed to start backups again.
I've not heard of Veeam not being able to backup VMs with snapshots on them. Veeam creates snaps itself to backup. If you do have them on VMs for a time and data grows, it can take a longer than normal time to do data processing/"disk digest" in the initial passes of Job runs. Otherwise, they are ok to have briefly.
The process can be interrupted and will fail in case that your Update solutions tries to delete a snapshot while the Veeam snapshot is still present, I had similar issues in the past.
Try to modify the timings to avoid this scenario helps but I definitely agree with Chris and Share, be careful with snapshots.
Which storage are you using and which protocol Do you use for your datatstores? In case of NFS this is known but works as designed. But Job must not fail for this vms. You can simply configure "failover to standard backup if Backup from storage fails"
Regards matze
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.