VirtualSharp on Cloud Disaster Recovery

DZone 's Guide to

VirtualSharp on Cloud Disaster Recovery

· Cloud Zone ·
Free Resource

I’m sitting here at the CloudBeat event, a conference that I’ve had a deep involvement in with as co-content adviser along with my friend and colleague Paul Miller. Our focus for this event was to avoid the obvious vendor pitches and CloudWashing sessions and instead gather togteher some great customer success stories to tell the world. Despite this customer focus however there are always the odd interesting product announcement and this is where VirtualSharp comes in.

One of the finalists in the CloudBeat Innovation Showdown, VirtualSharp is a provider of automated disaster recovery solutions for private and public clouds, and they’ve just announced the latest release of their product, ReliableDR 3.0. Reliable takes a different perspective on DR, coming to it from a data center orchestration viewpoint. They’re trying to not simply look at data replication, but to look at recovery across the entire stack, from storage to applications.

As well as this new release, VirtualSharp is formally launching the ReliableDR product in the US after good success in Europe. New features in ReliableDR 3.0:

  • Multitenancy. End customers will be able to share Disaster Recovery testing resources, without needing dedicated infrastructure.
  • Application-specific SLAs: Recovery Time Objectives and Recovery Point Objectives can be set individually for each application.
  • Role-based access control: end customers can gain access to compliance data with a very granular access level.
  • Web Oriented Architecture (WOA): access to test results will be provided through web services that can be accessed from any device
  • Embeddable dashboard

This is a pre-announcement, something that I’m always a little dubious about. VirtualSharp promises that ReliableDR 3.0 will be available in the first quarter of 2012.


Source: http://www.diversity.net.nz/virtualsharp-on-cloud-disaster-recovery/2011/11/30/


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}