Orphaned VMs

In this article

    This report discovers VMs that are present in existing backup files, but are missing in backup, replication or backup to tape jobs. The report examines the content of backups on disk and tape and compares this data to the configuration properties of scheduled jobs, listing VMs that are not included in the jobs.

    • The Summary section includes the VMs without Backup Jobs chart that shows the number of VMs that are not included in jobs.
    • The Details table provides information on orphaned VMs, including protection type, the number of restore points, backup location, the date of the last backup session and the date when the backup will be deleted according to the current file retention policy.

    Report Parameters

    You can specify the following report parameters:

    • Scope: defines a list of Veeam Backup & Replication servers to include in the report.
    • Protection type: defines a job type to include in the report (Backup, Replication, Archive, All).
    • Group by: defines whether data in the report output will be grouped by (Type of protection, Backup target).

    Orphaned VMs Report

    Use Case

    A VM may become orphaned due to an error or oversight, job misconfiguration or a lack of coordination between several backup administrators, for example, when someone changed the configuration of the job and by mistake forgot to include the VM in that job. A VM may also become orphaned due to some automatic procedures, for example, when the VM migrated to an unprotected host through vMotion or as a result of DRS activating.

    This report helps decide whether to modify the backup job settings for the VM if it is a mission critical one, or to delete the VM from the backup if it is no longer necessary.