AWS needs to come up with a way for replicating VMs from on premise to EC2. just like Microsoft ASR. These presentations are simply an excuse for not having disaster recovery. not all applications are two tired, legacy applications sit on one box only. The server it self may have scripts that may be getting modified every now and then. Plain and simple, AWS currently does not have Disaster recovery where one can simply point the VMs to and be sure that they can be turned on at a moment's notice. Whatever is being told here in this video can be done on any platform anywhere. These are not AWS specific. Replicating database on application level is not a wonder of AWS!!
it is already mentioned explaining architecture as a solution to achieve that. for instance, at 18:45 he mentions 3rd party apps that can work to replicate block by block even if you have updated scripts it is going to be replicated as part of the volume continous replication done by cloudendure.
AWS needs to come up with a way for replicating VMs from on premise to EC2. just like Microsoft ASR. These presentations are simply an excuse for not having disaster recovery.
not all applications are two tired, legacy applications sit on one box only. The server it self may have scripts that may be getting modified every now and then.
Plain and simple, AWS currently does not have Disaster recovery where one can simply point the VMs to and be sure that they can be turned on at a moment's notice.
Whatever is being told here in this video can be done on any platform anywhere. These are not AWS specific. Replicating database on application level is not a wonder of AWS!!
it is already mentioned explaining architecture as a solution to achieve that. for instance, at 18:45 he mentions 3rd party apps that can work to replicate block by block even if you have updated scripts it is going to be replicated as part of the volume continous replication done by cloudendure.