The volumes in Virtual machine disks (VMDKs) must contain the Microsoft SQL
Server databases that are not excluded from
the Data Protection for VMware backup processing.
About this task
The databases cannot be on physical compatibility mode raw device mapping (RDM) disks,
independent disks, or on disks that are attached directly to the guest through iSCSI.
Procedure
- Ensure that any EXCLUDE.VMDISK statements in the Data Protection for VMware data mover that is used to back up the virtual
machine do not inadvertently exclude VMDKs that are hosting volumes that contain Microsoft SQL
Server files, file space, database, and
mailboxes.
For example:
- vm_sql10.vmdk contains logical volume C:
- vm_sql10.vmdk contains logical volumes E: and F:
- The label for vm_sql10_1.vmdk is Hard Disk 1.
- The label for vm_sql10_2.vmdk is Hard Disk 2.
- The Microsoft SQL
Server database files to
be backed up are on the E: and F: drive.
- Verify that no statements exclude vm_exc10_2.vmdk from the virtual machine
backup by ensuring that the data mover does not contain the following or similar statements:
EXCLUDE.VMDISK VM_SQL10 "Hard Disk 2"
EXCLUDE.VMDISK * "Hard Disk 2"
Alternatively, if you exclude most hard disks, you must explicitly include the virtual machine
disks by using one of the following
statements:
INCLUDE.VMDISK VM_SQL10 "Hard Disk 2"
INCLUDE.VMDISK * "Hard Disk 2"
Include and exclude statements are processed from bottom to top as they are displayed in the
dsm.opt file. To achieve the goal, enter the statements in the correct
order.
You can specify the exclusion and inclusion of a virtual machine disk from the command-line
interface:
dsmc backup vm "VM_SQL10:-vmdisk=Hard Disk 2" -asnode=datacenter10