Migration Best Practices

Following the successful launch of AWS Application Migration (MGN), we plan to start restricting the CloudEndure 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. service starting June 30, 2022. Learn more.

You should follow these best practices in order to ensure the optimal functionality 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. solution:

Planning

1. Plan 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. project prior to installing machines.
2. Do not perform any reboots on the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines prior to a CutoverThe process of transitioning from one system to a replacement system..
3. When scheduling your CutoverThe process of transitioning from one system to a replacement system., ensure that you allow enough time for Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. to complete and for all necessary testing to be carried out.

Licensing

1. Ensure that you have sufficient 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. 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, contact Support.
   

   Important! The expiration date of 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. licenses is 90 days. During this time frame, you need to install the 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, and 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. or a CutoverThe process of transitioning from one system to a replacement system. to migrate the machines 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.

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 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. 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. 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. at least one week before you plan to migrate your SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines. This time frame is intended for identifying potential problems and solving them, before the actual CutoverThe process of transitioning from one system to a replacement system. takes place. After performing the test launch, validate connectivity 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 SSH for Linux or RDP for Windows), and perform acceptance tests for your application. If there are any issues, contact Support.
2. 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 CutoverThe process of transitioning from one system to a replacement system..

Successful Implementation

The following are the required steps to complete a successful 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. 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 ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. 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 a week before the actual CutoverThe process of transitioning from one system to a replacement system..
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). cloud.
5. CutoverThe process of transitioning from one system to a replacement system. the machines on the planned date.
6. Remove SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines from the Console after the CutoverThe process of transitioning from one system to a replacement system. has been completed in order to clean up the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks., reduce costs, and remove no longer needed replication resources.

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 test for every machineA physical or virtual computer. in advance, and report issues to CloudEndure.
5. Coordinate CutoverThe process of transitioning from one system to a replacement system. windows with CloudEndure in advance.