Comprehensive data protection for all workloads
Post Reply
tinto1970
Expert
Posts: 109
Liked: 32 times
Joined: Sep 26, 2013 8:40 am
Full Name: Alessandro T.
Location: Bologna, Italy
Contact:

Nice to have function (IMHO)

Post by tinto1970 »

Good day all,

i've been facing this issue a few times when backing up a pool of VMs which belong to a cluster or are Active Directory Domain controller and so on:

i understood it was 'safer' to save these machines not at the same time to avoid that the (brief) stun time at snapshot removal happens at the same time for all the machines, causing a downtime of the service or other problems.

I've workarounded this saving the VMs in two different jobs, or forcing a job to use the same proxy to reduce the chance of a simultaneous snapshot commit.

I'd love to have a switch "process VMs sequentially" in job settings :)
Alessandro aka Tinto | VMCE 2024 | Veeam Legend | VCP-DCV 2023 | VVSPHT2023 | vExpert 2024
blog.tinivelli.com
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Nice to have function (IMHO)

Post by PTide » 1 person likes this post

Hi,

In case all VMs have a single vmdk, a possible workaround will be to limit the amount of slots on the proxy that is used for the backup job to 1 slot thus forcing the job to process VMs one by one.

Thank you
Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 306 guests