Method and Means for Dynamic Pricing based Disaster-Recovery-as-a-Service (DRaaS) Service Offering
Publication Date: 2016-Jan-15
The IP.com Prior Art Database
Disclosed is a Disaster Recovery (DR) testing service-offering framework. A DR Offering Module and a DR Pricing Module form an interface between the customer and the Disaster-Recovery-as-a-Service (DRaaS) service provider data center, in order to provide a dynamic pricing-based DR test service-offering framework and alleviate the possible severe resource contention from multiple concurrent DR test requests.
Page 01 of 6
Method and Means for Dynamic Pricing based Disaster -Recovery-as-a-Service (DRaaS) Service Offering
Disaster-Recovery-as-a-Service (DRaaS) is an emerging information technology (IT) service offering that provides seamless data protection and business resiliency protection service for customer IT environments (e.g., a data center with hybrid physical and virtual resources (virtual machines, disks). The DRaaS service provider usually maintains a dedicated data center to host the replicated data from customer environments, as shown below.
Figure 1: Current DRaaS architecture
The customers connect a specified data center to a dedicated DRaaS data center belonging to the service provider. DR related tasks are submitted to a DR scheduler, which triggers the operations at the DRaaS data center. Common DR related requests are DR onboarding, DR declare, and DR testing.
This disclosure addresses DR testing, for which the customer requires the service provider to regularly perform disaster recovery tests and ensure that it meets the Service Level Agreement (SLA) criteria (e.g., recovery time objective, recovery point objective, etc.). All three types of requests utilize a common DR analyzer module to provide an information summary and analysis for the customer regarding the DR requests and the status of each. The novel contribution is a DR testing service-offering framework. The novel DR Offering Module and DR Pricing Module form an interface between the customer (i.e. issuing DR test requests) and the DRaaS service provider data center. (Figure 2)
Figure 2: Solution: The DR Offering Module and DR Pricing Module form an interface between the customer and the DRaaS service provider data center
Page 02 of 6
The DR Offering Module comprises different DR test offerings according to the delay tolerance of performing tests and generating test analysis reports. In addition, each DR test offering is associated with a price, which is determined by the DR Pricing Module. The price of a delay-tolerant DR test plan is less expensive than the time-critical DR test plan offering, which motivates the customer to choose a delay tolerant DR test plan for resource-overutilization avoidance. For example, the DR test plan offerings can be "on- demand" for x dollars, "within one day" for y dollars, and "within three days" for z dollars where x > y > z. The goal is to incentivize the DR test request issuing customers to choose a delay tolerant DR test plan, for example, "within 3 days", using a lower price of
z. With this approach, the DRaaS can provide the resource demanding DR test task for this specific customer during the low utilization period within three days.
In addition, the framework includes a hybrid DR testing offer, which utilizes the on- premise resources of a customer to perform the actual testing tasks, using the data stored in the DRaaS site. For example, this option can be offered as a "Hybrid DR Test" with zero or little cost where the goal i...