Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Failover Engine (FoE) > Clone a virtual server protected by Orion Failover Engine

Clone a virtual server protected by Orion Failover Engine

Table of contents
Created by Michael Perez, last modified by MindTouch on Jun 23, 2016

Views: 8 Votes: 2 Revisions: 5

Overview

This articles describes how to recover when a critical failure on a virtual server protected by Orion Failover Engine occurs. In many scenarios it may be possible to correct the issue with normal troubleshooting. When normal troubleshooting fails, or the time required is too costly, the following clone process can be used.  

Environment

Any virtual server pair protected by Orion Failover Engine

Steps

In a scenario where the Primary and Secondary server communicate over a LAN:

 

When the Secondary server is lost, follow these steps:  

  1. Make a clone of the Primary (Active) VM. 
  2. Take the Secondary (Passive) VM offline. 
  3. Replace the Secondary (Passive) VM with the clone you have taken. Ensure that the interfaces are disabled. 
  4. Properly adjust the IP addresses of the NIC's on the Secondary (Passive) VM. 
  5. Run the FOE Configuration Wizard and ensure that the Secondary VM is set to the Passive role. 
  6. Reboot the VM with the Interfaces Enabled. 

 

When the Primary server is lost, follow these steps: 

  1. ​Make a clone of the Secondary (Active) VM. 
  2. Take the Primary (Passive) VM off-line. 
  3. Replace the Primary (Passive) VM with the clone you have taken. Ensure that the interfaces are disabled. 
  4. Properly adjust the IP addresses of the NIC's on the Primary (Passive) VM. 
  5. Run the FoE Configuration Wizard and ensure that the Primary VM is set to the Passive role.  
  6. Reboot the VM with the Interfaces Enabled. 

 

In either scenario verify that the server pair can synchronize and switchover without issue once the steps above are complete.  

 

In a scenario where the Primary and Secondary server communicate over a WAN:

 

When the Secondary server is lost, follow these steps:  

  1. Make a clone of the Primary (Active) VM. 
  2. Take the Secondary (Passive) VM offline. 
  3. Replace the Secondary (Passive) VM with the clone you have taken. Ensure that the interfaces are disabled. 
  4. Properly adjust the IP addresses of the NIC's on the Secondary (Passive) VM. 
  5. Ensure that the static routes are correctly in place (see: How to Create a Static Route for the SolarWinds Channel Connection in a WAN Environment
  6. Run the FOE Configuration Wizard and ensure that the Secondary VM is set to the Secondary Passive role. 
  7. Reboot the VM with the Interfaces Enabled. 

 

When the Primary server is lost, follow these steps: 

  1. Make a clone of the Secondary (Active) VM. 
  2. Take the Primary (Passive) VM offline. 
  3. Replace the Primary (Passive) VM with the clone you have taken. Ensure that the interfaces are disabled. 
  4. Properly adjust the IP addresses of the NIC's on the Primary (Passive) VM. 
  5. Ensure that the static routes are correctly in place (see:How to Create a Static Route for the SolarWinds Channel Connection in a WAN Environment
  6. Run the FOE Configuration Wizard and ensure that the Primary VM is set to the Passive role. 
  7. Reboot the VM with the Interfaces Enabled. 

 

Last modified
19:27, 22 Jun 2016

Tags

Classifications

Public