No items found.
Recovery is essential for sustaining your business's core technology services. Dispersed cloud operations teams, fragmented processes, and static documents add to the complex demands of recovering today's cloud environments. Cutover, a collaborative automation SaaS solution, provides a single platform for executable recovery plans, bringing together both automated and manual tasks. Today we're going to look at how CutOver and AWS disaster recovery service can help you simplify and scale cloud disaster recovery to reduce costs and improve your resilience posture. For a large enterprise that maintains anywhere between five hundred to five thousand applications, the top twenty percent to thirty percent of those are mission and or business critical with recovery time objectives ranging from fifteen minutes to one hour. So when a power failure has occurred, knocking out a cloud availability zone, failing over applications that are affected to another a z or region is needed. Cutover allows you to efficiently identify those applications to fail over first from a single pane of glass with a repository of the approved templates including associated CMDB data at the runbook level directly fetched from ServiceNow or an in house tool. Now we need to filter based on location or an RTO of say fifteen minutes and AWS region US East one. You can see that one hundred and thirty four apps are involved in this failover. Let's look at a single example application that is going to use cutover and AWS DRS to failover. In the runbook, we know from the app definition that we are going to use DRS to failover the compute instances. This runbook has been populated at run time with real time data from app registry or the CMDB and describes EC two to filter instances by tags and dynamically create this runbook and get us this pair of server tasks that now appear in the runbook. You can see that those servers here have been instantiated with the DRS agents. Cutover is now connecting to DRS and will be using this DRS instance ID which you can find in the AWS console. The integration is also polling the status of the recovery and this provides real time visibility for all parties who might not have access to the DRS console. You can see here the replication has been kicked off. This is just one option. You can also use zonal shift or route fifty three arc to fail over across regions and then report on readiness of our landing zones capacity. Once the instance has been replicated back with DRS, we can move on to other tasks such as connecting these instances to the network via an AWS stack set operation. Throughout runbook orchestration, there is a comprehensive indelible audit trail that captures all actions by users during the execution of the runbook. This shows a single application recovering two servers. But when operating at enterprise scale, this can be upwards of thousands of servers across multiple AWS accounts. Cutover's multi runbook dashboard enables you to easily manage and track progress in real time and drill down into runbooks that require attention all from one screen. Take the risk and cost out of your cloud disaster recovery strategies with Cutover's automated and executable platform. Reduce your cloud disaster recovery execution time by fifty percent and gain the confidence you need to recover from cloud outages or failures with complete visibility and control.
.webp)
.webp)
