The Disaster Recovery Process Workflow

The general process is:

1. 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. on 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..
   
2. Configure the Target machineThe Machine created during Test, Cutover or Recovery. Blueprint for each machineA physical or virtual computer..
3. Wait until all machines enter Continuous Data Protection.
4. 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. 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. by creating one or more 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. This will create 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 selected SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines based on machineA physical or virtual computer. and network properties you defined in the Blueprint section for each. 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. does not stop replication.
5. Initiate 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..
6. To recover your data, initiate 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.. This step terminates Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks..
7. Return to normal operations.