Hi all, You all watching this video might be thinking of failback process too. I had few doubts regarding failback, so I opened a support case with AWS (using my corporate account as we don't get technical support in free tier account). As per the update I received from AWS: Currently EC2 instance can't be booted off the ISO image hence at this moment it is not possible to do failback when we have DR setup between the AWS regions. As VMWare and other cloud providers support booting their machine with ISO image, hence it is possible to do a failback when the source is VMWare or other cloud provider. AWS support team also mentioned that the automatic and fully orchestrated failback features (like Cloudendure) will be added to the AWS Elastic Disaster Recovery in future. So at this moment I am unable to make a video on failback as I have limited access to AWS only. Once I have supported resource as mentioned above by AWS support team( like VMWare ), I will try to bring failback video too. Till then happy learning :)
@@conceptsofcloud9303 I got the answer here from AWS. In scenarios Cloud to Cloud, there is no failback Agent. You need to perform the Drill, delete the source servers and then setup the target servers to perform a new Drill back to the original location. Very manual and confusing. If i can say, Azure Site Recovery is very ahead.
everything spoken was truth and correct until you made mistake when talking about the Failback process . When we do the Failback from one Region to another or simply from one AWS Account to another, we don't need to install any kind of Agent on the SOurce Server for failback ; we can simply click on Failback or start Reversed Replication and Voila !!!! But when we do the failback for On-prem Server , we need to boot it through the Failback Clicent ISO image .
Hello ,Thank you for this informative video, can you please do a failback on a windows instance, on your corp account,you can pause the recordings ,High level steps,will you consider doing something like this,thanx
Very informative. Thank you very much! Just curious, since it's creating a conversion server and terminate it right away before it launch a recovery instance, will that incur charges separately (the conversion server)?
In the AWS documentation it is mentioned that "You can perform a *cross-Region* or cross-AZ failover and failback directly with the aid of the DRS Console." But at 6:34 you mentioned that failback is not possible from one region to another region? Can you please cross check that part?
Glad that you asked. Please read answer to below question in FAQ at aws.amazon.com/disaster-recovery/faqs/ "What can I do using CloudEndure Disaster Recovery that I cannot do using AWS Elastic Disaster Recovery?" Still you have doubts feel free to write, I will try to help
@@conceptsofcloud9303 The failback match with the replication instace, but it says something like this "could not connect, check your network configuraton, trying in 1minute" I think it might be related with 1500 port, because I don't know how to connect it
@@conceptsofcloud9303 Hi, at that time i was bit confused but later got to know that while installing replication agent we should give region name where we want to recover our source instance. I.e if application instance is in us-east-1 and if you want to replicate that instance to us-west-2 then then you should give region name as us-west-2 while installing replication agent
Theoretically steps would be same. I will try to bring that demo at least till Failover. Since EDR is new AWS service they are still enhancing this service
@@conceptsofcloud9303 I'd like to see a video where you run the failback client on cloud machines. This is currently not possible as the failback client is an iso and not a binary to run. Are there any solutions for this?
The only work around I can see is, treat failover server as source machine and perform all the steps as if we are performing failover operation on new machine. But this is manual process and we can never failover to our desired machine(server). This is just a workaround and we can't compare it to failback
@@conceptsofcloud9303 I'm talking about the Failback client livecd. It is not easy to use it on machines where it is not possible to load a livecd iso. It is not easy to run binaries (extracted from the iso) correctly on a machine in another cloud provider such as AZURE or Oracle for example. it would be very helpful to find a solution
My "initial sync" keeps failing on the "Authenticate with service" step. Any idea what could be wrong? I've verified the access and secret keys, and have tried a second time, with the same result. I followed the troubleshooting guide in the AWS docs, no luck. I checked the agent logs at /var/lib/aws-replication-agent/agent.log.0, i see one warning: "WARNING Agent - migration script is missing for platform {'dist': ('amzn', '2', ''), 'system': 'Linux', 'release': '4.14.177-139.254.amzn2.x86_64'".
Did you get this resolved? I have the exact same issue. Can't seem to get past the "Authenticate with service" step. the cloud trail logs aren't particularly helpful in finding the issue either.
I guessed you want to do the Replication through the Private Connectivity and because of that you launched your replication server on Private Subnet ; now what you need to do is that you need to Setup the DRS endpoint, EC2 Endpoint , S3 endpoint and S3 Interface Endpoint and open port 1500 and 443 from the Replication Server SG.
![[Full Episode] The Restaurant War Thailand ศึกพ่อค้าซ่าแม่ค้าแซ่บ Episode 4 | 13 ต.ค. 67](http://i.ytimg.com/vi/h8N9tY46P-M/mqdefault.jpg)
Hi all,
You all watching this video might be thinking of failback process too. I had few doubts regarding failback, so I opened a support case with AWS (using my corporate account as we don't get technical support in free tier account). As per the update I received from AWS:
Currently EC2 instance can't be booted off the ISO image hence at this moment it is not possible to do failback when we have DR setup between the AWS regions.
As VMWare and other cloud providers support booting their machine with ISO image, hence it is possible to do a failback when the source is VMWare or other cloud provider. AWS support team also mentioned that the automatic and fully orchestrated failback features (like Cloudendure) will be added to the AWS Elastic Disaster Recovery in future.
So at this moment I am unable to make a video on failback as I have limited access to AWS only. Once I have supported resource as mentioned above by AWS support team( like VMWare ), I will try to bring failback video too.
Till then happy learning :)
any news here?
unfortunately no.
@@conceptsofcloud9303 I got the answer here from AWS. In scenarios Cloud to Cloud, there is no failback Agent. You need to perform the Drill, delete the source servers and then setup the target servers to perform a new Drill back to the original location. Very manual and confusing. If i can say, Azure Site Recovery is very ahead.
@@conceptsofcloud9303 Is there a way you can show us how to redirect traffic from source server to recovery instance during failover
everything spoken was truth and correct until you made mistake when talking about the Failback process . When we do the Failback from one Region to another or simply from one AWS Account to another, we don't need to install any kind of Agent on the SOurce Server for failback ; we can simply click on Failback or start Reversed Replication and Voila !!!! But when we do the failback for On-prem Server , we need to boot it through the Failback Clicent ISO image .
thank you for sharing this. very helpful
Thank you for sharing such useful information.
Hello ,Thank you for this informative video, can you please do a failback on a windows instance, on your corp account,you can pause the recordings ,High level steps,will you consider doing something like this,thanx
Good to understanding videos clearly
🥳
Can we configure cloudwatch to replication server and recovery server
This is gem
Thank u bro
Very informative. Thank you very much! Just curious, since it's creating a conversion server and terminate it right away before it launch a recovery instance, will that incur charges separately (the conversion server)?
Glad to know it helped you.
Yes it do incur charges, but the amount would be minimal.
Awesome!!!
bro plz make videos on firewall manager network firewall n advanced vpc networking concepts
Hi, can i take backup of EKS cluster using aws DR. is that possible ?
Thanks a lot for the awesome knowledge base
how to check installed AWS EDR version in Rhel and windows servers
In the AWS documentation it is mentioned that "You can perform a *cross-Region* or cross-AZ failover and failback directly with the aid of the DRS Console." But at 6:34 you mentioned that failback is not possible from one region to another region? Can you please cross check that part?
Glad that you asked.
Please read answer to below question in FAQ at aws.amazon.com/disaster-recovery/faqs/
"What can I do using CloudEndure Disaster Recovery that I cannot do using AWS Elastic Disaster Recovery?"
Still you have doubts feel free to write, I will try to help
What is meant by the term drill?
I am getting an error while installing the AWS EDR agent.
I have network problems and I don't now why, I have my replication agent all set, but the failback doesn't want to work, any idea?
Kindly check you IAM permission and security group rules. If needed do check AWS Elastic DR documentation.
@@conceptsofcloud9303 The failback match with the replication instace, but it says something like this "could not connect, check your network configuraton, trying in 1minute" I think it might be related with 1500 port, because I don't know how to connect it
What if we need on premise server to have disaster recovery and fail over. How do we go about this?
We need to follow same steps, with all the required permissions granted
@@conceptsofcloud9303 how about activating failover and fall back?
hi , thankyou for demo, can you please demo for failback as well? :)
Hi Ridwan, I hope this video was helpful. Sure, will make a video on failback soon. Happy learning :)
@@conceptsofcloud9303 please share failback process. That will be more informative as failback process is very rare over the internet. Please 🙏
Nice
Thanks Man.
Where are settings to launch recovery instance in another region?
Sorry I didn't get your question, please elaborate
@@conceptsofcloud9303 Hi, at that time i was bit confused but later got to know that while installing replication agent we should give region name where we want to recover our source instance. I.e if application instance is in us-east-1 and if you want to replicate that instance to us-west-2 then then you should give region name as us-west-2 while installing replication agent
Yeah, you got it right
Can you share demo from VMware to AWS Cloud Failover and Failback
Theoretically steps would be same. I will try to bring that demo at least till Failover. Since EDR is new AWS service they are still enhancing this service
@@conceptsofcloud9303 I'd like to see a video where you run the failback client on cloud machines. This is currently not possible as the failback client is an iso and not a binary to run. Are there any solutions for this?
The only work around I can see is, treat failover server as source machine and perform all the steps as if we are performing failover operation on new machine. But this is manual process and we can never failover to our desired machine(server). This is just a workaround and we can't compare it to failback
@@conceptsofcloud9303 I'm talking about the Failback client livecd. It is not easy to use it on machines where it is not possible to load a livecd iso. It is not easy to run binaries (extracted from the iso) correctly on a machine in another cloud provider such as AZURE or Oracle for example. it would be very helpful to find a solution
Kindly share the AWS elastic disaster failback process
I am working on it
@@conceptsofcloud9303 thanks a lot. If possible also show us cloud endure failover n failback process
Excellent video. Keep it up sir. ☺️
Sir any expected time to launch failback video ? :)
kindly show the failback process . we are awaiting.
Kindly share cloud endure data migration process :)
how can I get in touch with you.
You can write me at conceptsofcloud@gmail.com
source server is On-premise server please share the steps.
Steps would be same only
You can refer this link for more details docs.aws.amazon.com/drs/latest/userguide/source-servers.html
My "initial sync" keeps failing on the "Authenticate with service" step. Any idea what could be wrong? I've verified the access and secret keys, and have tried a second time, with the same result.
I followed the troubleshooting guide in the AWS docs, no luck.
I checked the agent logs at /var/lib/aws-replication-agent/agent.log.0, i see one warning: "WARNING Agent - migration script is missing for platform {'dist': ('amzn', '2', ''), 'system': 'Linux', 'release': '4.14.177-139.254.amzn2.x86_64'".
Kindly check IAM and security group rules
It could be your settings, if you’re launching your replication server in private subnet. Try to select no public IP.
Did you get this resolved? I have the exact same issue. Can't seem to get past the "Authenticate with service" step. the cloud trail logs aren't particularly helpful in finding the issue either.
I guessed you want to do the Replication through the Private Connectivity and because of that you launched your replication server on Private Subnet ; now what you need to do is that you need to Setup the DRS endpoint, EC2 Endpoint , S3 endpoint and S3 Interface Endpoint and open port 1500 and 443 from the Replication Server SG.