Performing a Disaster Recovery Failover and Failback

Failover and Failback Process Overview

In the event of planned or unplanned downtime, begin the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. process by using the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. to launch recovery machines in your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.

Note: CloudEndure performs most Failover and Failback related operations other than the actual redirection of traffic from the primary site to the Disaster Recovery site.

In this section we will cover:

1. Preparing your Disaster Recovery Project for Failover
2. Testing your CloudEndure Disaster Recovery solution prior to Failover
3. Performing a Failover
4. Preparing your Disaster Recovery Project for Failback
5. Failback Network Requirements
6. Failback Diagrams
7. Testing your CloudEndure Disaster Recovery Solution prior to Failback
8. Performing a Failback
9. Returning to Normal Operations

Detailed instructions on performing a FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. and FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. can be found in the following sections.

1. Performing a Failover with CloudEndure
2. Performing a Failback with CloudEndure

Preparing for Failover

Prepare your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. ProjectA Project is the basic organizational unit for running a CloudEndure solution.:

1. Configure Replication Settings
2. Install Agents
3. Configure Blueprints
4. Wait until machines reach Continuous Data Protection mode.

Test your Disaster Recovery solution

1. Launch TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines in TestThe same for Migration and Disaster Recovery. A process that is initiated manually. Launches Target machines on the Target location, and marks the tested machines on the Console as ready for Live Migration/Disaster Recovery. It is recommended to initiate a Test after the initial replication is completed. When a Test is initiated, an updated snapshot is created on the Staging Aaea. From this snapshot, a disk is created. Mode.
2. Perform a FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover..

Note: Test Mode and Recovery Mode create exactly the same Target machines, but by using the correct Mode, the User Console will correctly indicate if the Source machine was tested recently or if it is currently Failed Over (the User Console assumes that a Target machine launched in Recovery Mode was Failed Over, even though you do the actual Failover outside of CloudEndure.)

Important: You should launch machines in Test Mode prior to launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. them in Recovery Mode in order to ensure that the process has been thoroughly tested. After testing either SSH (Linux) or RDP (Windows) into your machineA physical or virtual computer. and ensure that everything is working correctly. If there are any issues, contact Support.

Performing a Failover

1. Launch machineA physical or virtual computer. in Recovery Mode
2. Perform the actual FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. (directing traffic to your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines) using the tool or means you use for directing traffic.
3. After a successful FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time., you can prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. with the aid of CloudEndure.

Preparing for Failback

After performing a successful FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time., you can prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. with the aid of CloudEndure. Follow these steps to perform a successful FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover.:

Note: Steps may vary according to your setup and Failback method. You can see specific steps for each setup here.

1. Before returning to normal operation, you need to have the data that was written to your Recovery machines copied back to the machines in your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure.
2. Do that by choosing the Prepare for Failback option in the PROJECT ACTIONS menu in the User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions..
   
3. The ProjectA Project is the basic organizational unit for running a CloudEndure solution. view will reset, and what were your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines will now appear as SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines, ready to replicate their data back to the original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure, which will now (temporarily) appear as your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.
4. Initialize Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. according to your setup.

Failback Network Requirements

Ensure that you comply by these additional FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. network requirements if you're failing back to vCenterVMWare's virtual environment management platform. or Other Infrastructure.

vCenter

The following are additional network requirements that are required for vCenterVMWare's virtual environment management platform. integration to work during the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process:

• VLANThe network within vCenter from which you want to launch the Replication Servers. for StagingA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. (Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. and Conversion ServerThe CloudEndure machine launched in Target region for the purpose of performing Machine Conversion.) should:
  • Provide DHCP addressing
  • Allow outbound port 1500 (when failing back)
  • Allow access to S3 so the replicator software can be downloaded
  • Allow access to console.cloudendure.com via TCP 443
  • Allow access to your vCenterVMWare's virtual environment management platform./vSphere hosts so it can send API calls to it
• VLANThe network within vCenter from which you want to launch the Replication Servers. for ApplianceThe CloudEndure vCenter Appliance. You must install the data center in order to use the CloudEndure solution. should:
  • Allow access to console.cloudendure.com via TCP 443
  • Allow access to S3 so the replicator software can be downloaded
  • Allow access to your vCenterVMWare's virtual environment management platform./vSphere hosts so that the virtual ApplianceThe CloudEndure vCenter Appliance. You must install the data center in order to use the CloudEndure solution. can send API calls to it
• SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance should:
  • Allow inbound port 1500 open on the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance from which you are failing back so that the CloudEndure Failback ClientThe software used with Failback in Disaster Recovery. could connect to it.
  • Allow the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance access to console.cloudendure.com via TCP 443.
• Administrative permissions to vCenterVMWare's virtual environment management platform. as configured in the Appliance installation.

Other Infrastructure

• SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance
  • Allow inbound port 1500 open on the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance from which you are failing back so that the CloudEndure Failback ClientThe software used with Failback in Disaster Recovery. could connect to it.
  • Allow the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. AWS instance access to console.cloudendure.com via TCP 443.
• TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). non-cloud or other-cloud on-prem environment (using the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. client)
  • Allow the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). non-cloud or other-cloud on-prem environment access to S3 so the replicator software can be downloaded.
  • Allow your non-cloud or other-cloud on-prem environment access to console.cloudendure.com over port 443.
  • Allow outbound port 1500 open on the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). environment

Failback Diagrams

The following diagrams illustrate the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process for each infrastructiure.

AWS

vCenter

Other Infrastructure

Testing before performing actual Failback

Ensure that all machines have reached Continuous Data Protection status after performing the Prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. action.

Before directing traffic back to your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure., you should test that all the machines which you prepared for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. are usable. Do this by checking the box to the left of the machineA physical or virtual computer. name in the Machine List View and selecting Test Mode under the Launch Target Machines menu.

Performing the Failback

Direct traffic back to your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure using the tool or means you use for directing traffic.

Note: Stop all operational services on the Source machine prior to Failback.

Note: Ensure to schedule a Failback window during which the Failback will be performed.

Note: CloudEndre will always only replicate the deltas (changes) during Failback.

Returning to normal operation

Once traffic was directed back to your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure, you want the machines in your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. ProjectA Project is the basic organizational unit for running a CloudEndure solution. to start replicating back to the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure . Do this by using the Back to Normal Operation option in the PROJECT ACTIONS menu in the User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions..

Note: There is no need to reinstall Agents on the machines.

Failover and Failback with CloudEndure - Detailed Instructions

Video Guide

AWS to AWS Failover and Failback

This video illustrates how to perform a FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. and Fully Orchestrated FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. from an AWS SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. to an AWS TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery)..

vCenter to AWS Failover and Failback

This video illustrates how to perform a FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. and Fully Orchestrated FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. from a vCenterVMWare's virtual environment management platform. SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. to an AWS TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery)..

Performing a Failover with CloudEndure

Note: If you plan to use CloudEndure’s orchestrated Failback from an AWS Source to an AWS Target, set the priority of any created network interfaces associated with Windows Target machines to ‘2’. This will prevent connectivity issues during the Failback process. Do this before directing traffic to the Target machine, as this network change may momentarily interrupt network connectivity.

1. Before you start the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time., open the User Console > Machines page. There, verify that the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. you want to FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. has the following status indications under each column.
• DATA REPLICATION PROGRESS - Continuous Data Protection
• STATUS – Target machine can be launched
• DISASTER RECOVERY LIFECYCLE – Tested Recently
  
  
2. Check the box to the left each machineA physical or virtual computer. you want to FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. and click the Recovery Mode option under the LAUNCH X TARGET MACHINES button.
   
   
3. A confirmation message will appear. Click NEXT to launch the Recovery machineA physical or virtual computer..
   

   Note: Any previous Target machines launched for the Source machines you are testing will be deleted.

   
   
   
4. Choose the Recovery PointA specific point within the Point-in-Time Recovery function. for the Target machineThe Machine created during Test, Cutover or Recovery. in Recovery Mode. This will indicate which Recovery PointA specific point within the Point-in-Time Recovery function. the system will use when launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. new TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines for the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time.. You can either choose the Latest Recovery PointA specific point within the Point-in-Time Recovery function., or a previous Recovery PointA specific point within the Point-in-Time Recovery function. from the list.
   
   

   Note: If the "Latest" Recovery Point is chosen, then CloudEndure will take a new snapshot of the Source machine and use that snapshot.

   
   After choosing your Recovery PointA specific point within the Point-in-Time Recovery function., click CONTINUE WITH LAUNCH.
   
   Most infrastructures allow the following Recovery PointA specific point within the Point-in-Time Recovery function. schedules:
   
• every 10 minutes in the past hour
• every 1 hour in the past 24 hours
• every 1 day in the past 30 days
5. A message will appear on the upper right corner of the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions., informing you that the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. has started and that a Target machineThe Machine created during Test, Cutover or Recovery. is being launched for the selected Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine..
   
   

   Note: You can view the progress of the Target machine launch by clicking on the Job Progress tab.
   
   
   

    

   
   The Job Progress window will appear, providing details for the Target machine launch process.
   

6. Once the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. is completed, on the DISASTER RECOVERY LIFECYCLE column, the status will change to Failed over The CloudEndure Console assumes that you have completed the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. process by this point.
   
   
7. To view additional information on the test, click the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine.. The Machine Dashboard page will appear, displaying the date of the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. (last recovery launch.)
   
   

Failing Over specific machines

 To Failover specific machines, you will need to create a new ProjectA Project is the basic organizational unit for running a CloudEndure solution. and configure it identically to your original DRThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. ProjectA Project is the basic organizational unit for running a CloudEndure solution. (same TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). region, license, credentials and Replication SettingsIn the Console UI, a set of settings affecting the data replication process, including Replication Servers subnet and IP, data throttling, use dedicated replicator, use multiple connections, etc..) Once you have the ProjectA Project is the basic organizational unit for running a CloudEndure solution. ready:

1. Check the box to the left of the specific machines you want to FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. in the original ProjectA Project is the basic organizational unit for running a CloudEndure solution. and move them to the newly created ProjectA Project is the basic organizational unit for running a CloudEndure solution. using the Move X Machines to Another Project option within the Machine Actions menu.
   
   
2. Once all the machines have been moved, switch to the newly created ProjectA Project is the basic organizational unit for running a CloudEndure solution. and repeat the steps in the above Performing the Failover section.
   

   Note: If you were unable to move the machines, then the Project configurations are most likely not identical. Contact Support for additional help.

   Note: If you have already launched a Target machine for the machine you are moving, then you do not need to launch a new Target machine after moving the machine to a new Project.

   
   

Performing a Failback with CloudEndure

In the event of planned or unplanned downtime, begin the FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. process by using the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. to launch recovery machines in your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.

Note: CloudEndure performs most Failover and Failback related operations other than the actual redirection of traffic from the primary site to the Disaster Recovery site.

The mechanism for preparing for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. differs based on your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. and TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure, as defined in the Replication SettingsIn the Console UI, a set of settings affecting the data replication process, including Replication Servers subnet and IP, data throttling, use dedicated replicator, use multiple connections, etc. of your ProjectA Project is the basic organizational unit for running a CloudEndure solution..

The following instructions illustrate how to perform a FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. with the aid of CloudEndure for non-cloud and other cloud infrastructures.

Performing a Failback Using the CloudEndure Console - AWS Source to an AWS Target

Note: This operation can only be performed from an AWS Source or a vCenter Source to an AWS Target.

Note: Users that only want to Failback a subset of their machines will have to follow the steps in the Performing a Failback by Moving Machines to a new Project section.

Note: In order to perform a fully orchestrated Failback from a vCenter Source, you must select vCenter as the Source infrastructure in your Replication Settings after installing the CloudEndure vCenter Appliance as described here.

After performing a successful FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time., you will want to FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. your machines. CloudEndure allows you to prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. by reversing the direction of Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. from the Target machineThe Machine created during Test, Cutover or Recovery. back to the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine.. The CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. will then treat the currently launched TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines as SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines and data will flow from your selected TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure back to your original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure.

Note: Traffic flow direction remains from the original Source site to the original Target site.

You can perform the Prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. action by following these steps:

1. Click on the PROJECT ACTIONS menu and select Prepare for Failback
   
   
   

   Note: You can only initiate the Prepare for Failback action once all of the Source machines in the Project have launched Target machines in either Test or Recovery mode.

   
   
2. Click CONTINUE on the Prepare for Failback prompt.
   
3. Once the action is performed the ProjectA Project is the basic organizational unit for running a CloudEndure solution. will display Preparing for failback to original Source next to the CloudEndure Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. ProjectA Project is the basic organizational unit for running a CloudEndure solution. type and the machines will display Initiating Data Replication under the DATA REPLICATION PROGRESS column. The direction of Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. will be reversed and your machines will be failed back from your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). back to your SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure..
   
   The machines will undergo the entire initiation process until they reach Continuous Data Protection status under the DATA REPLICATION PROGRESS column.
   

4. [vCenter as a Source infrastructure only] You must edit the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. Settings of any ProjectA Project is the basic organizational unit for running a CloudEndure solution. prior to performing the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover.. These settings will be used as a template for the Replication SettingsIn the Console UI, a set of settings affecting the data replication process, including Replication Servers subnet and IP, data throttling, use dedicated replicator, use multiple connections, etc. of each of your machines when you perform a FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover..

   1. To change the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. settings, navigate to the Setup & Info tab on the left-hand navigation menu and click on FAILBACK SETTINGS.

      
      

   2. Edit the settings as desired and then click SAVE FAILBACK SETTINGS on the bottom right of the page.
      
      

5. After performing the Prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. action, you can edit the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. Settings and Back to Normal settings of your individual machines.

   1. Click on the name of a machineA physical or virtual computer. to edit its FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. Settings.

      
      

   2. The Machine Details View for the specific machineA physical or virtual computer. will open. Navigate to the FAILBACK SETTINGS tab to edit the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. Settings for this machineA physical or virtual computer..
      

   3. You can edit a variety of settings for the machineA physical or virtual computer.. These settings will be used as a template for machineA physical or virtual computer. replication settingsIn the Console UI, a set of settings affecting the data replication process, including Replication Servers subnet and IP, data throttling, use dedicated replicator, use multiple connections, etc.. The available settings differ based on your infrastructure. All settings can be changed other than the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. and TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery).. You can learn more about platform-specific settings in the Replication Settings documentation.
      

   4. Edit the settings as desired and then click SAVE FAILBACK SETTINGS on the bottom right of the page.
      
6. You will now need to launch new TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines for your failed back machines. Check the box to the left of each machineA physical or virtual computer. name, click the LAUNCH TARGET MACHINES menu, and select Recovery Mode.
   
   

   Note: Stop all operational services on the Source machine prior to Failback.

   
   
7. Click NEXT on the Launch Target Instance dialog.
   

   Note: Any previous Target machines launched for the Source machines you are testing will be deleted.

   
   
8. Select the Latest Recovery PointA specific point within the Point-in-Time Recovery function. and click CONTINUE WITH LAUNCH.
   
   
9. Once the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines have been launched, click the PROJECT ACTIONS menu and select Return to Normal Operation to reverse the direction of Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. back to its normal state (original SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. to original TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery)..)
   
   
   
10. Click CONTINUE on the Return to Normal dialog.
    
11. Your machines will yet again undergo the initiation sequence.
    
    
12. Once your machines enter Continuous Data Protection mode, the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process has been successfully completed.
    
    

Failing Back specific machines

In certain cases, you may want to perform a failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. for a single machineA physical or virtual computer. (or various - but not all - machines) in a ProjectA Project is the basic organizational unit for running a CloudEndure solution. with multiple machines (AWS SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. or a vCenterVMWare's virtual environment management platform. SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. to an AWS TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery)..)

This can be achieved by moving the desired machines into a separate ProjectA Project is the basic organizational unit for running a CloudEndure solution. and performing the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. as discussed in the Performing a Failback Using the CloudEndure Console section above.

You can move a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. from one ProjectA Project is the basic organizational unit for running a CloudEndure solution. to another. When a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. is moved to another ProjectA Project is the basic organizational unit for running a CloudEndure solution., the replication of its data continues without major interruptions (except for a small backlogAccumulation over time of changes in a Source machine, which are waiting to be replicated to the Target location.). A backlogAccumulation over time of changes in a Source machine, which are waiting to be replicated to the Target location. occurs, but no re-scan or sync is performed. The Blueprint of the machineA physical or virtual computer. is maintained without change.

In order to move a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. from one ProjectA Project is the basic organizational unit for running a CloudEndure solution. to another, the two ProjectsA Project is the basic organizational unit for running a CloudEndure solution. need to match. The criteria for matching ProjectsA Project is the basic organizational unit for running a CloudEndure solution. are as follows:

• CloudEndure AccountThe entity that signed up with CloudEndure. - to match, the ProjectsA Project is the basic organizational unit for running a CloudEndure solution. must belong to the same CloudEndure AccountThe entity that signed up with CloudEndure..
• Cloud account – at times, there are several accounts on the same AWS cloud. To match, the ProjectsA Project is the basic organizational unit for running a CloudEndure solution. must belong to the same cloud account, both on the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. and the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructures.
• Solution type – either MigrationThe CloudEndure solution that allows you to move data, applications, and other business elements from an onsite network or a cloud environment to another physical location or cloud environment. or Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event.. To match, the ProjectsA Project is the basic organizational unit for running a CloudEndure solution. must belong to the same solution type.
• SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. infrastructure (including region) and TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure (including region) – to match, the ProjectsA Project is the basic organizational unit for running a CloudEndure solution. must have the same SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. and TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructures and regions
• License PackageIncludes the licenses that are required for installing Agents on your Source machines. – to match, the same License PackageIncludes the licenses that are required for installing Agents on your Source machines. must be applied to both ProjectsA Project is the basic organizational unit for running a CloudEndure solution..

You cannot move a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. that is in the middle of a JobDesignates several procedures within the CloudEndure Console, including launching Test or Recovery machines, the deletion of Target machines, and other tasks. (launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. a TestThe same for Migration and Disaster Recovery. A process that is initiated manually. Launches Target machines on the Target location, and marks the tested machines on the Console as ready for Live Migration/Disaster Recovery. It is recommended to initiate a Test after the initial replication is completed. When a Test is initiated, an updated snapshot is created on the Staging Aaea. From this snapshot, a disk is created. or a Recovery machineA physical or virtual computer., deleting TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines), or if the AccountThe entity that signed up with CloudEndure. is currently being upgraded. If you want to move a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. to a ProjectA Project is the basic organizational unit for running a CloudEndure solution. that does not match its existing project, do the following:

• Uninstall the AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. from the machines
• Open the new ProjectA Project is the basic organizational unit for running a CloudEndure solution. and install the AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. of that ProjectA Project is the basic organizational unit for running a CloudEndure solution. on the machines.

Moving the Machines

1. From the Project list, select the ProjectA Project is the basic organizational unit for running a CloudEndure solution. that includes the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. you want to move.
   
   
2. Open the Machines page, and check the box next to the name of the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines you want to move.
   

   Note: You can move multiple machines at once by selecting them on the Machines page.
   
   

3. Click the MACHINE ACTIONS button, and select the Move X Machine to Another Project option.
   
   
4. The Move machine to another Project dialog box will appear. Open the Move drop-down list and select the destination ProjectA Project is the basic organizational unit for running a CloudEndure solution. to which the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. will move. Click MOVE MACHINES.
   
   

   Note: Projects that are not listed do not match the criteria.

5. The selected Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. will be moved to the destination ProjectA Project is the basic organizational unit for running a CloudEndure solution., and it will no longer appear on the Machines page of the original ProjectA Project is the basic organizational unit for running a CloudEndure solution.. A message will appears on the upper right corner, informing you that X machine moved.
   
   When you select the destination ProjectA Project is the basic organizational unit for running a CloudEndure solution. from the Project list, the moved machineA physical or virtual computer. will appear on its Machines page. From there, continue with the steps in the Performing a Failback Using the CloudEndure Conosle section.

Performing a Failback Using the CloudEndure Failback Client - Non cloud or other cloud Source to an AWS Target

Important! The Failback ClientThe software used with Failback in Disaster Recovery. requires at least 4 GB of dedicated RAM.

Note: This operation can only be performed from a non-cloud or other cloud Source infrastructure to an AWS Target.

Note: Failing back to your original non-AWS Source is only possible when the Source infrastructure is set to Other Infrastructure .

Note: Stop all operational services on the Source machine prior to Failback.

Note: The Failback Client supports both UEFI and BIOS boot options. Ensure that the machine on which you run the Failback Client is configured to boot with the same configuration (UEFI or BIOS) at the Target instance on AWS. The Failback Client will display the Booting Failback client in [UEFI / BIOS] mode. Make sure that this is compatible with the EC2 instance boot mode message.

You can perform the Prepare for FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. action by following these steps:

1. Click on the PROJECT ACTIONS menu and select Prepare for Failback
   .
   

Note: You can only initiate the Prepare for Failback action once all of the Source machines in the Project have launched Target machines in either Test or Recovery mode.

2. Click CONTINUE on the Prepare for Failback prompt.
   
3. Once the action is performed the ProjectA Project is the basic organizational unit for running a CloudEndure solution. will display Preparing for failback to original Source next to the CloudEndure Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. ProjectA Project is the basic organizational unit for running a CloudEndure solution. type.
   
   The machines in the Machine List View will display Waiting for boot from Failback Client under the DATA REPLICATION PROGRESS column.
   
   The Machine Details View for the machines being failed back will also indicate that it's Waiting for boot from the Failback Client. The Machine Details View will show all of the steps that the Failback ClientThe software used with Failback in Disaster Recovery. will undergo during the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process. Use this view to monitor the progress of the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. and to troubleshoot any issues.
   
   
4. Download the Failback ClientThe software used with Failback in Disaster Recovery., using the link from the Replication Settings section in the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. under Setup & Info. You can access the link by clicking on Learn more about failing back to "Other Infrastructure" and then clicking download from here on the Failing Back to an Unidentified Cloud / Other Infrastructure dialog. The file will be downloaded automatically.
   
   
   

   Note: Download the latest copy of the Failback Client prior to initiating a Failback.

   
   
5. To initiate replication of a Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine., the Target machineThe Machine created during Test, Cutover or Recovery. needs to be booted into the CloudEndure Failback ClientThe software used with Failback in Disaster Recovery. Image (failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover._livecd.iso)
6. The Failback ClientThe software used with Failback in Disaster Recovery. interface will launch and connect to the DHCP client. Upon connection, you will be prompted for your CloudEndure Installation Token. Input your installation token into the Failback ClientThe software used with Failback in Disaster Recovery..
   
   

   Note: You can locate your installation token by navigating to Setup & Info > Other Settings > Installation Token in the CloudEndure Console.

   
   
   
7. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to automatically detect your instance.
   
   If the Failback ClientThe software used with Failback in Disaster Recovery. is unable to automatically detect your instance, then it will ask you to manually map the instance by selecting the instance from a list of available instances.
   
   If the Failback ClientThe software used with Failback in Disaster Recovery. is unable to fetch a list of available instances, it will ask you to enter the full instance ID manually.
   
   
   You can follow the progress of the Failback ClientThe software used with Failback in Disaster Recovery. in the Machine Details View in the CloudEndure Console. Once you have entered your installation token, authentication has been complete, and the instance has been detected the Authenticate Failback Client and the Determine the EC2 instance to fail back from steps will be marked as complete in the Machine Details View.
   
   
   
   
   

   Note: If the Failback Client is stopped, rebooted, or shut down at any point after the completion of this step, the CloudEndure Console with display a Communication with the Failback Client lost under the DATA REPLICATION PROGRESS column in the Machine List View.

8. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to automatically map the volumes on your machineA physical or virtual computer.. If successful, then the Failback ClientThe software used with Failback in Disaster Recovery. will indicate that the volumes were mapped successfully and show the exact volume mapping that will be used.
   
   If the Failback ClientThe software used with Failback in Disaster Recovery. fails to map the volumes automatically, then you will be requested to map the volumes manually.
   
   Enter a local block device (e.g. /dev/sdg) to replicate from the remote block device or use the EXCLUDE command to exclude a device. The Failback ClientThe software used with Failback in Disaster Recovery. will indicate if the manual mapping is invalid and will state a reason, such as volume size mismatches, a lack of a root-level block volume, non-existant volume, or a volume that cannot be read.
   
   Once the volumes have been mapped, the Complete Volume Mapping step will be marked as complete in the Machine Details View.
   
9. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to download the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks..
   
   If the Failback ClientThe software used with Failback in Disaster Recovery. fails to download the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks., it will retry to download the software three more times. If the download still fails, then an error message will be displayed. The Failback ClientThe software used with Failback in Disaster Recovery. will indicate exactly which software package it failed to download.
   
   The download may fail due to various reasons, including lack of connectivity to s3, a network disconnect, or a lack of connectivity to the CloudEndure Service ManagerThe CloudEndure server.. Ensure that you have the correct connectivity settings configured and then rerun the Failback ClientThe software used with Failback in Disaster Recovery..
   
   Once the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks. has been downloaded, the Download the CloudEndure Replication Software to the Failback Client step will be marked as complete in the Machine Details View.
   
10. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to configure the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks..
    
    If the Failback ClientThe software used with Failback in Disaster Recovery. fails to configure the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks., then that means that the software was not installed properly. Rerun the Failback ClientThe software used with Failback in Disaster Recovery. (by rebooting the machineA physical or virtual computer. with the Failback ClientThe software used with Failback in Disaster Recovery. ISO).
    
    Once the CloudEndure Replication SoftwareThe software that is downloaded from the Console by the Replication Servers. It runs on the Replication Servers and it is responsible for writing the replicated data to the Staging area disks. is configured, the Configure CloudEndure Replication Software step will be marked as complete in the Machine Details View.
    
11. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to verify EC2 instance connectivity to the CloudEndure Service ManagerThe CloudEndure server..
    
    If the initial connection fails, then the Failback ClientThe software used with Failback in Disaster Recovery. will retry the connection. If the Failback ClientThe software used with Failback in Disaster Recovery. isn't able to verify connectivity after retrying, then you will need to ensure that the Security GroupThe Security Group is an AWS feature that acts as a virtual firewall, which controls the inbound and outbout traffic of the Staging area. attached to the EC2 instance allows 443 outbound connectivity and ensure that you have the correct connectivity settings configured . The Establish communication between the EC2 instance and the CloudEndure Service Manager step in the Machine Details View in the CloudEndure Console will indicate that this step is stuck until connectivity is verified.
    
    Once connectivity is verified, the Establish communication between the EC2 instance and the CloudEndure Service Manager step will be marked as complete in the Machine Details View.
    
12. The Failback ClientThe software used with Failback in Disaster Recovery. will attempt to pair with the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. running on the EC2 instance.
    
    If the Failback ClientThe software used with Failback in Disaster Recovery. failed to pair with the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. running on the EC2 instance, then you should contact Support.
    
    Once the Failback ClientThe software used with Failback in Disaster Recovery. is paired with the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. running on the EC2 instance, the Pair the CloudEndure Agent with the CloudEndure Replication Software step will be marked as complete in the Machine Details View.
    
    
    
13. Finally, the Failback ClientThe software used with Failback in Disaster Recovery. will attempt to establish a connection with the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. running on your EC2 instance over port 1500. Once connection is established, replication will begin immediately.
    
    The Failback ClientThe software used with Failback in Disaster Recovery. will continuously attempt to connect until connectivity is established. If the Failback ClientThe software used with Failback in Disaster Recovery. fails to connect, then you will need to ensure that the Security GroupThe Security Group is an AWS feature that acts as a virtual firewall, which controls the inbound and outbout traffic of the Staging area. attached to the EC2 instance allows 1500 inbound connectivity and ensure that you have the correct connectivity settings configured . The Establish communication between the CloudEndure Agent and the CloudEndure Replication Software step in the Machine Details View in the CloudEndure Console will indicate that this step is stuck until connectivity is established.
    
    
    Once a connection is established, replication will begin immediately. You will most likely not see the Establish communication between the CloudEndure Agent and the CloudEndure Replication Software marked as complete in the Machine Details View.
    
    Instead, you will see Initial Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. starting, on both the Machine Details View and the main Machine List View.
    
    
    
    
14. When initial replication is completed, the User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. will indicate that replication is in Continuous Data Protection mode. You will now need to launch new TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines for your failed back machines. Check the box to the left of each machineA physical or virtual computer. name, click the LAUNCH TARGET MACHINES menu, and select Recovery Mode.
    
    

    Note: You can also launch the Target machine from the Machine Details View.

    
    
    
15. Click NEXT on the Launch Target Instance dialog.
    

    

    
    
16. Select the Latest Recovery PointA specific point within the Point-in-Time Recovery function. and click CONTINUE WITH LAUNCH.
    
    
17. When the TestThe same for Migration and Disaster Recovery. A process that is initiated manually. Launches Target machines on the Target location, and marks the tested machines on the Console as ready for Live Migration/Disaster Recovery. It is recommended to initiate a Test after the initial replication is completed. When a Test is initiated, an updated snapshot is created on the Staging Aaea. From this snapshot, a disk is created. or the Recovery are finished, the Failback ClientThe software used with Failback in Disaster Recovery. will indicate that the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. has been finished and that the machineA physical or virtual computer. will be rebooted. The Target machineThe Machine created during Test, Cutover or Recovery. will eject the Failback ClientThe software used with Failback in Disaster Recovery. and reboot into the new operating system.
    
    Once all machines are recovered, select Project Actions and click Return to Normal Operation. At the end of the operation, the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. project is configured to replicate into the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure again. The machines will start replicating into the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.
    
    
18. Click CONTINUE on the Return to Normal dialog.
    
19. Your machines will yet again undergo the initiation sequence.
    
    

20. Once your machines enter Continuous Data Protection mode, the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process has been successfully completed.
    

Additional Failback Client Troubleshooting

The following are additional troubleshooting steps for various Failback ClientThe software used with Failback in Disaster Recovery. errors and issues.

Errors when failing back to different source machine

If you're failing over to AWS from one Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. and then failing back from AWS to a different source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine., you may encounter replication issues after completing Steps 17-18 above (Return to Normal). The machineA physical or virtual computer. may be stuck at the Initiating Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. stage without data replication progress.

To fix this issue, reinstall the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. on the new (different) Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine.. Replication should start automatically and the machineA physical or virtual computer. should reach CDPA method of replicating data in real time from one location to another. CDP works by capturing every change to any block on a storage volume in real time, and sending it immediately to a remote location. Traditional enterprise-grade disaster recovery solutions, such as the ones provided by IBM, EMC, NetApp and Microsoft all use CDP for storage or hypervisor replication..

Unexpected error after volume mapping

If you receive the message "There was an unexpected error that caused replication to stop" after mapping volumes (Step 8 above), it could be due to a login time out in the failbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process. Rerun the Failback ClientThe software used with Failback in Disaster Recovery. and complete the entire process without lengthy interruptions (hours in between steps) to avoid this issue.

Connection with Failback Client Lost message

The DATA REPLICATION PROGRESS in column in the Machine List View may show "Communication with Failback ClientThe software used with Failback in Disaster Recovery. lost" after booting the machineA physical or virtual computer. through the Failback ClientThe software used with Failback in Disaster Recovery. and going through the Failback ClientThe software used with Failback in Disaster Recovery. steps if you're using an old version of the Failback ClientThe software used with Failback in Disaster Recovery..

Ensure that you're using the latest version of the Failback ClientThe software used with Failback in Disaster Recovery. by downloading the Failback ClientThe software used with Failback in Disaster Recovery. ISO file as indicated in Step 4 above. Boot the machineA physical or virtual computer. with the newly downloaded ISO and complete the FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. process.

Failback Notes

Review the following notes prior to initiating a FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover..

Note: The Failback will launch new machines. After the new machines have been launched, the old original Source machines need to be cleaned up manually as CloudEndure never deletes Source machines. If the Failback Client is launched on an Other Infrastructure (non-AWS) Source, then the same machine will function as the Target and should not be deleted.

Note: When your Target machine is Openstack-based, create a standard disk from the Failback Client ISO file, and boot from that standard disk, instead of attaching the ISO directly.

Note: In Azure (ARM), skip drive D: during Failback, as Azure (ARM) automatically adds a 128GB temporary disk to the new machine (on drive D:) which can cause the Failback to fail or take a very long time.