You can migrate a Microsoft Windows cluster’s business services. PlateSpin Migrate supports single-active-node versions of the following clustering technologies:
Windows 2008 Server-based Microsoft Failover Cluster (Node and Disk Majority and No Majority: Disk Only models)
Windows 2003 Server-based Windows Cluster Server (Single-Quorum Device Cluster model)
NOTE:To migrate Windows clusters, use the PlateSpin Migrate Client.
You can use a Move job to migrate the essential services of a cluster that results in a functional single-node cluster in a virtual machine.
The scope of support for cluster migrations in the current release is subject to the following conditions:
All shared disks belong to the active node.
The source workload of the migration must be the active node—the node that currently owns the quorum resource of the cluster. To discover a cluster, specify the IP address of one of the cluster’s resource groups.
A cluster’s quorum resource must be collocated with the cluster’s resource group (service) being protected.
For a successful X2P or Server Sync operation, target disks must have discrete SCSI controllers to separate the cluster’s shared disks from disks that host system volumes of individual nodes.
To be able to function, the migrated single-cluster virtual machine requires access to a domain controller with the same parameters as the original domain controller. To address this requirement, consider either leaving the original domain controller online or simultaneously migrating it as well.
File based transfer is not supported for protecting Microsoft Windows clusters.
The workflow of migrating a Windows cluster is similar to that of migrating a standalone server:
Discover the active node, specifying the cluster IP address and cluster admin credentials.
In the Servers view, use drag-and-drop to start a migration job, then configure the job’s parameters.
(Conditional: successful migration) If the migration job completes successfully, perform a Server Sync operation on the active node.
NOTE:If the active node in the cluster fails over before you can perform a Server Sync operation, perform a full migration using the new active node, and then perform a Server Sync on this new node.
(Conditional: failover prior to migration) If a cluster failover occurs prior to the completion of file transfer, the migration job aborts. If this happens, refresh the source and retry the migration job.
NOTE:If you select Shut down for the source’s post-migration end state, a shutdown of all source nodes of the cluster results.