trying to set this up, but however i tr yto configure the tape job it always starts as expected but changes to pending status with the messageIf the source job creates per-VM backups, the tape job gets priority for each per-VM restore point separately.
In this case, the source job will be able to lock other per-VM restore points and perform the needed
cant change much on the backup job itself besides selecting per vm backup. this definitely works as i get backup files for every vm individually as expected.No backup files found
Some backup files are locked by running jobs, retry is required
but i would have expected the tape jobs starts up and as soon as the first vms are processed and their backup files are created and begins to copy them to tape. instead the tape job seems to wait until the backup job is finished before starting to write files to tape?
tried to setup the tape job having the backup job as source and also having the repository as source! also tried using scheduling the tape job at a fixed time 5 minutes after backup jobs starts and also tried to schedule the tape job as new backup files appear.
no change, always same behaviour: tape job just waits ...
what am i doing wrong here? or do i missunderstand per vm backup to tape functionality?
looks like the backup job is locking ALL backup files also already finished vms backup files instead of locking just backup files of currently written vm backups?