Troubleshooting the status for a newly discovered VM

The following table describes a problem that may occur when you review the status of a newly discovered VM under Virtual machines.

Table: Errors encountered when you review Status for a newly discovered VM

Error message or cause	Explanation and recommended action
The protection status of a VM indicates that it has not been backed up. However, a backup job that includes the VM has successfully completed.	In the NetBackup web UI, the protection status for a newly discovered VM does not indicate that it is backed up until the next backup of the VM has completed. In some circumstances, a new VM is backed up before the discovery of that VM has happened, as in the following scenario: By default, autodiscovery occurs every 8 hours. A new VM is added to the environment. A backup job completes successfully before discovery completes. For example, a backup job that uses existing policies where the new VM is included as part of the backup selection criteria. Later, discovery completes. However, in the NetBackup web UI, the protection status of the VM indicates that it has not been backed up. If you encounter a similar situation, you can still browse the recovery points and recover them. However, it is only after another backup of the VM successfully completes that the protection status indicates that the VM has been backed up. To review the protection status of a newly discovered VM in the NetBackup web UI, Cohesity recommends that you wait until the next successful backup has completed. Then, the protection status of the VM should correctly indicate its protection status.

Error message or cause

Explanation and recommended action

The protection status of a VM indicates that it has not been backed up. However, a backup job that includes the VM has successfully completed.

In the NetBackup web UI, the protection status for a newly discovered VM does not indicate that it is backed up until the next backup of the VM has completed.

In some circumstances, a new VM is backed up before the discovery of that VM has happened, as in the following scenario:

By default, autodiscovery occurs every 8 hours.
A new VM is added to the environment.
A backup job completes successfully before discovery completes. For example, a backup job that uses existing policies where the new VM is included as part of the backup selection criteria.
Later, discovery completes. However, in the NetBackup web UI, the protection status of the VM indicates that it has not been backed up.

If you encounter a similar situation, you can still browse the recovery points and recover them. However, it is only after another backup of the VM successfully completes that the protection status indicates that the VM has been backed up.

To review the protection status of a newly discovered VM in the NetBackup web UI, Cohesity recommends that you wait until the next successful backup has completed. Then, the protection status of the VM should correctly indicate its protection status.

Troubleshooting the status for a newly discovered VM

Feedback

Feedback