Verifying that the configuration backs up data that can be restored

Before you can restore individual MicrosoftSQL Server databases from a Data Protection for VMware virtual machine backup, you must complete at least one successful virtual machine backup. For the restore operation to work, the backup must contain Microsoft SQL Server database metadata.

Procedure

  1. Issue the following backup-archive client query command on one of the data mover nodes:
    dsmc query vm vmname -detail -asnode=datacenter_node
    where:
    • vmname specifies the name of the virtual machine
    • datacenter_node specifies the name of the datacenter node
    .
  2. In the command output, look for the following details:
    Application(s) protected: MS SQL 2008 (database-level recovery) 
    Ensure that Excluded is not indicated in any Virtual Machine Disk (VMDK) status fields for virtual disks that host Microsoft SQL Server database files. The Excluded status indicates that one or more of the VMDKs that are required to recover a Microsoft SQL Server database are not being protected. For example:
    Query Virtual Machine for Full VM backup
    # Backup Date 	Mgmt Class  Size 	  Type    A/I   Virtual Machine
    - ----------- 	----------  ----- 	----    ---   -----------------
    1 02/20/2014 		STANDARD 	 43.94GB IFFULL  A     vm_sql10
      12:43:59 	
    
    	Size of this incremental backup: n/a
    	Number of incremental backups since last full: 0
    Amount of extra data: 0
    TSM object fragmentation: 0
    Backup is represented by: 328 TSM objects
    Application protection type: TSM VSS
    Application(s) protected: MS SQL 2008 (database-level recovery)
    VMDK[1]Label: Hard Disk 1
    VMDK[1]Name: [ess800_dev2] vm_sql10/vm_sql10 .vmdk
    VMDK[1]Status: Protected
    …
    VMDK[6]Label: Hard Disk 6
    VMDK[6]Name: [ess800_dev2] vm_sql10/vm_sql10_5.vmdk
    VMDK[6]Status: Protected