Disaster Recovery as a Service

Discover how Engineering Disaster Recovery Cloud Service, based on the Commvault suite can help you reduce Backup and Disaster recovery costs. Data protection has changed, and although protecting data both for backup and disaster recovery purposes is as important as ever, there are alternate applications and methods for protecting data that are more efficient and less expensive.  Engineering DRaaS solution streamlines disaster recovery in the cloud with a simply powerful solution that features the deep integration, automation and flexibility across multiple VM and cloud platforms. It allows to apply disaster recovery capabilities across all customers workloads, with existing IT staff and within budget.

 

  • RTO
  • RPO
  • Warm DR site
  • VM Format conversion
  • Snapshot
  • Backup as a Service
  • Monitoring
  • Data center extension
  • Workload format conversion

 

Get Started  

Disaster Recovery as a Service

Disaster Recovery as a Service

Implementing a modern disaster recovery approach, which addresses diverse data siloes, multiple sites and varying application priorities, can be quite a long journey. For this purpose  Engineering DRaaS offers a solution, based on the Commvault platform, that can protect customer data no matter where it lives, greatly simplifying what otherwise would be a budget and logistical nightmare in terms of providing protection and recovery across multiple platforms and siloes.

This is achieved through the backup copy generated by CommVault backup and used Commvault Live Sync Replication to generate the copy in DR.

Commvault lets you manage cloud exactly like any other backup target, applying the same proven data recovery and retention policies that you use for local disks and other devices. The underlying technologies that power Commvault backup and recovery — security, encryption, deduplication and more — are extended to the cloud. Pre-built cloud workflows and simplified image creation reduce backup costs, empower all levels of IT skillset and reduce risk.

DRaaS offers turnkey solutions comprehending all technology and  professional services for implementing and managing functionality:

  • internet-VPN connection between Engineering DC and customer premises
  • backup agent installation
  • service configuration  and initial test
  • continuous monitoring controlled by Engineering control room
  • professional support for backup and restore activities
  • periodic DR test to verify recovery capability.

DRaaS live synchronous replication

The DRaaS feature enables incremental replication from a backup of a virtual machine (source VM) to a synced copy of the virtual machine (destination VM).  CommVault Live Sync opens the destination VM and applies changes from the source VM backups since the last sync point.

You can replicate virtual machines to Engineering Cloud, or to a VmWare or Microsoft Hyper-V infrastructure, or to a public cloud. When replicating to Cloudeng, you can specify the organization, virtual data center (vDC), vApp name, and vApp owner.

The Live Sync feature can initiate replication automatically after backups or on a scheduled basis (for example, daily or once a week), without requiring any additional action from users. Using backup data for replications minimizes the impact on the production workload by avoiding the need to read the source VM again for replication. In addition, in cases where corruption on the source VM is replicated to the destination VM, users can still recover a point-in-time version of the source VM from older backups.

DRaaS can be used to create and maintain warm recovery sites for virtual machines running critical business applications.

Engineering DRaaS Benefits

Engineering DRaaS offers the following benefits:

  • DRaaS is based not only on the replication of the latest production data, but it allows to recovery from the last valid backup, avoiding to replicate data that could eventually corrupted.
  • The impact on production servers is minimized because the service uses backup data to create replicated virtual machines; backup captures virtual machine data in a single pass, and DRaaS runs on backup infrastructure.
  • DRaaS is hardware agnostic; there is no need to reproduce the original hardware environment at the recovery site.
  • The recovery time objective (RTO), the time interval between a service interruption and the restoration of services from the recovery site, is the time needed to power on the virtual machines at the recovery site. Automated validation and the ability to specify new network connections at the recovery site ensure that startup time is minimized.
  • The recovery point objective (RPO), the acceptable time interval within which virtual machine data must be recoverable, is determined by the frequency of backups.
  • Backup data can be copied to a remote location where DRaaS operations are performed; deduplication and compression reduce the amount of data that needs to be transferred over the wide area network (WAN).

Advanced Backup can be requested for a VM to execute hot backup of databases, to select specific files, or to adopt different frequency of backup and different latency of data.

The copy of the image is always in sync with the latest backup copy. in the case where the warm stand by VM could not be used there is always the chance to perform a restore, based on the images kept according to the retention plan.

Engineering DRaaS Options

The most important options for the disaster recovery service depend on backup service options.

DRaaS allow to configure major DR parametres in the following way:

  • RPO depends on backup frequency. For critical data it is possible to setup hot backup that reduce RPO to desidered values.
  • RTO  is fixed and depends on the number of workload to be activated in the warm stand by site, or by particular recovery procedure that the cstomer requires.

The backup service can be customized with different options:

  • encryption to cipher data.
  • additional backup copy stored in the Engineering secondary data center.

DraaS depends on Backup policy Plans.
The copy of the image is always in sync with the latest backup copy. in the case where the warm stand by VM could not be used there is always the chance to perform a restore, based on the images kept according to the retention plan.

The service can be delivered with different charging models:

  • metered /consumption based - the price is determined by the real resource consumption
  • in bundle  - the price is fixed and is determined on the base of an estimation of reserved resources