Customer wants to setup a Disaster site on AWS Cloud.
Tools used : Aws Cloud and Cloud Endure.
Tasks to be done on AWS Cloud :
- Create a AWS account for the customer
- Create an IAM user named “ Cloudendure user”
- Attach desired policy as recommended by Cloudendure to the IAM user.
- Create a site to site VPN for the customer’s Data centre to AWS Cloud. 5.Create a VPC 6.Create a Private Subnet 7.Create a security group Tasks to be done at Cloudendure : 1.Create a Cloudendure account and navigate to the dashboard. Choose new project, in the available options choose Disaster recovery.
- Choose setup and info.
- Input the IAM user’s access key and secret key and copy the Cloudendure OS agent link in a notepad, When it prompts copy the Cloudendure generated token in the notepad.
- Mail the contents of the notepad to the customer ( on-prem server admin ) 5.Ask the onpremise server admin to run the contents you mailed in the server( to be set up as DR site in Aws)
- Navigate to replication settings. Choose the desired instance type ( to be replicated in Aws console ),Choose the staging VPC you created in Aws console, Choose the private subnet( as application and database to be present in private subnet) Input the private Ip for the staging server that falls within the subnet range. 7.Choose the communication type as through site to site VPN and choose the VPN you created. 8.Click on done Getting back to AWS console : 1.When you check here you could see a replication instance getting spinned up. Getting back to Cloudendure console: 1.When you check here you could see a instance showing the data flow phases from onprem to Cloudendure. Once this is completed, in Cloudendure you can see Launch target machine. Click it. Give the instance type, instance name ,Subnet,IP, choose cutover option and click on Done. You could see a new machine with the instance name you gave earlier getting spinned up. Wait for a while, you can see now the replication instance that was running earlier getting terminated automatically. You can see now the target machine is running. If you login and check you will find the onpremise server’s data here. The difference between migration and DR setup is when you choose migration as Cloudendure project it will move the Data from your source machine ( can be onpremise or Aws or Azure or any Cloud Account’s machine) to the target machine. When you choose Disaster recovery as Cloudendure project it will copy the data from source machine to target machine. These are the steps involved in DR/ migration using Cloudendure.
(Since medium blog is not free, I have replicated my medium blog here)
Top comments (0)