Hi,
Is there any harm in setting all of my dozen backup jobs to kick off say between 6-7pm. There won't be enough resources for the proxies to hot add so I assume everything will just get queued and dealt to in an orderly fashion. Or is Veeam going to failover to network backup if it can't hotadd disks after 'X' amount of time?
At the moment I've staggered my jobs throughout the night but am wondering if there's any point in staggering them if they'll just automatically queue and wait for resources, then they would finish in the most efficient time possible.
Thanks
-
- Enthusiast
- Posts: 34
- Liked: never
- Joined: Oct 24, 2018 12:51 am
- Full Name: Chris Warner
- Contact:
-
- Product Manager
- Posts: 14836
- Liked: 3083 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Backup job scheduling
Hello,
Yes, job chaining ("run after this job") is not recommended / not effcient.
Best regards
Hannes
correct. if you start job 1,2,3,4... at 6:00, 6:01, 6:02, 6:03... they will be queued in exactly that order and wait until resources are available. The backup mode will not change, because it does not matter whether a task is used for hot-add / nbd / san.just get queued and dealt to in an orderly fashion
Yes, job chaining ("run after this job") is not recommended / not effcient.
Best regards
Hannes
Who is online
Users browsing this forum: jim.lowry and 129 guests