Migration When Both Old and New Clusters Have Multiple Nodes When Settings are Migrated

Applies To: Windows Server 2008

This topic provides an overview and steps that describe how to perform a migration when both the old and new clusters have multiple nodes when the settings are migrated. For information about how to perform an in-place migration, see In-Place Migration for a Two-Node Cluster. For a list of other topics about migrating a failover cluster, including overview and requirements topics, see Migrating Cluster Settings from Windows Server 2003 to Windows Server 2008 Step-by-Step Guide.

Overview of migration when both the old and new clusters have multiple nodes when settings are migrated

For this migration scenario, there are three phases:

• Phase I: Create a two-node failover cluster. For this phase, while the old cluster continues to run, install Windows Server 2008, Failover Clustering, and any needed services, applications, or server roles on at least two servers. Create the networks the servers will use, and connect the storage. Next, run the complete set of cluster validation tests to confirm that the hardware and hardware settings can support a failover cluster. Finally, create the new cluster. At this point, you have two clusters.

  Additional information about connecting the storage: If the new cluster is connected to old storage, make at least one logical unit number (LUN) or disk accessible to the servers, and do not make that LUN or disk accessible to any other servers. (This LUN or disk is necessary for the witness disk, which is similar to, although not the same as, the quorum resource in Windows Server 2003.) If the new cluster is connected to new storage, make as many disks or LUNs accessible to it as you think it will need, and see Cluster Migrations Involving New Storage: Drive Letters and Labels and Cluster Migrations Involving New Storage: Mount Points, earlier in this guide.

  For details about this phase, see Steps for creating a two-node failover cluster.

• Phase II: Determine how you will make any existing data available to the new cluster, and then migrate settings to it. If the new cluster will use old storage, plan how you will make the storage available to it, but leave the old cluster connected to the storage until you are ready to complete the transition. If the new cluster will use new storage, copy the appropriate folders and data to the storage, until you have recreated everything except the drive letters and disk labels that exist on the old storage. Run the Migrate a Cluster Wizard. When the wizard completes, most or all migrated resources will be offline. Leave them offline at this stage.

  For details about this phase, see Steps for migrating settings from a server cluster running Windows Server 2003.

• Phase III: Complete the transition from the old cluster to the new. If the new cluster uses old storage, the first step in the transition is to follow your plan for making LUNs or disks inaccessible to the old cluster and accessible to the new cluster. If the new cluster uses old storage, finish the configuration of drive letters, mount points, and the associated disk resources, as described in Cluster Migrations Involving New Storage: Drive Letters and Labels and Cluster Migrations Involving New Storage: Mount Points. Review some or all of the migrated disk resources to confirm that they are configured as intended, and confirm that any needed applications and services have been installed. Then, whether the new cluster uses new or old storage, take each resource group offline on the old cluster and bring the corresponding clustered service or application online on the new cluster.

  For details about this phase, see Steps for completing the transition from the old cluster to the new.

Steps for creating a two-node failover cluster

This section tells how to create a two-node failover cluster. Additional nodes can be added, although the steps for this are not included.

Step 1: Connect the cluster servers to the networks and storage

Step 2: Install the failover cluster feature and other needed software

Step 3: Validate the cluster configuration

Step 4: Create the cluster

Step 1: Connect the cluster servers to the networks and storage

Use the following instructions to connect your selected cluster servers to networks and storage.

For a failover cluster network, avoid having single points of failure. There are multiple ways of accomplishing this. You can connect your cluster nodes by multiple, distinct networks. Alternatively, you can connect your cluster nodes with one network that is constructed with teamed network adapters, redundant switches, redundant routers, or similar hardware that removes single points of failure. (If you use a network for iSCSI, you must create this network in addition to the other networks).

For the two-node failover cluster described in this topic, when you connect the servers to the cluster storage, you must expose at least one volume (LUN). You can expose additional volumes as needed for thorough testing of your configuration. Do not expose the clustered volumes to servers that are not in the cluster.

To connect the cluster servers to the networks and storage

1. Review the details about networks in Overview and Requirements for a Two-Node Failover Cluster, earlier in this guide.

2. Connect and configure the networks that the servers in the cluster will use.

3. If your test configuration includes clients or a non-clustered domain controller, make sure that these computers can connect to the clustered servers through at least one network.

4. Follow the manufacturer's instructions for physically connecting the servers to the storage.

5. If the new cluster is connected to old storage, make at least one logical unit number (LUN) or disk accessible to the servers, and do not make that LUN or disk accessible to any other servers. (That LUN or disk is necessary for the witness disk, which is similar to, although not the same as, the quorum resource in Windows Server 2003.) If the new cluster is connected to new storage, make as many disks or LUNs accessible to it as you think it will need.

   You can use any of the following interfaces to expose disks or LUNs:

   • The interface provided by the manufacturer of the storage.

   • If you are using iSCSI, an appropriate iSCSI interface.

   • Microsoft Storage Manager for SANs (part of the operating system in Windows Server 2008). To use this interface, you need to contact the manufacturer of your storage for a Virtual Disk Service (VDS) provider package that is designed for your storage.

6. If you have purchased software that controls the format or function of the disk, follow instructions from the vendor about how to use that software with Windows Server 2008.

7. On one of the servers that you want to cluster, click Start, click Administrative Tools, click Computer Management, and then click Disk Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.) In Disk Management, confirm that the intended cluster disks are visible.

   Also, if you are using new storage, at this point, avoid using the same drive letters in the new storage as are currently used in the old storage. For other important details about working with drive letters and mount points in new storage, see Cluster Migrations Involving New Storage: Drive Letters and Labels and Cluster Migrations Involving New Storage: Mount Points, earlier in this guide.

8. If you want to have a new storage volume larger than 2 terabytes, and you are using the Windows interface to control the format of the disk, convert that disk to the partition style called GUID partition table (GPT). To do this, back up any data on the disk, delete all volumes on the disk and then, in Disk Management, right-click the disk (not a partition) and click Convert to GPT Disk.

   For volumes smaller than 2 terabytes, instead of using GPT, you can use the partition style called master boot record (MBR).

9. Check the format of any exposed volume or LUN. We recommend NTFS for the format (for a witness disk, you must use NTFS).

Step 2: Install the failover cluster feature and other needed software

In this step, you install the failover cluster feature and any needed services, applications, or server roles. The servers must be running Windows Server 2008.

To install the failover cluster feature on the servers

1. If you recently installed Windows Server 2008, the Initial Configuration Tasks interface is displayed, as shown in the following illustration.

   

   If this interface is displayed, under Customize This Server, click Add features. Then skip to step 3.

2. If the Initial Configuration Tasks interface is not displayed and Server Manager is not running, click Start, click Administrative Tools, and then click Server Manager. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)

   

   In Server Manager, under Features Summary, click Add Features.

3. In the Add Features Wizard, click Failover Clustering, and then click Install.

4. Follow the instructions in the wizard to complete the installation of the feature. When the wizard finishes, close it.

5. Install any needed services, applications, or server roles. For example, if you plan to migrate clustered DHCP to the new cluster, install the DHCP Server role from Initial Configuration Tasks or from Server Manager.

   If you are migrating a Generic Application, Generic Script, or Generic Service resource, you must also confirm that any associated application is compatible with Windows Server 2008, or any associated service exists in Windows Server 2008 and has the same name as in Windows Server 2003. Test the application or service (separately, not as part of a cluster) to confirm that it runs as expected.

6. Repeat the entire installation process for each server that you want to include in the cluster.

Step 3: Validate the cluster configuration

Before creating a cluster, we strongly recommend that you validate your configuration. Validation helps you confirm that the configuration of your servers, network, and storage meets a set of specific requirements for failover clusters.

To validate the failover cluster configuration

1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)

   

2. Confirm that Failover Cluster Management is selected and then, in the center pane under Management, click Validate a Configuration.

   

3. Follow the instructions in the wizard to specify the two servers and the tests, and then run the tests. To fully validate your configuration, run all tests before creating a cluster.

   If you run tests on only one server, you cannot run all tests. Some tests require two servers.

4. The Summary page appears after the tests run. To view Help topics that will help you interpret the results, click More about cluster validation tests.

5. While still on the Summary page, click View Report and read the test results.

   To view the results of the tests after you close the wizard, see

   SystemRoot\Cluster\Reports\Validation Report date and time.html

   where SystemRoot is the folder in which the operating system is installed (for example, C:\Windows).

6. As necessary, make changes in the configuration and rerun the tests.

7. To view Help topics about cluster validation after you close the wizard, in Failover Cluster Management, click Help, click Help Topics, click the Contents tab, expand the contents for the failover cluster Help, and click Validating a Failover Cluster Configuration.

Step 4: Create the cluster

To create a cluster, you run the Create Cluster wizard. If you are migrating one or more Network Name resources with Kerberos enabled, as displayed in Cluster Administrator in the Properties for the Network Name resource, you must also adjust permissions on the corresponding computer accounts (computer objects) in Active Directory (on a domain controller).

To run the Create Cluster wizard

1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)

2. Confirm that Failover Cluster Management is selected and then, in the center pane under Management, click Create a Cluster.

   

   Follow the instructions in the wizard to specify:

   • The servers to include in the cluster.

   • The name of the cluster.

   • Any IP address information that is not automatically supplied by DHCP.

3. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard performed, click View Report.

4. If you are migrating one or more Network Name resources with Kerberos enabled (as displayed in Cluster Administrator in the Properties for the Network Name resource), perform the following permissions change in Active Directory Users and Computers on a domain controller. Locate the computer accounts (computer objects) for any Network Name resources you will migrate that have Kerberos enabled. Make sure you know the correct name of the new cluster, and modify the accounts associated with the Network Name resources to assign Full Control over these accounts to the computer account of the failover cluster.

   The computer account for the failover cluster is created automatically when you run the Create Cluster wizard.

Steps for migrating settings from a server cluster running Windows Server 2003

Use the following instructions to migrate settings from your old cluster to your new cluster. After the Migrate a Cluster wizard runs, it leaves most migrated resources offline, so that you can examine them before bringing them online.

To migrate data and settings from an existing server cluster to a new failover cluster

1. Begin the transition for the storage:

   • If the new cluster uses old storage, plan how you will make LUNs or disks inaccessible to the old cluster and accessible to the new cluster (but do not make changes yet).

   • If the new cluster will use new storage, copy the appropriate folders and data to the storage. Adjust drive letters and mount points as needed. For more information, see Cluster Migrations Involving New Storage: Drive Letters and Labels and Cluster Migrations Involving New Storage: Mount Points, earlier in this guide.

2. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)

3. In the console tree, if the cluster that you created is not displayed, right-click Failover Cluster Management, click Manage a Cluster, and then select the cluster you want to configure.

4. In the console tree, click the plus sign next to the cluster that you created to expand the items underneath it.

5. If the clustered servers are connected to a network that is not to be used for cluster communications (for example, a network intended only for iSCSI), then under Networks, right-click that network, click Properties, and then click Do not allow the cluster to use this network. Click OK.

6. In the console tree, select the cluster.

7. Under Configure, click Migrate Services and Applications.

   

8. Read the first page of the Migrate a Cluster Wizard, and then click Next.

9. Specify the name or IP Address of the cluster or cluster node from which you want to migrate resources, and then click Next.

10. Click View Report. Read the report, which explains whether each resource is eligible for migration and describes additional steps to perform after running the wizard.

    If you are using new storage for the migrated cluster, and the report says that some of the disk resources you expected to migrate cannot be migrated, make sure that you are not using the same drive letters in the new storage as are used in the old storage. For more information, see Cluster Migrations Involving New Storage: Drive Letters and Labels, earlier in this guide.

11. Follow the instructions in the wizard to complete the following:

    • Choose the resource group or groups whose settings you want to migrate.

      Some types of resource groups are eligible for migration and some are not. For more information, see Overview of the Process of Migrating from a Cluster Running Windows Server 2003, earlier in this guide.

      The following illustration shows the selection of a resource group called CLUS-FS1.

      

    • Specify whether the resource groups to be migrated will use new storage, or the same storage used in the old cluster. If the resource groups will use new storage, also specify the disk that each resource group should use after migration. For illustrations of this process, see Cluster Migrations Involving New Storage: Drive Letters and Labels, earlier in this guide.

12. After the wizard runs and the Summary page appears, click View Report. This report contains important information about any additional steps you must perform before you bring the migrated resource groups online. For example, if you have not already installed needed applications on the new cluster nodes, you might need to install them.

13. When the wizard completes, most migrated resources will be offline. Leave them offline at this stage.

Steps for completing the transition from the old cluster to the new

You must perform the following steps to complete the transition from the old server cluster running Windows Server 2003 to the new failover cluster running Windows Server 2008.

To complete the transition from the old cluster to the new

1. Complete the transition for the storage:

   • If the new cluster uses old storage, follow your plan for making LUNs or disks inaccessible to the old cluster and accessible to the new cluster.

   • If the new cluster uses mount points (regardless of whether the storage is new or old), make each disk resource that uses a mount point dependent on the resource of the disk that hosts the mount point. For more information about mount points, see Cluster Migrations Involving New Storage: Mount Points, earlier in this guide.

2. Take each resource group offline on the old cluster and bring the corresponding clustered service or application online on the new cluster.

3. To perform a basic test of failover on the new cluster, expand Services and Applications, and then click the service or application for which you want to test failover.

4. Under Actions (on the right), click Move this service or application to another node, and click the available choice of node. When prompted, confirm your choice.

   You can observe the status changes in the center pane of the snap-in as the clustered service or application is moved. If there are any problems with failover, review the following:

   • View events in Failover Cluster Management. To do this, in the console tree, right-click Cluster Events and then click Query. In the Cluster Events Filter dialog box, select the criteria for the events that you want to display, or to return to the default criteria, click the Reset button. Click OK. To sort events, click a heading, for example, Level or Date and Time.

   • Confirm that necessary services, applications, or server roles are installed on all nodes. Confirm that services or applications are compatible with Windows Server 2008 and run as expected.

   • If you used old storage for the new cluster, rerun the Validate a Cluster Configuration wizard to confirm the validation results for all LUNs or disks in the storage.

   • Review migrated resource settings and dependencies. If you are using new storage that includes disks using mount points, see Cluster Migrations Involving New Storage: Mount Points, earlier in this guide.

   • If you migrated one or more Network Name resources with Kerberos enabled, confirm that the following permissions change was made in Active Directory Users and Computers on a domain controller. In the computer accounts (computer objects) of your Kerberos-enabled Network Name resources, Full Control must be assigned to the computer account for the failover cluster.