Validation Process for VMware VMs

During validation, Commvault mounts a VM from backup, starts the VM, and then executes a script if applications are discovered on the VM.

The following scripts are included on access nodes:

  • SQL Server on Windows: C:\Program Files\Commvault\ContentStore\Base\CVGetSqlServerStatus.bat.

  • Oracle on Windows: C:\Program Files\Commvault\ContentStore\Base\CVGetOracleDBStatus.bat

  • Oracle on Linux: /opt/commvault/Base/

Validation Process

  1. During backups and backup copies, discover the applications that are running on the guest VMs.

    For Oracle, the list of instances that to start on boot are fetched. For a Linux server, instances are fetched from the oratab file. For Windows servers, instances are fetched from the Oracle services details.

  2. When validating a backup, live mount the VMs that are included in the backup, either using the ESX host for the source VM or a recovery target, depending on the options that were specified for validation.

    When validating a backup from a Snapshot copy, the hardware snapshot will be mounted on the ESXi host and the selected VMs will be registered for validation.

    The following recovery target options are NOT honored during the validation process.

    • VM display name

    • VM storage policy

    • Datastore

    • Resource pool

    • VM folder

    • Destination network

    Only the below options are honored during validation for the VM:

    • Destination hypervisor

    • Destination host


      When validating a backup from the primary copy and snap job is not moved from snap primary copy to primary copy, backup validation from the primary source will not pick the most recent job. Instead, it will pick the last successful job from the primary copy.

  3. Start the live mounted VM.

    If no applications were discovered for the VM, the validation process validates the VM state. The validation checks the VMware tool's status on the live mounted VM and waits for the tools to be in the running state.

  4. If applications are discovered, execute a script to validate the applications.

    For example, the SQL Server script logs on, verifies that services are running, and executes SQL queries to enumerate the databases.

    Oracle instances are validated to verify that they are in the correct state (Open Mode or ReadWrite state). If instances are not in the correct state, the script attempts to bring the databases to OPEN MODE.

    If the application validation is successful, the script return code is 0. In addition, the VM group page and the backup job indicate whether validation was successful.

  5. After validation is complete, one of the following actions occurs:

    • If you mounted VMs to a recovery target and selected Keep the validated virtual machines running, the VMs are retained using the network options that were specified for the recovery target.

    • If you did not select Keep the validated virtual machines running, the live mounted VMs are disconnected and then deleted.

Monitoring Validation Status for VMware VMs