HP PART NUMBER: 461487-401A manual Premigration consideration steps for clusters

Page 79

B Performing migrations in a Microsoft Cluster server environment

Migrations in a Microsoft Cluster server environment often require you to move an operating system, appropriate applications, and data to new server hardware. In a cluster, various applications such as Microsoft Exchange, Microsoft SQL Server, or a file share can be installed. Cluster migration includes moving these additional resources.

This appendix discusses a scenario where a file share with both nodes and the cluster resources must be migrated. Basic components in a Microsoft Cluster server environment include:

Shared disk, where the quorum and log reside

Cluster IP address

Cluster network name

Application resources (such as Microsoft Exchange, SQL Server, or file share)

Microsoft Windows Server 2008 x64-based failover clusters support up to 16 nodes in a single cluster. Microsoft Windows 2003 Server Enterprise Edition and Windows Server 2003 Data Center Edition support up to eight nodes in a cluster. These nodes are connected to a Fibre Channel switch that is connected to a storage array where the quorum and resources are stored. If multipathing is used, multiple Fibre Channel switches connect the nodes to the server so that if one path fails, the other path takes over the connection from the nodes to SAN array.

Figure 12 The basic hardware design of a three-node duster.

Premigration consideration steps for clusters

1.Note the IP address and network names of the nodes to which the clusters are attached.

Premigration consideration steps for clusters

79

Image 79
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewRight configuration Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration securityGenerating static or dynamic certificates Installing ProLiant Support PacksInstalling Service Pack for ProLiant Disabling antivirus softwarePreparing software for migration Part III Migration Preparing a Microsoft Hyper-V source server Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Verifying Linux source server requirementsDeploying Agents Removing guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Virtual machine hosts PrerequisitesLinux destination size requirement Physical destination serversBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationSource virtual machine prerequisites Preparing for a Linux server migrationSource physical server prerequisites SAN migrations in Windows Starting the migration wizard Launching server migration by using the Deploy menuIdentify the source server Launching server migration by using Quick LaunchQuick Launch Starting the migration wizard X2P postmigration tasks Windows Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration Postmigration tasksX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating Windows migrations Viewing migration logsValidating the migration Validating Linux migrationsPart IV Troubleshooting and support User interface TroubleshootingServer migration wizard hangs HP SIM Source server identification fails Source preparationLinux Source Agent window does not appear on Rhel 64-bit Migration Agent deployment failsPerform any one of the following on the source server Incorrect LUN size is detected in of the migration wizardDestination preparation Unable to boot Windows due to unsigned or corrupt driversDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration process 2011/03/14 141934 The job failed Migration hangs if the source server is shut downReiserFS volumes are blocked for Linux migration Ntfs resize error message appearsMigration fails during the disk cloning phase SAN-connected destination server displays a blue screen Error occurs during data copy of Linux migrationHP Smart Array B320i controller name is not displayed Destination server boots with an invalid IP addressPostmigration Linux migration to servers with iSCSI storage fails to bootHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesWebsites HP authorized resellersRelated information DocumentsRelated documentation Typographic conventionsTIP Documentation feedback Applying old server migration standalone licenses Basic hardware design of a three-node duster Premigration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter