Administrator Guide

SQL Server VM recovery
To recover a SQL Server VM:
1 Log on to the Console VM.
2 Start Failover Cluster Manager, and then connect to the SQL Server cluster < Prex >SQLCL.
3 Evict the node that you want to recover, for example < Prex >SQL02. To do this, under the cluster name, click Nodes. Right-click the
node that you want to evict, point to
More Actions, and then click Evict.
4 Under Nodes, verify that the server you evicted is no longer listed.
5 Use the steps in Recovering a VM to its original location to recover the SQL Server VM.
6 From the VMM console, start the SQL Server VM.
7 Validate that all nodes in the SQL Server cluster (< Prex >SQL01 and SQL02) are up and running.
8 If the node is not attached to the cluster, then add the node to the SQL Server cluster.
9 Detect and repair any data consistency issues by following the required steps in How to use data consistency runbooks.
Recovering a tenant VM
By default, all tenant VMs that are deployed as VM roles are deployed with a single parent VHD, and therefore use a dierencing disk.
DPM’s original location recovery work ow (described in Recovering a VM to its original location) will not work for tenant VMs that use a
dierencing disk.
NOTE
: You must perform the procedures in this section as a member of the < Prex >-Diag-Admins group.
Determine whether the VM uses a dierencing disk
To recover a tenant VM, you must rst check whether the VM has a shared parent VHD conguration.
1 On a Console VM, open Windows PowerShell ISE.
2 Run the following script. Update the value of VM_Name with the name of the VM that you want to recover.
vmname = "VM_Name"
$VHDMap = @{}
$VmsWithParentVHDs = @{}
$vms = Get-SCVirtualMachine
foreach($VM in $vms)
{
foreach($vhd in $vm.VirtualHardDisks)
{
if($vhd.ParentDisk -ne $null)
{
if($VHDMap[$vhd.ParentDisk.ID] -ne $null)
{
$VHDMap[$vhd.ParentDisk.ID] += "," + $vm.Name
Operations
77