I have a main backup job that backs up all our VMs - active full once a week, incrementals the other days.
I want to start experimenting with forever forward for one of the VMs. If I create a new job and add one VM to it, will that affect the main job in any way? Eg if the new job does a full backup of one VM, will the main job decide to skip its weekly full and do an incremental instead? Or are separate jobs completely independent, even if they contain the same VMs?
-
- Veteran
- Posts: 254
- Liked: 14 times
- Joined: Nov 23, 2015 10:56 pm
- Full Name: Peter Shute
- Contact:
-
- Product Manager
- Posts: 2584
- Liked: 710 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Making second backup of a VM
Greetings!
Jobs will be completely independent. That is, different source/target settings, schedule, retention, guest processing and so on.
Please note, that if application-aware backup is used, both jobs will act according to the Guest Processing tab settings, so for example, both jobs might try to truncate/backup SQL transaction logs, which is not the best idea to overlap. Be aware of it.
/Cheers!
Jobs will be completely independent. That is, different source/target settings, schedule, retention, guest processing and so on.
Please note, that if application-aware backup is used, both jobs will act according to the Guest Processing tab settings, so for example, both jobs might try to truncate/backup SQL transaction logs, which is not the best idea to overlap. Be aware of it.
/Cheers!
Who is online
Users browsing this forum: No registered users and 30 guests