With this information only being in the summary it is gone by the time the next job has run.15/08/2017 10:13:50 :: ViewComposer is no longer processed by this job. Make sure this change is intentional.
15/08/2017 10:13:50 :: ViewConnectEXT is no longer processed by this job. Make sure this change is intentional.
15/08/2017 10:13:50 :: ViewConnectINT is no longer processed by this job. Make sure this change is intentional.
Here is an example where machines have dissapeared from the job in between runs, I know this is an operational mess up I'm tring to recover from but If I could search the job report for "is no longer processed by this job" it would make it easier to recover from.
Backup job: RPO-Weekly-FileServer
weekly backup of the FileServer Storage Servers
Warning
0 of 0 VMs processed
02 July 2017 14:00:10
Success0Start time14:00:10Total size0.0 BBackup size24.4 GBNothing to process. All VMs were excluded from task list.
Warning0End time14:00:41Data read0.0 BDedupe2.1x
Error0Duration0:00:31Transferred0.0 BCompression1.6x
Details
NameStatusStart timeEnd timeSizeReadTransferredDurationDetails
Backup job: RPO-Weekly-FileServer
weekly backup of the FileServer Storage Servers
Warning
2 of 2 VMs processed
25 June 2017 14:00:22
Success0Start time14:00:22Total size80.0 GBBackup size29.4 GB
Warning2End time14:08:11Data read8.2 GBDedupe1.7x
Error0Duration0:07:49Transferred4.9 GBCompression1.6x
Details
NameStatusStart timeEnd timeSizeReadTransferredDurationDetails
FileServerSS01Warning14:00:4814:04:4840.0 GB4.3 GB2.5 GB0:04:00Production datastore FileServersan01 is getting low on free space (227.5 GB left), and may run out of free disk space completely due to open snapshots.
FileServerSS02Warning14:00:4814:03:4840.0 GB3.9 GB2.5 GB0:03:00Production datastore FileServersan02 is getting low on free space (220.5 GB left), and may run out of free disk space completely due to open snapshots.