Troubleshooting VMware backups and restores of SQL Server
Note the following when you perform a VMware backup that protects an application:
One Application State Capture job is created per VM, regardless of which applications are selected in policy.
The ASC job can fail if the VMware disk layout has changed since the last discovery. In this situation, you must force NetBackup to rediscover virtual machines by lowering the value of the option. See the NetBackup for VMware Administrator's Guide.
If the ASC job fails, the VMware snapshot or backup continues. Application-specific data cannot be restored.
When you query the SQL Server Management Studio (SSMS), it may show that the database was backed up. In this case, though the database was skipped, the snapshot was still successful.
Failure results in the discovery job or parent job exiting with status 1.
ASC messages are filtered to the ASC job details.
If you enable recovery for a particular application but that application does not exist on the VM, the ASC job returns Status 0.
Details on the ASC job can be found in the Activity monitor job details.
If neither the Veritas VSS provider nor the VMware VSS Provider is installed at the time of backup, the SQL Server databases are not quiesced. In this case, the recovery of a SQL Server database after it is restored may require manual steps.
bpfis is executed and simulates a VSS snapshot backup. This simulation is required to gain logical information of the application.