-
- Novice
- Posts: 6
- Liked: never
- Joined: Mar 29, 2020 6:24 am
- Full Name: M.Y.
- Contact:
Alternative to job chaining
We have several backup jobs based on retention, target repository (local vs remote) that used to work based on job chaining when we were using VMware. Now that we've moved to Proxmox, job chaining is no longer supported. What's the best way to ensure that when running backup jobs, they don't run simultaneously causing a conflict (the disk is blocked by another backup job)?
-
- Product Manager
- Posts: 10953
- Liked: 3001 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Alternative to job chaining
Hi M.Y.,
May I ask why you need to use different backup jobs?
Typically, customers use a single backup job per virtual machine and utilize Backup Copy Jobs for different retention requirements.
This ensures that only one job processes your virtual machines.
Best regards,
Fabian
May I ask why you need to use different backup jobs?
Typically, customers use a single backup job per virtual machine and utilize Backup Copy Jobs for different retention requirements.
This ensures that only one job processes your virtual machines.
Best regards,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 10 guests