In my last post, I described how to use VMware® vCenter™ Site Recovery Manager™ to orchestrate the failover of a group of virtual machines (VMs) from one location to another. I also discussed the importance of planning when it comes to using Site Recovery Manager.
Some IT initiatives, such as disaster recovery, are natural fits for cloud computing. Yet it can be challenging to know exactly where to begin when it comes to configuring self-managed recovery plans and replicating virtual machines (VMs) from on-premises to a cloud service provider.
In the emerging business world, concepts like Disaster Recovery are often swept under the rug due to the added cost, but the reality is that downtime is a far worse consequence and the price of a modest Disaster Recovery plan in the cloud is marginal compared to what that downtime could cost your business.
VMware® vCenter™ Site Recovery Manager™ is used to orchestrate the failover of a group of virtual machines (VMs) from one location to another. It’s a really useful tool to have in your arsenal to tackle the daunting task of disaster recovery (DR), especially if you take a little time to plan for how and when it will be used.
For anyone tasked with developing an IT disaster recovery (DR) plan, the alphabet soup of DR options talked about today by service providers, software vendors, analysts and pundits can be truly bewildering. Against this backdrop, analysts like Gartner predict dramatic growth in both the consumption and hype of “cloudwashed” DR services. For example, John Morency of Gartner claims, “RaaS has been hailed as a ‘killer’ cloud app for disaster recovery, but the reality is that there has been much hype and some truth.”
The focus of any IT company should be on innovation, not disaster recovery. Budget and resources should align with your business objectives, and when possible, non-revenue generating tasks should be outsourced.