Share via

In-Place Migration for a Two-Node Cluster

  • Article

Updated: January 7, 2010

Applies To: Windows Server 2008 R2

This topic provides an overview and steps for upgrading an existing failover cluster to Windows Server 2008 R2 when you have only two servers, that is, performing an in-place migration.

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 a contrasting scenario that also uses the Migrate a Cluster Wizard, see Migration Between Two Multi-Node Clusters. 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 an in-place migration for a two-node cluster

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

  1. Install the new server operating system and run selected validation tests. For this phase, allow one existing server to continue running Windows Server 2003 or Windows Server 2008 and the Cluster service while you begin the migration process. Evict the other server from the old cluster, and then perform a clean installation of Windows Server 2008 R2 and the Failover Clustering feature on it. On that server, run all tests that the Validate a Configuration Wizard will run. The wizard will recognize that this is a single node without storage and limit the tests that it runs. Tests that require two nodes (for example, tests that compare the nodes or that simulate failover) will not run.

    Note that the tests that you run at this stage do not provide complete information about whether the storage will work in a cluster running Windows Server 2008 R2. As described later in this section, you will run the Validate a Configuration Wizard later with all tests included.

    For information about steps for this phase, see Steps for installing a new server operating system and running selected validation tests later in this topic.

  2. Make the new server into a single-node cluster and migrate clustered services and applications to it. Create a new single-node cluster and run the Migrate a Cluster Wizard, but leave the migrated resources offline on the new cluster.

    For information about steps for this phase, see Steps for creating a one-node failover cluster and migrating clustered services and applications to it later in this topic.

  3. Make existing data available to the new cluster, and bring it online. Confirm that the settings for the migrated services and applications are correct. Next, take the migrated services and applications in the old cluster offline. If the new cluster will use new storage, copy the folders and data to appropriate LUNs or disks in the new storage, and make sure that those LUNs or disks are visible to the new cluster (and not visible to any other servers). If the new cluster will use the old storage, make the appropriate disks or LUNs accessible to the new cluster. Bring the services and applications in the new cluster online, and make sure that the resources are functioning and can access the storage.

    For information about steps for this phase, see Steps for making existing data available to the new cluster and bringing it online later in this topic.

  4. Bring the second node into the new cluster. Destroy the old cluster and on that server, install Windows Server 2008 R2 and the Failover Clustering feature. Connect that server to the networks and storage that are used by the new cluster. If the appropriate disks or LUNs are not already accessible to both servers, make them accessible. Run the Validate a Configuration Wizard, specifying both servers, and confirm that all tests pass. Finally, add the second server to the new cluster.

    For information about steps for this phase, see Steps for bringing the second node into the new cluster later in this topic.

Steps for installing a new server operating system and running selected validation tests

You must complete the following steps to install the first server for the new cluster and run selected validation tests on it.

Step 1: Install Windows Server 2008 R2 on one server and connect it to networks and storage

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

Step 3: Run validation tests on the new server

Step 1: Install Windows Server 2008 R2 on one server and connect it to networks and storage

Use the following instructions to install Windows Server 2008 R2 on one server and connect it to networks and storage.

Note

Review Overview and Requirements for a Failover Cluster Running Windows Server 2008 R2, earlier 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 install Windows Server 2008 R2 on one server and connect it to networks and storage

  1. Review the details about networks in Overview and Requirements for a Failover Cluster Running Windows Server 2008 R2 earlier in this guide.

  2. Evict one node from the old cluster and perform a clean installation of Windows Server 2008 R2 on it.

Note

The failover cluster feature is not available in Windows Web Server 2008 R2 or Windows Server 2008 R2 Standard.

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

  2. Follow the manufacturer's instructions for physically connecting storage to the server running Windows Server 2008 R2.

  3. Make an appropriate number of LUNs or disks accessible to the server running Windows Server 2008 R2, 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.

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

  5. On the server running Windows Server 2008 R2, 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.

  6. 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, for the server running Windows Server 2008 R2, 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. Still using the server running Windows Server 2008 R2, 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 server on which you install the failover cluster feature must be running Windows Server 2008 R2.

To install the failover cluster feature on a server

  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.

Step 3: Run validation tests on the new server

In this step, you run some validation tests on the new server. You will need to run the Validate a Configuration Wizard again later, after you add the second node to the cluster running Windows Server 2008 R2.

To run validation tests on the new server

  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

    Follow the instructions in the wizard to specify the server, specify that you want to run all tests (in this case, all the tests that are possible with one node), and then run the tests. Note that some tests require multiple nodes to run.

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

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

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

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

Steps for creating a one-node failover cluster and migrating clustered services and applications to it

You must complete the following steps to create a new one-node failover cluster and to migrate clustered services and applications to it from your old cluster.

Step 4: Create the cluster

Step 5: Migrate clustered services and applications from the old cluster to the new cluster

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

Step 5: Migrate clustered services and applications from the old cluster to the new cluster

Use the following instructions to migrate clustered services and applications from your old one-node cluster to your new one-node 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 clustered services and applications from the old cluster to the new cluster

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

  3. In the console tree, expand the cluster that you created to see the items underneath it.

  4. If the clustered server is 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.

  5. In the console tree, select the cluster.

  6. Under Configure, click Migrate services and applications.

    Figure 6   Migrate a Cluster Wizard

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

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

  9. 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 node, 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 making existing data available to the new cluster and bringing it online

Use the following procedure to make existing data available to the new cluster and bring it online.

To make existing data available to the new cluster and bring it online

  1. Confirm that the settings for the migrated services and applications appear correct.

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

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

  4. 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 node, use Disk Management to confirm that the appropriate LUNs or disks are visible to the new cluster and not visible to any other servers.

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

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

Steps for bringing the second node into the new cluster

Use the following instructions to bring the second node into the new cluster. As part of this process, you will run validation tests that include both servers.

To bring the second node into the new cluster

  1. On the new cluster, confirm that the migrated services or applications are functioning and that clients can connect to them.

  2. On the old cluster (the server that is running Windows Server 2003 or Windows Server 2008), open the cluster interface. Use this interface to delete the migrated resource groups, and then destroy the old cluster.

  3. On the same server, perform a clean installation of Windows Server 2008 R2.

  4. Add the failover clustering feature in the same way that you added it to the other server, and install any needed services, applications, or server roles.

  5. Connect the newly-installed server to the same networks and storage that the existing failover cluster node is connected to.

  6. Identify the disks or LUNs that are exposed to the new one-node failover cluster, and expose them to the newly-installed server also.

    We recommend that you keep a small disk or LUN accessible to both nodes, and unused by clustered services and applications, throughout the life of the cluster. With this LUN, you can always run storage validation tests without taking your services and applications offline.

  7. On either server running Windows Server 2008 R2, open the failover cluster snap-in. 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.)

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

    Figure 8   Validate a Configuration Wizard

    Follow the instructions in the wizard, but this time, be sure to specify both servers (not just the existing cluster name) and specify that you want to run all tests. Then, run the tests. Because two nodes are now being tested, a more complete set of tests will run, which takes longer than when there was only one node.

Important

If a clustered service or application is using a disk when you start the wizard, the wizard will prompt you about whether to take that clustered service or application offline for the purposes of testing. If you choose to take a clustered service or application offline, it will remain offline until the tests finish.

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

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

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

    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.

  4. If the new cluster is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the new cluster.

  5. In Failover Cluster Manager, in the console tree, select the one-node cluster, and then in the Actions pane, click Add Node.

  6. Follow the instructions in the wizard to specify the server that you want to add to the cluster.

  7. After the wizard runs and the Summary page appears, if you want to view a report of the tasks that the wizard performed, click View Report.

    After you close the wizard, in the center pane, you might see a warning about “Node Majority.” You will correct this issue in the next few steps.

    To view the report after you close the wizard, see the following folder, where SystemRoot is the location of the operating system (for example, C:\Windows):

    SystemRoot**\Cluster\Reports\**

  8. In the console tree, expand Storage. Check to see if all the disks that you want to make available to the new cluster are shown, either in one of the clustered services or applications or in Available Storage. In most cases, you need at least one disk in Available Storage for the next step (specifying a witness disk). If you need to add a disk, in the Actions pane, click Add Storage and follow the steps in the wizard.

    Before you can add a disk to storage, it must be accessible from both nodes in the cluster. A disk that is to be used for a witness disk can be a relatively small disk, but not less than 512 MB in size.

  9. In the console tree, right-click the new cluster, click More Actions, and then click Configure Cluster Quorum Settings.

  10. Follow the instructions in the wizard to select the most appropriate quorum setting for your needs. In most cases, this is the Node and Disk Majority quorum configuration, which also requires that you specify an appropriate disk (from Available Storage) for the witness disk.

  11. Expand Services and Applications, and then click a migrated service or application that you want to test.

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

    • 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 earlier 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.