HP VME: Why can't you cascade jobs?

[MBR7609]

I am a VMware shop moving to VME. The one feature I loved about Veeam was the ability to have a job start "after X job finishes". Why is that option not available for the VME plugin? I have also noticed that there is not an option to add a secondary target for the jobs created with the VME plugin.

[cody.ault]

Hey Matt,

The limitation with the "run after" is across all of the plug-in managed hypervisor integrations. The VMware backup jobs use a scheduler service that's managed by VBR itself, where as the plug-in managed backup jobs are scheduled by the plug-in itself. There's been issues in the past with the run-after feature with VMware jobs that can cause daisy chained jobs to never run if one of the jobs in the middle doesn't finish and it was decided not to implement the logic into the plugin schedulers. It's more reliable to have jobs run on a schedule. Jobs that are scheduled earlier than other jobs should have priority in the queue for resources (workers/repository tasks).

Regarding the option to manage backup copy jobs (secondary destination) through the backup job, I believe we are looking to add this eventually. You can still create backup copy jobs for these jobs: Backup Copy Jobs, just in a separate wizard.

[MBR7609]

If there are no available workers for the job when the job is scheduled will it queue up or just fail the job?