Disaster Recovery Best Practices

You should follow these best practices in order to ensure the optimal functionality of your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. solution:

Planning

1. Plan your Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. project prior to installing machines.
2. Ensure that you review the Blueprint options for your specific Target locationThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery)..

Licensing

1. Ensure that you have sufficient Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. LicensesAllows the installation of the Agent on one machine. One License enables one Agent. Licenses are a part of the License Package. for your ProjectA Project is the basic organizational unit for running a CloudEndure solution.. If you are unsure, then contact Support.

Machine Limit Recommendations

1. We recommend limiting a single CloudEndure ProjectA Project is the basic organizational unit for running a CloudEndure solution. to 300 machines or less, as managing more than 300 machines in a single ProjectA Project is the basic organizational unit for running a CloudEndure solution. can be difficult.
   

   • If you have more than 300 machines, divide them among two or more CloudEndure ProjectsA Project is the basic organizational unit for running a CloudEndure solution..

2. Limit the amount of machines replicated into a single AWS AccountThe entity that signed up with CloudEndure. and RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP. for Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. purposes to 300 or less. Replicating more than 300 machines into a single AWS AccountThe entity that signed up with CloudEndure. and RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP. could cause various issues by hitting AWS API rate limits. In addition, replicating 300 or more machines could create an unmanageable number of EBS and EC2 in the AWS AccountThe entity that signed up with CloudEndure. and RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP..

   • If you want to replicate more than 300 machines, ensure that you utilize multiple AWS AccountsThe entity that signed up with CloudEndure. or several Regions within the same AccountThe entity that signed up with CloudEndure. to limit the number of machines to 300 or less per AccountThe entity that signed up with CloudEndure./RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP..

   Learn more about utilizing different Target account credentials to aid with overcoming machine limits.

Testing

1. Ensure that you perform 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. prior to performing a Recovery.
2. After testing by 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

Failover and Failback

1. Ensure that all SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines in the ProjectA Project is the basic organizational unit for running a CloudEndure solution. have 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 in either 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 or Recovery Mode 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..
2. Ensure that you have downloaded the latest copy of the Failback ClientThe software used with Failback in Disaster Recovery. prior to performing 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. using the CloudEndure Failback ClientThe software used with Failback in Disaster Recovery..
   

   Note: The Failback Client requires at least 4 GB of dedicated ram.

   
   
3. Remember to clean up old SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines after performing 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..

Successful Implementation

The following are the required steps to complete a successful Disaster RecoveryThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. implementation with CloudEndure:

1. Deploy CloudEndure AgentsThe 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 your SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines.
2. Confirm replication reaches Continuous Data Protection mode.
3. 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 launch of 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 regularly.
4. Address any issues that come up, such as Blueprint misconfiguration and limits 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). infrastructure.

Best Practices for Ensuring Project Success

1. Train a field technical team & assign a CloudEndure SME.
2. Share project timelines with CloudEndure.
3. Monitor data replication progress and report any issues in advance.
4. Perform 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. for every machineA physical or virtual computer. in advance, and report issues to CloudEndure.