Cloudendure DR Implementation on AWS

https://www.cloudendure.com/
https://www.cloudendure.com/disaster-recovery/aws/
https://docs.cloudendure.com
https://www.slideshare.net/AmazonWebServices/disaster-recovery-best-practices-and-customer-use-cases-cgs-and-healthquest

SAML SSO: CloudEndure SAML.pdf

Support

·         +1 650 360 0717

·         support@cloudendure.com

CloudEndure can be purchased on AWS Marketplace and subscription costs US$99/month/VM which is billed to our AWS account.

I did the following to configure TM1 application DR with CloudEndure:

• Once CloudEndure subscription was created it also created a CloudEndure login (zoran.gagic@customer.com) and password to manage CloudEndure. Please note we intend to change this to SSO.
• On our AWS account (123456789012) we have IAM credentials for CloudEndure as documented here. 

Configuration Steps

·        1.  The following was configured on CloudEndure console https://console.cloudendure.com/:

• Under AWS Credentials: Enter AWS credentials from previous step into CloudEndure
• Under Replication Settings: 

  

• Under Other Settings: take note of installation token 

2. On source VMs configure proxy

3. Install CloudEndure agent (installed_win.exe -t  installation_token_from_previous_step) as documented: https://docs.cloudendure.com/#Installing_the_CloudEndure_Agents/Installing_the_Agents/Installing_the_Agents.htm

This will start syncing all disks from source VMs to CloudEndure Replication server in our AWS environment, this will take a few hours. When replication is finished you should see the following:

4.  The following was configured on CloudEndure console https://console.cloudendure.com/:

a) Configure AWS blueprint for TM1APPPROD01

                b) Configure AWS blueprint for TM1WEBPROD01

5.  To perform failover test:

a) Ensure Cloudendure is in sync with source VMs

b) Power off VMs (to simulate sudden failure of systems)

c) In CloudEndure console Launch 2 Target Instances in test mode and choose the latest point in time:

d) Choose Point in Time for Recovery:

This will start TM1WEBPROD01 and TM1APPPROD01 on AWS. After several minutes DNS will automatically be update to AWS IP addresses.

·         6. Once DR testing complete

a) On AWS console terminate EC2 instances TM1WEBPROD01 and TM1APPPROD01

b) Power on VMware VMs