Job Chaining

[Gostev]

Glad to see continuous success stories from people who were brave enough to disable chaining

Just to reassure, the chaining as a feature is not going away, but I am thinking of at least adding some nasty warning when this option is selected in the wizard, explaining the recommended way to organize required concurrency.

Great discussion!

[dellock6]

Something like multiple popups:

"Do you really want to enable chaining?" YES/NO
!_____> "Do you really really want to enable chaining?" YES/NO
!___________> "Oh gosh, you want to use it for real... ok, I've warned you"

[veremin]

Something like multiple popups:

"Do you really want to enable chaining?" YES/NO
!_____> "Do you really really want to enable chaining?" YES/NO
!___________> "Oh gosh, you want to use it for real... ok, I've warned you"

Vista style?

[dellock6]

"cancel or allow?" https://www.youtube.com/watch?v=VuqZ8AqmLPY

[lp@albersdruck.de]

"Please enter any 11-digit prime number to continue:"

[zoltank]

- We use the network NBD protocol for our transport since we found we found it to be the most reliable and didn't want to access the SAN directly (only hosts have a physical SAN connection). Because of the slower speed NBD provides, and due to our desire to minimize the time a snapshot is present on a VM, we want to process our VMs one at a time. It's slower overall, but faster for any individual VM.

- We run three separate backup jobs (apps/files/emails) to reduce the size of the backup files and to make it easier to dump them to tape to send offsite.

- We process our application and file servers before our email so the email servers can be backed up during a lower utilization period.

- After doing our nightly backup we run a SureBackup job on everything to make sure our backups are happy.

- We chain our jobs so they run Apps>Files>Emails>SureBackup. This allows us to minimize the amount of time backups are running, ensure only one VM is processed at a time, and verifies our backups.

[Vitaliy S.]

ensure only one VM is processed at a time

Have you considered limiting the concurrent tasks on the proxy/repository server instead of job chaining?

[Gostev]

This allows us to minimize the amount of time backups are running

If you really care to minimize the time, then you should definitely stop using job chaining.

"Please enter any 11-digit prime number to continue:"

99999999977. This one is actually easy to remember, nine 9 and two 7

[lp@albersdruck.de]

If you really care to minimize the time, then you should definitely stop using job chaining.

I can second that. Not using job chaining cut around 1h off our backup duration.

99999999977. This one is actually easy to remember, nine 9 and two 7

You could amend that with "that has not been entered before". Or use "Enter the last digit of pi to continue" and then fail every time