Looking to get a bit more info on potential issues / limitations around concurrent jobs that touch a single set of VMs. Specifically, around the following use cases:
1. Scheduling a Backup job and a VM copy job for the same VM at the same time.
2. Scheduling a backup job in one Veeam instance and a VM copy job in another for the same VM.
3. Scheduling a backup job in 2 separate Veeam instances for the same VM at the same time (I realize this probably isnt recommended, but curious of any technical limitations in doing so).
Thanks!
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Nov 28, 2011 5:18 pm
- Full Name: Tim Graffam
- Contact:
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: Concurrent jobs for same VM/s
Hi Tim,
Please keep in mind Veeam B&R has a priority between jobs: Restore jobs > Backup Jobs > Backup Copy Jobs\Secondary Jobs.
1. The backup job has a higher priority, so the VM copy job will be executed after completion.
2,3. Separate Veeam instances know nothing about each other activities, so you should get an error in the both examples, since the VM will be locked in by one of the jobs. Thanks!
Please keep in mind Veeam B&R has a priority between jobs: Restore jobs > Backup Jobs > Backup Copy Jobs\Secondary Jobs.
1. The backup job has a higher priority, so the VM copy job will be executed after completion.
2,3. Separate Veeam instances know nothing about each other activities, so you should get an error in the both examples, since the VM will be locked in by one of the jobs. Thanks!
Who is online
Users browsing this forum: alxz89, Google [Bot], Semrush [Bot] and 113 guests