Use AWS DRS to replicate a physical machine to AWS and failback to VMware vSphere
Hi guys,
Recently, I am working on a project that require to implement data backup and restore solution for a MS SQL Database . I use AWS DRS to replicate block level data from a physical machine to AWS then I use the failback feature of DRS to failback the machine to a VMware vSphere cluster. However, when I boot the failback client iso the system show the message "Could not retrieve Failback Client VMware instance UUID". Thus, my question is that is it possible to use AWS DRS to replicate data from a physical machine to AWS and then failback it to VMware vSphere. If you have experience about this issue, please kindly help me.
Thanks, Steven
- 最新
- 最多得票
- 最多評論
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.
相關內容
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前