Verification that the configuration backs up data that is viable for restore

Before you can restore individual Microsoft Exchange Server databases from a Data Protection for VMware virtual machine backup, you complete at least one successful virtual machine backup. For the restore to work, the backup needs to contain the necessary Microsoft Exchange Server database metadata. You can verify that the backup includes the correct information.

Enter the following backup-archive client query command on one of the data mover nodes:

dsmc query vm vmname -detail -asnode=datacenter_node

In the command output, look for the following details:

Application(s) protected: MS Exchange 2013 (database-level recovery)

Ensure that there are no VMDK status fields for virtual disks that host Microsoft Exchange Server database files that indicate Excluded. The Excluded status indicates that one or more of the VMDKs that is needed to recover a Microsoft Exchange Server database are not being protected. Sample:

Query Virtual Machine for Full VM backup
# Backup Date 	Mgmt Class  Size 	  Type    A/I   Virtual Machine
- ----------- 	----------  ----- 	----    ---   -----------------
1 02/20/2015 		STANDARD 	 43.94GB IFFULL  A     vm_exc10
  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 EXC 2013 (database-level recovery)
VMDK[1]Label: Hard Disk 1
VMDK[1]Name: [ess800_dev2] vm_exc10/vm_exc10 .vmdk
VMDK[1]Status: Protected
…
VMDK[6]Label: Hard Disk 6
VMDK[6]Name: [ess800_dev2] vm_exc10/vm_exc10_5.vmdk
VMDK[6]Status: Protected