How To Clone A Primary Server Deployed As VMware VM For Building A Secondary Server Without Neverfail EMS Web Console

How To Clone A Primary Server Deployed As VMware VM For Building A Secondary Server Without Neverfail EMS Web Console

Summary

This Knowledgebase article provides the step-by-step procedure necessary to replace a server when this is a VMware Virtual Machine.

More Information

Initial Assumptions

· The Primary active server will be cloned.

· The Secondary passive server will be replaced by the new clone of Primary active server.

Before you begin

· Read the entire article before performing any steps!

Procedure

A. On the Primary (Active) server:

1. Open Windows Services console and stop the Neverfail Continuity Engine service.

2. Also from the Windows Services console set the Neverfail Engine service to Manual instead of Automatic. 

3. Open the Neverfail Configure Server Wizard (from the Neverfail System Tray icon, or Neverfail group of icons under Windows Start button).

4. Chose "Stop Webservices" when prompted.

a. Select the Machine tab.

b. Change the “Physical Hardware Identity” of the server to Secondary .


c. The “Active Server” should remain set to Primary so that after the cloning will be completed, this value will remain the same onto the newly cloned Secondary server.

d. Click the Finish button.

5. Start cloning the Primary machine using the VMware vCenter or other tools.

6. Once the clone is completed, open the Neverfail Configure Server wizard.

a. Select the Machine tab.
b. Change the “Physical Hardware Identity” back to Primary .
c. Make sure that the “Active Server” has the Primary value selected.
d. Click the Finish button.

7. Set the Neverfail Engine service to Automatic using the Windows Service Control Manager.

 

B. On the newly cloned Secondary (Passive) server:

1. Virtually disconnect the virtual NICs for Public and Channel of the VM from vSphere Client.

2. Start the newly cloned Secondary machine.

3. After the OS boots up, go in the Properties window of each network card, verify that the IP address settings are correct. It may be necessary to remove ghost NICs. If ghost NICs are found, open a command prompt and run the following commands:

a. set devmgr_show_nonpresent_devices=1

b. devmgmt.msc

c. in the device manager snap-in click View -> Show hidden devices

d. Uninstall all ghost NICSs without deleting driver software for those devices.

4. Open the Neverfail Configure Server Wizard -> go to Machine tab -> make sure that the “Physical Hardware Identity” is set to Secondary and that “Active Server” is the Primary.

5. Also, in the Neverfail Configure Serve Wizard -> go to Public tab and verify that the Public IP is correct for Secondary.

6. If this is a WAN installation then open a command prompt window and use the “ route print ” command to check if all WAN routes are correctly configured. For more details, read Neverfail Knowledgebase article #466 .

7. Virtually reconnect the virtual NICs for Public and Channel of the Secondary VM from vSphere Client.

8. In the System Tray, right click on the Neverfail tray icon and select Start Neverfail Engine.

9. Set the Neverfail Engine service to Automatic using the Windows Service Control Manager.

 

C. On the Primary (Active) server:

1. In the System Tray, right click on the Neverfail tray icon and select Start Neverfail Engine.

2. Open the Neverfail Advanced Management Client and verify that replication started between Primary active and the newly cloned Secondary passive servers.

Applies To

All Windows OS versions when deployed as a VMware virtual machine.

Related Information

Knowledgebase article #466 - How to Create a Static Route for the Neverfail Channel Connection in a WAN Environment

 

 

 

KBID-2726