HP Virtual Connect Enterprise Manager Software Pre-migration consideration steps for clusters

Page 71

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

Pre-migration consideration steps for clusters

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

Pre-migration consideration steps for clusters

71

Image 71
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewProduct Description Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying application station system requirements Preparing hardware for migrationVerifying hardware and operating system support 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 PacksDisabling antivirus software 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 Uninstalling guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install dialog 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 migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations X2V post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2P post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processValidating Linux migrations X2V post-migration tasks LinuxViewing migration logs Validating the migrationPost-migration tasks Part IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface Source preparationMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration Migration fails during the disk cloning phase Error during data copy of Linux migration SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot the server and then reinstall PSP manually Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites