Hi cluster fans,
Many of you have been using the Release Candidate (RC) of Windows Server 2008 R2 and want to move to the Release to Manufacturing (RTM) build. This guide will walk you through the upgrade path which uses the “Migrate a Cluster Wizard” tool to move your resources to your RTM cluster. Details about the Migration Wizard are available here: http://go.microsoft.com/fwlink/?LinkID=142796 .
This guide applies to resources which are migrated using the “Migrate a Cluster Wizard” which include DFS-Namespace, DHCP, (MS)DTC, File Server, Generic Application, Generic Script, Generic Service, iSNS, MSMQ, NFS, Remote Desktop Connection Broker, WINS and 3 rd Party resources.
Below are notes and upgrade paths for some resources.
To migrate a DFS-R cluster, follow these guidelines:
1. Add the network name (VCO) of the new Windows Server 2008 R2 Failover Cluster to the replication group. Details available at: http://technet.microsoft.com/en-us/library/cc776309(WS.10).aspx
2. Wait until DFS-R finishes synchronizing the replicated data to that cluster
3. If you plan to decommission the old cluster, remove its network name from the replication group. If necessary, destroy the old cluster.
a. If you plan to use both clusters, give the File Server resource group a unique network name on the new cluster before adding it to the replication group.
For more information about DFS Replication in Windows Server 2008 R2 visit: http://technet.microsoft.com/en-us/library/cc737634(WS.10).aspx
Make sure you first drain the MSDTC transaction logs. Migrating a MSDTC resource to a new cluster does not carry the information stored in the transaction logs. This means, if you have any unresolved transactions, transaction state information about those transactions will be lost once you migrate the resource.
Follow these steps to check and resolve if you have any unresolved transactions.
1) Stop the application creating transactions on the DTC cluster resource that is being migrated, so that it’s possible to completely empty the DTC transaction log of all active, in-doubt, and failed-to-notify transactions.
2) Run dcomcnfg on one of the nodes in the Failover Cluster that hosts the DTC cluster resource.
3) Open the clustered DTC resource that is being migrated by navigating to Component Services -> Computers -> My Computer -> Distributed Transaction Coordinator -> Clustered DTCs.
4) Open the Transaction List for this DTC resource. If this list is empty, the transaction log is empty and this resource is ready to be migrated. If there are transactions listed, then either wait for them to be completed or manually resolve them by right clicking on them and selecting Forget, Commit, or Abort.
· Transaction State Resolution Options: http://msdn.microsoft.com/en-us/library/ms681604(VS.85).aspx
· View Transaction Information: http://technet.microsoft.com/en-us/library/cc753009(WS.10).aspx
To run Exchange on Windows Server 2008 R2, install a clean version of Exchange 2010 as there is no direct upgrade path. After Exchange 2010 has been installed, customer data can be migrated using the Move Mailbox tool to migrate mailboxes and Public Folder Replication to migrate public folders.
· Exchange (2007) Move Mailbox Scenarios: http://technet.microsoft.com/en-us/library/bb124797.aspx
· Exchange 2010 Move Local Legacy Mailbox: http://technet.microsoft.com/en-us/library/bb124495(EXCHG.140).aspx
· Exchange 2010 PowerShell: http://technet.microsoft.com/en-us/library/aa997599(EXCHG.140).aspx
To migration Hyper-V Virtual Machines (VMs), refer to the guidance in this KB: http://support.microsoft.com/kb/957256 which is regularly being updated.
Alternatively, you may use System Center Virtual Machine Manager’s (SCVMM) Quick Storage Migration feature: http://blogs.technet.com/virtualization/archive/2009/06/25/system-center-virtual-machine-manage...
When an MSMQ resource is included in the migration, it is important that you do NOT delete the source or the destination MSMQ resource until you are sure the migration is complete. Deleting either resource can remove the MSMQ service specific data from the shared storage, and cause the other resource to fail to come online. When you delete the source resource, or if you have to delete the newly migrated MSMQ resource or its group to perform another migration, please remove the disk resource from the group that is being deleted and take it offline first, then delete the MSMQ resource or the group. It is highly recommended that you backup the data associated with the MSMQ resource before migration. In case of the MSMQ service specific data being accidently deleted, you can restore the data from the backup. For more information about MSMQ backup and restore, please visit Backing up and restoring messages .
To migrate your clustered printers, use either the UI or CLI version of PrintBRM.
· Print Migration Overview: http://technet.microsoft.com/en-us/library/cc722360.aspx
· Print Migration Guide: http://technet.microsoft.com/en-us/library/dd379488
To migrate your clustered SQL instances, use the SQL upgrade utility:
· SQL Server Supported Upgrade Paths: http://msdn.microsoft.com/en-us/library/ms143393.aspx
· SQL Server 2008 Failover Clustering Rolling Upgrade Guide: http://msdn.microsoft.com/en-us/library/ms191295.aspx
· SQL Server 2008 Failover Clustering whitepaper: http://sqlcat.com/whitepapers/archive/2009/07/08/sql-server-2008-failover-clustering.aspx
· SQL Server 2008: http://support.microsoft.com/kb/958734
· SQL Server 2008 Upgrade technical reference: http://msdn.microsoft.com/en-us/library/cc936623.aspx
· SQL Server 2005: http://msdn.microsoft.com/en-us/library/ms191295(SQL.90).aspx
For a clustered resource type which do not come inbox, the Migrate a Cluster Wizard will perform a “best effort” migration. If the resource type is not added to the new cluster is will not be migratable.
To attempt the “best effort” migration, you can first add this new resource type on the new cluster:
1) Right-click on the (new) Cluster Name
2) Select Properties
3) Click the ‘Resource Types’ tab
4) Select Add
5) Specify the Resource Dll path and file name, Resource Type Name, and Resource type display name
6) Click OK
7) Click Apply and exit the properties page
8) Run the Migrate a Cluster Wizard
Note : this guide assumes you are reusing the same hardware and storage. In this example I have a 2-node WS08 R2 RC Failover Cluster (Build 7100) running a highly-available DHCP Server, File Sever and Remote Desktop Connection Broker. I will be migrating to WS08 R2 RTM (Build 7600).
1. Move your running resources to a node or subset of nodes. The resources have already been moved to Node2 (SymonP-n2). Clients will still be connected to the services and applications.
2. Pause the node or subset of nodes which are not hosting the resources from the cluster, by right-clicking on the node name, then selecting Pause.
3. Evict the paused nodes by selecting More Actions…, then selecting Evict. In this example Node1 will be evicted.
4. Clean install Windows Server 2008 R2 RTM on the machines which have been evicted, an upgrade is not supported. Enable the Failover Clustering feature and any other features or roles.
5. Create a new cluster with this subset of nodes now running Windows Server 2008 R2 RTM.
6. Run the “Migrate a Cluster Wizard” and migrate your resources to the new cluster. Do not online these resources yet. For more information about cluster migration, review this guide: http://go.microsoft.com/fwlink/?LinkID=142796 . The screenshot below shows my new RTM cluster which currently has 1 node.
a. Important: Read the pre- and post-migration reports to understand any additional steps or requirements to complete the migration.
7. Offline any remaining resources on the RC cluster. The services and applications will now be unavailable to clients.
8. Reattach the newly upgraded cluster nodes to the storage. The disks or CSV volumes may be mounted as a different path than what it was mounted as before the upgrade exercise. Add the storage to the Windows Server 2008 R2 RTM cluster if you are reusing storage.
9. Run “Validate a Cluster Wizard” once the storage is attached.
10. Online any other resources or applications which were migrated to the (new) RTM cluster. The services and applications will now be available to clients.
11. Delete the offline resources and destroy the Windows Server 2008 R2 RC cluster by right-clicking on the cluster name, selecting More Actions…, then selecting Destroy Cluster. Clean install Windows Server 2008 R2 RTM on these nodes, an upgrade is not supported. Enable the Failover Clustering feature and any other roles or features. Add these newly upgraded machines to the new Windows Server 2008 R2 RTM cluster, by clicking on the cluster name, then selecting Add Node…
You have now upgraded your Failover Cluster from Windows Server 2008 R2 RC to Windows Server 2008 RTM.
Clustering & High-Availability
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.