VirtualSharp announces ReliableDR 3.0 to be released Q1 2012

VirtualSharp announced it will release ReliableDR version 3.0 in Q1 of 2012. ReliableDR delivers Disaster Recovery Assurance. It automates Disaster Recovery testing and verifies that the recovery time (RTO)  and maximum allowed lose of data (RPO)  is according the Service Level Agreement.

Where other tools like Site Recovery Manager are limited to testing if the operating system responds, ReliableDR verifies that an application is operational after recovery. This is done by several fully automated tests like verification if certain services are running, or by sending a SQL query to a database server while verifiying the output of the query has an expected output. Automated recovery testing can be performed even every 15 minutes.

ReliableDR can both use storage based replication or host based replication.

Besides testing if an application is operational, ReliableDR tests if an application or set of applications running on different servers can be made operational within the defined Recovery Time Objective. Also is verified if the data which is used to recover services is not older than the agreed Recovery Point Objective.

More information on VirtualSharp and ReliableDR can be found in my posting I made a couple of months ago.

New features in version 3.0 are:

  • Multitenancy. End customers will be able to take advantage of the economies of scale provided by the cloud by sharing Disaster Recovery testing resources, without needingdedicated infrastructure. Hosters will be able to provide a low monthly cost that not onlyreplicates and secures data to cloud, but more importantly certifies recoverability and assures time to service in case of failover. End customers will further benefit from not needing to have specialized staff or to have to work weekends or holidays to perform Disaster Recovery tests. In addition, deployment costs will be extremely low and time to value will accelerate as VirtualSharp’s solution has zero footprint in the end customer data center. For hosters, multitenancy will also reduce the customer acquisition cost significantly as administrative tasks will be largely automated and partly delegated to the end customers. Without multitenancy, hosters had to incur significant up-front costs to deploy and manage dedicated resources to each customer.
  • Application-specific SLAs: Recovery Time Objectives and Recovery Point Objectives can be set individually for each application. For those applications that need more protection, hosters can set the frequency of Disaster Recovery tests as often as required and charge accordingly. Hosters can also provide value-added services to assure the perfect health of the components of the applications and remediate any compliance threats detected during the Disaster Recovery testing processes.
  • Role-based access control: end customers can gain access to compliance data with a very granular access level. This will allow application owners, auditors and compliance officers to independently verify the resilience of the IT services that they are responsible for, without compromising on security and confidentiality.
  • Web Oriented Architecture (WOA): access to test results will be provided through web services that can be accessed from any mobile device, including smartphones and tablets. IT and non-IT staff alike can obtain the recovery status of each application in real time, or look at the historical compliance data to evaluate service resilience over longer periods of time.
  • Embeddable dashboard: leveraging WOA, ReliableDR will provide an API to integrate the dashboard to implement administrative functions out of the hoster’s portal, or embed them in their Disaster Recovery cloud governance tools that can be provided to end customers. This will give customers at-a-glance visibility of all aspects regarding the hoster’s servicehealth and quality, and the ability to drill down into specific items.

    ReliableDR VirtualSharp DRaaS Disaster Recovery

    ReliableDR 3.0 dashboard


Add a Comment

Your email address will not be published. Required fields are marked *

Current ye@r *