Freigeben über

Migration Between Two Multi-Node Clusters

  • Artikel

Updated: January 7, 2010

Applies To: Windows Server 2008 R2

This topic provides an overview and steps that describe how to perform a migration to a cluster running Windows Server 2008 R2, when both the old and new clusters have multiple nodes when the migration is performed.

Important

Before following the steps in this topic, confirm that the clustered service or application that you want to migrate can be migrated by using the Migrate a Cluster Wizard, as described in Migration Paths for Migrating to a Failover Cluster Running Windows Server 2008 R2.

For information about how to perform an in-place migration with the Migrate a Cluster Wizard, 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 Clustered Services and Applications to Windows Server 2008 R2 Step-by-Step Guide.

Overview of migration between two multi-node clusters

This migration uses the Migrate a Cluster Wizard, and it has three phases:

  1. Install two or more new servers, run validation, and create a new cluster. For this phase, while the old cluster continues to run, perform a clean installation of Windows Server 2008 R2 and Failover Clustering on at least two servers. Create the networks that the servers will use, and connect the storage. Make an appropriate number of logical unit numbers (LUNs) or disks accessible to the servers, and do not make those LUNs or disks accessible to any other servers. 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.

    For information about the steps for this phase, see Steps for creating a failover cluster later in this topic.

  2. Migrate clustered services and applications to the new cluster, and determine how you will make any existing data available to the new cluster. When the Migrate a Cluster Wizard completes, all the migrated resources will be offline. Leave them offline at this stage. If the new cluster will reuse 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 make the transition.

    For information about the steps for this phase, see Steps for migrating clustered services and applications to a failover cluster running Windows Server 2008 R2 later in this topic.

  3. Make the transition from the old cluster to the new cluster. The first step in the transition is to take the clustered services and applications offline on the old cluster. 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 will use new storage, copy the appropriate folders and data to the storage. Then bring the clustered services and applications online on the new cluster.

    For information about the steps for this phase, see Steps for completing the transition from the old cluster to the new cluster later in this topic.

Steps for creating a failover cluster

This section describes the following steps:

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.

Note

Review Overview and Requirements for a Failover Cluster Running Windows Server 2008 R2 in this guide for details about the hardware that you can use with Windows Server 2008 R2.

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).

To connect the cluster servers to the networks and storage

  1. Review the details about networks in Overview and Requirements for a Failover Cluster Running Windows Server 2008 R2 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. Make an appropriate number of LUNs or disks accessible to the servers, and do not make those LUNs or disks accessible to any other servers. If the new cluster will use old storage, for testing purposes you can limit the number of LUNs or disks to one or two. If the new cluster will use new storage, make as many disks or LUNs accessible to it as you think it will need.

    We recommend that you keep a small disk or LUN available (unused by clustered services and applications) throughout the life of the cluster, so that you can always run storage validation tests without taking your services and applications offline.

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

    • The interface that is 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 R2). 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 disks in the storage, follow instructions from the vendor about how to use that software with Windows Server 2008 R2.

  7. On one of the servers that you want to include in the 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 Yes.) In Disk Management, confirm that the intended cluster disks are visible.

    If you are using new storage and your disk configuration uses mount points, this is an appropriate time to review Cluster Migrations Involving New Storage: Mount Points in this guide.

  8. If you want to have a new storage volume that is 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).

Important

You can use either MBR or GPT for a disk that is used by a failover cluster, but you cannot use a disk that you converted to dynamic by using Disk Management.
If you purchased software that controls the format or function of the disk, contact the vendor for instructions about how to use that software with Windows Server 2008 R2.

  1. Check the format of any exposed volume or LUN. We recommend that you use NTFS for the format. (For a disk witness, 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 R2.

To install the failover cluster feature on the servers

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

    Figure 1   Initial Configuration Tasks

    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 Yes.)

    Figure 2   Server Manager

    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 Windows Internet Name Service (WINS) to the new cluster, install the WINS Server feature 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 R2, or that any associated service exists in Windows Server 2008 R2 and has the same name as it had in the cluster that you are migrating from. 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 you create 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 Manager. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.)

    Figure 3   Failover Cluster Manager snap-in

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

    Figure 4   Validate a Configuration Wizard

  3. Follow the instructions in the wizard to specify the servers that will be in the cluster and select the tests, and then run the tests. To fully validate your configuration, run all tests before you create 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 Manager, 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.

To run the Create Cluster Wizard

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

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

    Figure 5   Create Cluster Wizard

    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 that the wizard performed, click View Report.

  4. Ensure that your firewall is configured appropriately. For example, if you are using Windows Firewall, and you will be sharing folders and files, use your preferred Windows Firewall interface to allow the exception for Remote Volume Management.

Steps for migrating clustered services and applications to a failover cluster running Windows Server 2008 R2

Use the following instructions to migrate clustered services and applications from your old cluster to your new cluster. After the Migrate a Cluster Wizard runs, it leaves most of the migrated resources offline, so that you can perform additional steps before you bring them online.

To migrate data and clustered services or applications from an existing cluster to a new cluster

  1. 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).

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

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

  4. In the console tree, expand the cluster that you created to see 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 cluster network communication on this network. Click OK.

  6. In the console tree, select the cluster.

  7. Under Configure, click Migrate services and applications.

    Figure 6   Migrate a Cluster Wizard

  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 resource groups, and then click Next.

  10. Click View Report.

Important

We recommend that you read the report, which explains whether each resource is eligible for migration. 

The wizard also provides a report after it finishes, which describes any additional steps that might be needed before you bring the migrated resource groups online.

  1. Follow the instructions in the wizard to complete the following tasks:

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

      Some types of resource groups are eligible for migration and some are not. For more information, see Migration Paths for Migrating to a Failover Cluster Running Windows Server 2008 R2 in this guide.

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

      Migrate a Cluster Wizard, Select Resource Groups page

    • Specify whether the resource groups to be migrated will use new storage or the same storage that you used in the old cluster. If the resource groups will use new storage, you can specify the disk that each resource group should use. Note that if new storage is used, you must handle all copying or moving of data or folders—the wizard does not copy data from one shared storage location to another.

    • If you are migrating from a cluster running Windows Server 2003 that has Network Name resources with Kerberos protocol enabled, specify the account name and password for the Active Directory® account that is used by the Cluster service on the old cluster. Alternatively, you can provide the name and password of another account that has access permissions for the Active Directory computer accounts (objects) that the old cluster uses. This provides the new cluster with the necessary permissions for those accounts.

  2. After the wizard runs and the Summary page appears, click View Report.

Important

We recommend that you read the report, which contains important information about any additional steps that you might need to complete 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.

  1. 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 cluster

You must perform the following steps to complete the transition to the new cluster running Windows Server 2008 R2.

To complete the transition from the old cluster to the new cluster

  1. Prepare for clients to experience downtime, probably brief.

  2. Take each resource group offline on the old cluster.

  3. Complete the transition for the storage:

    • If the new cluster will use 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 will use new storage, copy the appropriate folders and data to the storage. As needed for disk access on the old cluster, bring individual disk resources online on that cluster. (Keep other resources offline, to ensure that clients cannot change data on the disks in storage.) Also as needed, on the new cluster, use Disk Management to confirm that the appropriate LUNs or disks are visible to the new cluster and not visible to any other servers.

  4. If the new cluster uses mount points, adjust the mount points as needed, and 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 in this guide.

  5. Bring the migrated services or applications online on the new cluster.

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

  7. To perform a basic test of failover for the migrated service or application, under Actions (on the right), click Move this service or application to another node, and then click an 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.

  8. If there are any issues with failover, review the following:

    • View events in Failover Cluster Manager. 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 R2 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 that use mount points, see Cluster Migrations Involving New Storage: Mount Points in this guide.

    • If you migrated one or more Network Name resources with Kerberos protocol 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 protocol-enabled Network Name resources, Full Control must be assigned to the computer account for the failover cluster.