VSS Validation Limitation

When you validate a volume collection, the array verifies that the application and volumes associated with the volume collection are present on the specified application server, and that communication between the array and the application server is functioning properly.

VSS synchronization Validate button does not test for application data on the volumes. As a result, VSS protection set validation passes even when application data/logs are missing from those volumes.

The VSS synchronization Validate button tests three items:
  1. Communication to the Windows host.
  2. The application selected in the volume collection (SQL Server or Exchange) matches a VSS writer on the Windows host.
  3. The volumes in the volume collection are mounted and have an active connection on the Windows host.

By design, the Validate button does not test that the volumes have actual application data or logs on them as required for a successful VSS snapshot.

Click the Validate button to confirm communication and mounted volumes, as mentioned in Description. But do not rely upon it to verify application data/logs on the volumes. Note that the validation does not verify the presence of Exchange DAG nor does it verify the number of database copies.

If the synchronization selection is Microsoft VSS and the application is defined as "MS Exchange Server 2010 or later w/DAG," and Verify backups is set to Yes, you have the option to Skip consistency check for database files. Enable this option only if each database being backed up has at least two good copies in the DAG.

NOTE: There is no way to skip verification of log files.