- Newest
- Most votes
- Most comments
Yes, Ofcourse ; We can use the AWS DRS to do the failover/cutover on AWS as well as the failback to the Original Source Server or any new Servers. The thing is that when we perform drills/failover , everything is quite simple , easy, reliable and everything works . But, For Failover process, AWS themselves haven't refined this process and its kinda half-baked . For AWS to AWS, doing failback is easy ; No need to install any kind of Agent or bootable Failback Client ISO ,only just we need to click on "Start reverse Replication " and push the "Failback" option and Voila , it worked; but
the things is different when we do the Failback between On-prem and AWS .We need to boot the On-prem Source server with the bootable Failback Client ISO and put some credentials and it works . But , it's kinda tedious process and not well documented and organized. Sometimes, it ask for Static IP, Default Gateway, Subnet mask while configuring Failback and sometimes it doesn't . Even if we provide those credentials and input, it would shows errors .
Wish AWS makes the Failback process more easy , organized way like those of CloudEndure, or Azure Site Recovery.
Regarding the issue, Could please raise the Support ticket and get the issues resolved.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago