Hello all.
We have some (10 or so VM individual jobs) forward Incremental will synthetics @ 7 days and 14 restore points.
These jobs are chained together/dependent on the first scheduled job.
We are adding a single backup copy job which contains all of the VM Backups above.
Question - If I don't specify a time window, or start time (i.e. the defaults) when will the backup copy job start? Will it wait for all of the Backup jobs to complete, or...?
Thank you
-
- Enthusiast
- Posts: 91
- Liked: never
- Joined: Aug 04, 2010 12:34 am
- Contact:
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: VBUR 9.4 u4 - Backup and Backup Copy concurrency?
Hello,
it will start transferring data as soon as new data is available.
Best regards,
Hannes
PS: job chaining is not recommended because if one job in the chain fails, all the other jobs will also fail. If you set one job to 10pm and the next to 10:01pm then it will run in exactly that order or in parallel if enough resources are available.
it will start transferring data as soon as new data is available.
Best regards,
Hannes
PS: job chaining is not recommended because if one job in the chain fails, all the other jobs will also fail. If you set one job to 10pm and the next to 10:01pm then it will run in exactly that order or in parallel if enough resources are available.
-
- Enthusiast
- Posts: 91
- Liked: never
- Joined: Aug 04, 2010 12:34 am
- Contact:
Re: VBUR 9.4 u4 - Backup and Backup Copy concurrency?
Thank you.
In previous versions of VEEAM (if memory serves) we didn't want to have VM's backing up via a single backup job as the storage file size would get too big and possibly cause issues. Granted - way back in previous version(s).
What is the recommended process these days? Still to keep the VM's independent with their own BU(R) job? or all in one job?
In previous versions of VEEAM (if memory serves) we didn't want to have VM's backing up via a single backup job as the storage file size would get too big and possibly cause issues. Granted - way back in previous version(s).
What is the recommended process these days? Still to keep the VM's independent with their own BU(R) job? or all in one job?
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: VBUR 9.4 u4 - Backup and Backup Copy concurrency?
Hello,
as we have "per-VM" backup chains since some years, there are the following recommendations for "classic" and "per-VM" chains
Best regards,
Hannes
as we have "per-VM" backup chains since some years, there are the following recommendations for "classic" and "per-VM" chains
from best practice guideFor per job backup files: 30 VMs per job
For per VM backup files: 300 VMs per job
Best regards,
Hannes
Who is online
Users browsing this forum: No registered users and 52 guests