VM’s are scheduled to be backed up, but there is no savepoint in the repository and there is no failed messages in the failed tasks.
The backup is failing very early in the backup process, at this stage of the process there is no mechanism to report to the failed task view of vRanger at the individual job / vm
The stage that the backup would needs to fail between when the job starts to run , but before the task is run.
An example would be if a vm gets registered, its UUID would change,
The job would start but fail to create the task to backup the vm, because it cannot find the vm.
There is no resolution, there is an open defect with development.
Workaround, advise the customer to run a nightly jobs report so that they can double check for failed tasks / vm not being backed up.
A typical Job log of a Job experiencing this issue would show a Task failed to be created.
Note; in the example below, there is 16 tasks ( vm’s to be backed up).
[2012-06-18 20:00:47.081]: Backup task 9532c3aa-bbf2-4248-892a-19896e82a404 for virtual machine GBKGFS01-4224a0a3-5a09-8f4f-53fc-5165c850d58f was created.
[2012-06-18 20:00:47.097]: Backup task 9532c3aa-bbf2-4248-892a-19896e82a404 for virtual machine GBKGFS01-4224a0a3-5a09-8f4f-53fc-5165c850d58f was queued.
[2012-06-18 20:00:47.097]: 'GBKGWC01' failed to have task created for backup.
[2012-06-18 20:00:47.113]: No inventory node of type 'Vizioncore.vRanger.Facade.DTO.InventoryNodeDTO' could be found by identifier 'vm-93'!
[2012-06-18 20:00:47.113]: Completed retrieving virtual machines and creating their tasks.
[2012-06-18 20:00:47.113]: Total tasks created: 15
[2012-06-18 20:00:47.128]: Backup job completed but failed to create 1 task(s).
