Monitor protected systems with the Boot VM Report - x360Recover

Written By Heather Hootman ()

Updated at July 15th, 2021

The Boot VM Report provides a visual quick reference to the status of the latest Boot VM test for all Protected Systems managed by the Global Management Portal. With the details in this report, you can quickly verify that all Protected Systems are bootable.


To properly utilize the Boot VM Report, the Boot VM Check feature must be enabled for each individual Managed System (Appliance and Vault).

If the Boot VM Check feature is not enabled for a Managed System, the image column will display as NA.

Within the Boot VM Report, the AutoVerify column displays results of the AutoVerify check, which alerts you of possible issues with Protected Systems before they fail. With this advanced notification, you can ensure you have valid backups and the resources necessary to repair potentially bad data on the source system.

To view the Boot VM Report:

  1. In the GMP, click the Boot VM Report tab. The Boot VM page displays.
  2. Use the columns to view the details of each Protected System boot process:
    1. The Customer column identifies the Customer to whom the Protected System is registered.
    2. The Location column identifies the geographic location of the Protected System.
    3. The PS Name identifies the device name.
    4. The Device Type section displays the type of device that is protecting the Protected System.
    5. The IP Address column lists the IP address of the Protected System.
    6. The Snapshot Time column displays the time of the latest Snapshot.
  3. The AutoVerify column displays the results of the chkdsk test and the heartbeat test. chkdsk confirms the integrity of the file system. If chkdsk fails, a full backup of the Protected System might be triggered (if one has not already been performed recently) in an attempt to self-heal the failure. Heartbeat confirms that the system was able to fully boot the operating system, start services, and accept commands to perform additional testing (for example, chkdsk.)
  4. The Screenshot column displays the captured image of the boot process to help you ensure the Protected System image was able to boot properly.


Full scans generated by AutoVerify will occur no more than once every 30 days.

chkdsk may fail due to the following conditions:

  • Corrupted or incomplete backup snapshot on the BDR Appliance. (A new full backup will likely resolve the issue.)
  • File system corruption on the source-protected system disk(s) (chkdsk should be run on the protected system and then a new full backup taken to fix this problem).

If chkdsk exits with error codes that indicate possible data consistency issues, the Appliance will attempt to resolve the issue by performing a new full scan of the Protected System and an alert is generated on the Appliance. Alerts generated by AutoVerify are automatically closed after the full scan completes.