Performing a Failback by Moving Machines to a New Project

Users of other infrastructures can 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. through the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. by creating a new ProjectA Project is the basic organizational unit for running a CloudEndure solution. and moving the Failed Over 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 into that ProjectA Project is the basic organizational unit for running a CloudEndure solution..

1. Perform the Recovery operation for any machines that suffered a disaster. This will 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.

2. Create a new 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. ProjectA Project is the basic organizational unit for running a CloudEndure solution. with 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). as Other Infrastructure.

3. Add the 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 to the ProjectA Project is the basic organizational unit for running a CloudEndure solution. by installing 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 them with the installation instructions found in the Machines tab of your 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. ProjectA Project is the basic organizational unit for running a CloudEndure solution..

4. Once the machines have been added, utilize the Migration ClientThe software used in Any-to-Any Migration. to perform 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.:

1. 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 "Other Infrastructure" dialog. The file will be downloaded automatically.
   
   
   

   

    

   
   
   

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

   
   
2. 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 Bootable Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. Image.
3. If the networking settings cannot be fetched using DHCP, the software will request you to manual input the networking configuration needed for connectivity.
4. The CloudEndure Failback ClientThe software used with Failback in Disaster Recovery. will then connect to console.cloudendure.com over TCP Port 443 and authenticate using the CloudEndure credentials that you will be prompted to enter.
5. Follow the instructions and provide all the necessary details, such as: the ProjectA Project is the basic organizational unit for running a CloudEndure solution. name, Machine ID of 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 disk mapping between 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). and the IP address of the Target machineThe Machine created during Test, Cutover or Recovery. 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 send the replicated data.
   

   Note: Ensure that you enter a valid IP address that has internet connectivity and has access to console.cloudendure.com and is accessible from the CloudEndure Agent on TCP Port 1500, over a VPN, or through the internet.

   
   
6. 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 connect to the Target machineThe Machine created during Test, Cutover or Recovery. on TCP Port 1500 to start replication.
7. 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 Replication mode, at which point you can initiate 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 an actual Recovery by using the corresponding buttons in the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions..
8. Note that machines must be in Continuous Data Replication mode before FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover., otherwise, there is no consistent state and CloudEndure will not allow the recovered on-premise machineA physical or virtual computer. to boot in an inconsistent state.
9. 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 Target machineThe Machine created during Test, Cutover or Recovery. should eject the Failback ClientThe software used with Failback in Disaster Recovery. and should reboot the Target machineThe Machine created during Test, Cutover or Recovery. into its new operating system.
10. To return to normal operations, you will need to install 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. into the newly created 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 with the credentials of the newly created 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..