Farewell Cloud Endure, Hello AWS DRS

1. Download the Assessment Tool using the following command:
   wget https://cedr-to-drs-upgrade-tool.cloudendure.com/latest/cloudendure_to_drs_upgrade_assessment_tool
2. Change the permissions using the following command:
   sudo chmod +x cloudendure_to_drs_upgrade_assessment_tool
3. Run the following command with above variables
   sudo ./cloudendure_to_drs_upgrade_assessment_tool –api-token [api_token] --project-id [12345xx-0000-0000-0000-00aa00ab00b0]
   or use below command which uses username and password
   sudo ./cloudendure_to_drs_upgrade_assessment_tool --username [[email protected]] --password [my_secret_password] --project-id [12345xx-0000-0000-0000-00aa00ab00b0]

1. Download the Assessment Tool from following URL:
   https://cedr-to-drs-upgrade-tool.cloudendure.com/latest/cloudendure_to_drs_upgrade_assessment_tool.exe
2. Run the following command in Power Shell with the variables
   .\cloudendure_to_drs_upgrade_assessment_tool –api-token [api_token] --project-id [12345xx-0000-0000-0000-00aa00ab00b0]
   or use below command which uses username and password
   .\cloudendure_to_drs_upgrade_assessment_tool --username [[email protected]] --password [my_secret_password] --project-id [12345xx-0000-0000-0000-00aa00ab00b0]

   Once the assessment is complete (which usually takes 8-10 mins), the Assessment Tool will display the assessment results, including which machines are:

   • Eligible for DRS upgrade as-is
   • Eligible but have warnings that must be addressed
   • Ineligible for upgrade
   
   

   The Assessment Tool will create a folder in the same directory where the tool was installed called ‘output’ and a CSV that lists all the warnings, errors, and mitigations will be stored.

Here are some common warnings and their descriptions for troubleshooting that you may encounter:

• CreatingNewSubnetUnsupported: This warning arises if the Subnet settings in the CEDR blueprint are configured to "Create New." To resolve, either select an existing subnet in the Blueprint settings or leave it unchanged, and the launch template in DRS will not be associated with a Subnet.
• CreatingNewSecurityGroupsUnsupported: This warning occurs when the Security Group settings in the CEDR blueprint are set to "Create New." To address this, choose an existing Security Group in the Blueprint settings or leave it as is to ensure that the launch template in DRS does not have an associated Security Group.
• CustomConverterTypeUnsupported: This warning is triggered if a specific converter instance type is selected in the replication settings. opt for the default instance type to resolve this warning.
• IAMRolesRequireRecoveryInstancePermissions: This warning appears if an IAM Instance Profile is defined in the Blueprint. To support failback, ensure that all recovery instances have the AWSElasticDisasterRecoveryRecoveryInstancePolicy policy attached to the instance profile role.
• MachineSettingsNotSupported: This warning requires careful consideration, and resolution may involve seeking assistance from AWS Support.

Except for the machine settings warning, all the above-mentioned warnings can be ignored.

1. Download the Upgrade Tool using the following command:
   wget https://cedr-to-drs-upgrade-tool.cloudendure.com/latest/cloudendure_to_drs_upgrade_tool
2. Change the permissions using the following command:
   sudo chmod +x cloudendure_to_drs_upgrade_tool
3. Run the following command with above variables
   sudo ./cloudendure_to_drs_upgrade_tool start-upgrade --api-token [api_token] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings
   or use below command which uses username and password
   sudo ./cloudendure_to_drs_upgrade_tool start-upgrade --username [[email protected]] --password [my_secret_password] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings

1. Download the Upgrade Tool using the following command:
   https://cedr-to-drs-upgrade-tool.cloudendure.com/latest/cloudendure_to_drs_upgrade_tool
2. Run the following command on PowerShell with above variables
   .\cloudendure_to_drs_upgrade_tool start-upgrade --api-token [api_token] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings
   or use below command which uses username and password
   .\cloudendure_to_drs_upgrade_tool start-upgrade --username [[email protected]] --password [my_secret_password] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings

   If at this point there is a situation of disaster, the recovery instance could be initiated using Cloud Endure from retained snapshots, but all new snapshots will be taken in DRS. The RPO will be less than 24 hours for this scenario.

   After completing the installation, the machine will be added to DRS on the Source servers page with a ‘lag’ because only one snapshot is replicated. The lag will disappear once we successfully complete the finalize upgrade phase.

   When the status changes to ‘Ready’ initiate the drill and select the most recent data and initiate a drill.

   The launched Drill instance on the ‘Recovery instances’ page in DRS. Test the server's connectivity and make sure it works as required. If there are any issues, review your settings, change the blueprint, and perform the necessary troubleshooting steps. Once the tests are completed successfully, move on to the finalize-upgrade step.

For “libz.so.1: failed to map segment from shared object: Operation not permitted” error:

• The error can be solved by remounting /tmp with exec permission and changing it back to noexec as it is a security best practice.
  sudo mount -o remount,exec /tmp
sudo mount -o remount,noexec /tmp

1. Run the following command variables
   sudo ./cloudendure_to_drs_upgrade_tool finalize-upgrade --api-token [api_token] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings
   or use below command which uses username and password
   sudo ./cloudendure_to_drs_upgrade_tool finalize-upgrade --username [[email protected]] --password [my_secret_password] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings

1. Run the following command on PowerShell with above variables
   .\cloudendure_to_drs_upgrade_tool finalize-upgrade --api-token [api_token] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings
   or use below command which uses username and password
   .\cloudendure_to_drs_upgrade_tool finalize-upgrade --username [[email protected]] --password [my_secret_password] --project-id [project-id] --aws-access-key-id [access_key] –aws-secret-access-key [secret_key] –aws-session-token [session_token] --import-replication-configuration --import-blueprint --import-test-snapshot --ignore-validation-warnings

   Upon executing the provided commands, DRS will initiate a server rescan, replicating all identified disks. The duration of this process may vary, ranging from 4 to 24 hours, contingent on the size of the respective servers.

   After the completion of the rescanning process, the server will be in a healthy state and available for use.