Issue link: https://insights.oneneck.com/i/1190444
12 DISASTER RECOVERY GUIDE – Powered by ZERTO Hypervisor-based replication All these categories of replication technologies have critical limitations in a virtual context. In this way they undermine the promise of virtualization and limit its functionality. To fully benefit from the investment made in virtualization without compromising on BC/DR, a new approach is required: hypervisor-based replication. Zerto moved replication up the stack, from the storage layer, above the resources abstraction layer into the virtualization/ hypervisor layer. Section 2 describes how Zerto's innovative hypervisor-based replication solution delivers enterprise-class, virtual replication and BC/DR capabilities for the data center and the cloud. DR offered by hypervisors Hypervisor vendors, like VMware, also offer their own software-based replication solutions, limited to their own hypervisor. A solution like VMware vSphere Replication (VR) offers limited replication functionality, and does not include all the orchestration, testing, reporting and enterprise-class DR functions that are needed. Even combined with VMware Site Recovery manager (SRM), the recovery time and scalability may not be enough to satisfy the business needs. While SRM adds capabilities around the planning, testing, and execution of a disaster recovery, it can't overcome the replication limitations of vSphere Replication, as VMware vSphere Replication utilizes virtual machine snapshot technology. Disaster Recovery & the Cloud With the cloud becoming more of an option, enterprises of all sizes are looking for the cloud, be it public, hybrid or private, to become part of their BC/DR solution. Virtualization has created the opportunity, but depending on the solution, there still can be a significant technology gap. Mission-critical applications can be effectively virtualized and managed; however, they cannot be effectively protected in a cloud environment when the wrong tools are chosen. Disaster Recovery as a Service (DRaaS) The cloud as a DR solution is a smart choice, since the cloud is more flexible and usually less expensive than implementing a self-owned DR site. When it comes to choosing a cloud service provider and a DRaaS service it is important to realize that DRaaS is not a technology. It is a service based on one of the technologies mentioned above. The only big difference lies in the place where DR files are stored. This means that, if a solution is based on snapshots, it will come with all the shortcomings associated with snapshots including performance and storage impact on the production site. And foremost: a 15 minutes RPO based on snapshots is still unrealistic. Looking for a DRaaS service, a closer look has to be taken at the technology the service is based upon, with assurance that the RTO and RPO it offers is realistic and proven and without extra investments upfront. To help with this choice we set up a DR and DRaaS requirements checklist that can be found on the following page.