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.
Note: Before you begin please read this entire article so that you get a correct understanding of all the steps and the entire process.
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. Do not restart Neverfail Engine.
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 on the Primary machine and do the followings:
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. From Windows Service Control Manager set the Neverfail Engine service to be on Automatic and start it.
B. On the newly cloned Secondary (Passive) machine:
1. Do an Edit Settings of that VM and disconnect its NICs from vSphere Client.
2. Start the newly cloned Secondary machine.
3. After the OS boots up, go in the Properties window of each NIC and verify that the IP, Subnet Mask, Gateway and DNS settings are correct.
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 machine.
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 our Neverfail Knowledgebase article #466 .
7. Do another Edit Settings from vSphere CLient and re-connect all NICs of the Secondary machine.
8. From Windows Service Control Manager set the Neverfail Engine service to be on Automatic and start it.
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
Related Articles
How To Clone A Primary Server Deployed As Hyper-V Machine 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 the server is a Hyper-V Virtual Machine. More Information Initial Assumptions: The Primary/Active server is healthy and will be used as source ...How To Clone A Primary Server With Windows Backup (Wbadmin) For Deploying A Secondary Server By Using Neverfail EMS Console
Summary This KB article describes how to use Windows Server Backup (aka, wbadmin) in order to clone the Primary server for completing the deployment of Engine on a Secondary or even a Tertiary server. Since Engine is already installed on the Primary ...How to Install Neverfail Engine Management Service (EMS - web centralized console)
Summary This Knowledgebase article provides the procedure to install the Neverfail Engine Management Service. Using this procedure will ensure that you achieve a successful installation. Note: You CAN'T install the EMS web console on a server which ...Neverfail Continuity Engine Secondary server deployment hangs at: Waiting for Secondary VM to complete auto configuration...
Summary This Knowledgebase article provides details and a workaround procedure for the situation where Secondary server deployment hangs at Waiting for Secondary VM to complete auto configuration... step and eventually, the Secondary VM deployment ...Configuring VMware Converter In Neverfail Engine Management Server (EMS)
Summary This Knowledgebase article provides the procedure used to configure VMware Converter for cloning from a physical server to a virtual server. More Information Use the Configure VMware Converter feature to convert physical Primary or VMs with a ...