CALL NOW:866-611-7554

Disaster Recovery Solutions

VMware SRM

As a VMware Certified Hosting Provider, Your DR Site is able to provide your organization with VMware Site Recovery Manager (SRM). SRM is a disaster recovery suite to be integrated with VMware infrastructure. SRM offers SAN agnostic storage replication via vSphere Replication. vSphere Replication provides RPO as low as 1 minute and eliminates expensive hardware replication devices, such as EMC RPAs, and expensive licensing such as NetApp's SnapMirror.

Diaster Recovery Packages:


Package #1

  • 3 Hours DR Consulation
  • 5 Virtual Machines
  • 300GB SAN Storage
  • 20mbps of replication bandwidth
  • Veeam Backup & Replication or VMware SRM
  • VM control panel

$199 per month

Order Now

Package #3

  • 10 Hours DR Consulation
  • 20 Virtual Machines
  • 2TB SAN Storage
  • 250mbps of replication bandwidth
  • Dedicated VMware Cluster of ESXi hosts
  • VMware SRM
  • Dedicated VMware vCenter Access

$999 per month

Order Now

Package #2

  • 5 Hours DR Consulation
  • 10 Virtual Machines
  • 1TB SAN Storage
  • 100mbps of replication bandwidth
  • Veeam Backup & Replication or VMware SRM
  • VM control panel

$499 per month

Order Now

Package #4

  • 15 Hours DR Consulation
  • 50 Virtual Machines
  • 4TB SAN Storage
  • 300mbps of replication bandwidth
  • Dedicated VMware Cluster of ESXi hosts
  • VMware SRM
  • Dedicated VMware vCenter Access

$1999 per month

Order Now

Disaster Recovery Planning

Disaster Recovery starts with a plan. DR planning must consider existing infrastructure design, crucial components, non-crucial components, RTO (Recovery Time Objective), RPO (Recovery Point Objection), and cost. Your DR Site will provide a disaster recovery plan tailored to your specific needs, objectives, and bugetary requirements.

Existing Infrastructure

A DR Strategy needs to be implemented as efficiently as possible and should utilize your existing infrastrustructure. Whether your infrastructure is currently virtualized or using single purpo se physical servers you can implement DR today.

Indentifying Crucial Components

During planning, all crucial servers and functionality need to be identified. Databases, webservers, email servers, directory servers, and similar "high value" servers are placed on a high pr iority schedule. Development servers, test servers, data archives, and legacy systems would be placed on a lower priority or would simply not be part of the DR plan. After a thorough assessment of crucial components has been completed, each server would then be ordered by boot sequence. An example Windows environment crucial components boot order could be:

  1. Active Directory
  2. MSSQL
  3. Application Servers
  4. Webservers
  5. Exchange


RTO / RPO

Recovery Time Objective (RTO) is the duration of time within which a business process must be restored after a disaster in order to return service levels to a pre-disaster leve l. It can include the time for trying to fix the problem without a recovery, the recovery itself, testing, and the communication to the users/customers.

Recovery Point Objective (RPO) is the expected age of data that will be used to restore business services. As an example, data from servers that was backed up to tape will ha ve a potential RPO of the latest backup. If your scheduled backup ended at midnight and a disaster occurs at 3pm - the data available will be from 15 hours prior. In this example, your earlies t RPO would be 15 hours.

The goal of both RTO and RPO is to provide realistic timeframes - objectives. Realistic expectations shape the entire Disaster Recovery planning cycle and gu ides infrastructure and budget requirements.

Cost

Disaster Recovery is similar to an insurance policy. Like other forms of insurance, you pay a small premium to cover the costs associated with resolving a catastrophic event and allowing your company to continue operations. Costs are contingent upon required RTO, RPO, size of infrastructure, data change rate, and various other metrics that are considered in DR planning.

-->