VMware vCenter Server Heartbeat - Migrating vCenter Server Heartbeat 6.3 Update 1 from Identical Nodes to Non-Identical Nodes

Follow

Summary

This Knowledge Base article provides the procedure to migrate vCenter Server Heartbeat 6.3 Update 1 from an Identical nodes configuration to a Non-identical nodes configuration.


More Information

This procedure reconfigures vCenter Server Heartbeat 6.3 Update 1 installed in a LAN environment where vCenter Server and SQL Server are protected but not installed on the same machine (remote SQL Server) from an Identical nodes configuration to a Non-identical nodes configuration.

Procedure

Before starting this process, shutdown vCenter Server Heartbeat on both servers leaving the protected applications running.

On Secondary Server

  1. Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual .
  2. Open the Configure Server wizard, click the Public tab, and select Non-identical .
  3. Provide the Service Name for vCenter Server.

    Note: Normally this is the current name of vCenter Server.
  4. In the NIC drop-down, select the Principal (Public) NIC.
  5. In the Public IP drop-down, select the Principal (Public) IP address assigned to the Principal (Public) NIC.
  6. In the first Mask field, enter the Subnet Mask of the Principal (Public) IP address.
  7. In the Mgmt IP field, enter a reserved Management IP address for the Secondary server.
  8. In the second Mask field, enter the Subnet Mask of the Management IP address.
  9. Click Finish .
  10. Right-click the Secondary server image and select Edit Settings .
  11. Disable the network adapters for both the VMware Channel and Principal (Public) NICs.
  12. Open Network Connections, right-click the Principal (Public) connection and select Properties . Select Internet Protocol (TCP/IP) and click Properties .
  13. Change the IP address to match that of the Secondary Management IP address previously configured in the Configure Server wizard. Click OK twice to close the dialogs.
  14. Navigate to the server’s System Properties , select the Computer Name tab, and click Change to rename the Secondary server and join a Workgroup. When requested, restart the server.
  15. Right-click the Secondary server image and select Edit Settings .
  16. Re-enable the virtual network adapters for both the VMware Channel and Principal (Public) NICs.
  17. Navigate to the server’s System Properties , select the Computer Name tab, and click Change to join the domain. When requested, restart the server.

On Primary Server

  1. Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual , Stopped , and close the dialog.
  2. Open the Configure Server wizard, click the Public tab, and select Non-identical .

    Note: The option selected should be the same as selected previously when configuring the Secondary server.
  3. Provide the Service Name for vCenter Server.

    Note: The Service Name is the same as current name of the Primary server.
  4. In the NIC drop-down, select the Principal (Public) NIC.
  5. In the Public IP drop-down, select the Principal (Public) IP address assigned to the Principal (Public) NIC.
  6. In the first Mask field, enter the Subnet Mask of the Principal (Public) IP address.
  7. In the Mgmt IP field, enter a reserved Management IP address for the Primary server.
  8. In the second Mask field, enter the Subnet Mask of the Management IP address.
  9. Click Finish .
  10. Navigate to the server’s System Properties , select the Computer Name tab, and click Change to rename the Primary server. When requested, restart the server.
  11. On both the Primary and Secondary servers, navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Automatic, and close the dialog.

Note: If using Microsoft DNS servers in a Locked Down mode, vCenter Server Heartbeat will not attempt to update DNS and therefore the Administrator must prepopulate the DNS server with entries for the new management names and IP addresses that are to be used.



Applies To

vCenter Server Heartbeat 6.3 Update 1 Only
vCenter Server 4.0 and later using a remote SQL Server


Related Information

vCSHB-Ref-2137

KBID-2137

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.