Dynamic resource allocation in recover to cloud sandbox

• US 8,700,946 B2
• Filed: 10/27/2011
• Issued: 04/15/2014
• Est. Priority Date: 10/27/2011
• Status: Active Grant

• Current Assignee: 11 11 Systems, Inc.
• Original Assignee: Sungard Availability Services LP (Sungard Availability Services Capital, Inc.)
• Inventors: Reddy, Chandra, Li, Enyou
• Primary Examiner(s): DUNCAN, MARC M
• Application Number:
  US13/283,173
• Publication Number:
  US 20130111260A1
• Time in Patent Office: 901 Days
• Field of Search: 714/4.11, 714/27, 714/28, 714/41
• US Class Current: 714/4.11
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 11/273 Tester hardware, i.e. output processing circuits G06F11/263 takes precedence
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 2201/815 Virtual

Abstract

A recover to cloud (R2C) service replicates a customer production environment to virtual data centers (VDCs) operated in a cloud service provider environment. Customers provision both a disaster recovery VDC and a test VDC. At A Time of Disaster (ATOD), the disaster VDC is made available to the customer through the cloud. The disaster VDC is allocated a first set of resources dedicated to the specific customer and to disaster recovery. The test VDC, brought on line at A Time of Test (ATOT), is allocated resources from second set of resources arranged in a shared pool, separate from the first set. Provisioning of the test VDC does not disturb critical resource assignments needed in the event of a disaster.

Claims

1. A data processing system for replication of a production data processing environment operated by a customer, the production environment including at least one production data processor and at least one production networking device, the system comprising:

(a) a disaster virtual data center (VDC) including at least one dedicated live virtual machine (VM), at least one dedicated replication networking device, and one or more dormant VM definition for storing replicated data received from the production environment;

(b) a test virtual data center (VDC) including provisions for allocating a networking and security device on demand from a pool of networking devices;

(c) a failover process comprising;

a replication process for receiving replicated data from the production system and writing the replicated data to the dormant VM in the disaster VDC, while the production system is in operation;

a failure recovery process for activating the disaster VDC for access by the customer in place of the production system by promoting the dormant VM to a live VM when the production system fails; and

(d) a testing process comprising;

a sandbox test process for (i) moving or copying the first dormant VM from the disaster VDC to the dormant second VM in the test VDC;

(ii) promoting the second dormant VM to a live VM within the test VDC;

(iii) allocating a networking device on demand from a pool of networking devices reserved for sandbox testing;

(iv) activating the test VDC for access by the replication service customer while the production system is still operating; and

(v) releasing the networking device to the pool when the sandbox test process is finished.

2. The system of claim 1 wherein the networking devices are at least one of firewalls or VLANs.

3. The system of claim 1 wherein the service customer accesses the test VDC using network device identifiers that do not conflict with network device identifiers allocated to the production system.

4. The system of claim 1 wherein the replication process also supports failure recovery and sandbox test processes for a second customer, and the sandbox test process for the second customer allocates a same networking device from the pool that was earlier allocated to and then released by the first customer.

5. The system of claim 1 wherein the sandbox testing process further tests at least one of production system failover scenarios, roll out of new applications and services, different backup scenarios, or stress testing.

6. The system of claim 1 wherein once a VDC is assigned to a customer as a disaster or test VDC, it is isolated from other customers'"'"' VDCs at the service provider environment by its own virtual firewall and other security measures.

7. The system of claim 1 wherein the pool of networking devices reserved for sandbox testing does not include the dedicated networking device assigned to the disaster VDC.

8. The system of claim 1 wherein the failover process further comprises:

an allocation process for allocating network and firewall resources to connect the failed over live VMs to other recovered servers located within the same or a different data center as the disaster VDC.

9. A method for recovering a production system comprising:

(a) replicating the production system with a disaster virtual data center (VDC) including at least one live virtual machine (VM) having a secure connection through at least one networking device dedicated to the disaster VDC, and a first dormant VM definition, for storing replicated data received from the production system while the production system is in operation;

(b) maintaining a test virtual data center (VDC) definition including at least a second dormant VM definition;

(c) recovering from a disaster event by activating the disaster VDC for access by the replication service customer in place of the production system by promoting the first dormant VM definition to a live VM when the production system fails; and

(d) testing recovery of the production system in a sandbox by;

(i) moving or copying the first dormant VM from the first dormant to the second dormant VM in the test VDC;

(ii) promoting the second dormant VM to a live VM within the test VDC;

(iii) allocating a networking device on demand from a pool of networking devices reserved for sandbox testing;

(iv) activating the test VDC for access while the production system is still operating; and

(v) releasing the networking device to the pool when the sandbox testing step is finished.

10. The method of claim 9 wherein the networking devices are at least one of firewalls or VLANs.

11. The method of claim 9 wherein the test VDC uses network device identifiers that do not conflict with network device identifiers allocated to the production system.

12. The method of claim 9 further comprising recovering and testing recovery steps for a second customer, and the testing recovery step for the second customer allocates a same networking device from the pool that was earlier allocated to and then released by the first customer.

13. The method of claim 9 wherein the testing recovery step further includes testing to at least one of a production system failover scenario, roll out of new applications and services, different backup scenarios, or stress testing.

14. The method of claim 9 wherein the dormant VM definition is a VMDK-compatible file.

15. The method of claim 9 wherein once a VDC is assigned to a customer as a disaster VDC or test VDC, it is isolated from other customers'"'"' VDCs by at least a virtual firewall and one other security measure.

16. The method of claim 9 wherein the pool of networking devices reserved for the sandbox testing step does not include the dedicated networking device assigned to the disaster VDC.

17. A programmable computer product for providing disaster recovery and sandbox testing of a production data processing environment, the production environment comprising two or more data processors to be replicated, the program product comprising one or more data processing machines that retrieve instructions from one or more stored media and execute the instructions, the instructions for:

(a) replicating the production system with a disaster virtual data center (VDC) including at least one live virtual machine (VM) having a secure connection through at least one networking device dedicated to the disaster VDC, and a first dormant VM definition, for storing replicated data received from the production system while the production system is in operation;

(b) maintaining a test virtual data center (VDC) definition including at least a second dormant VM definition;

(c) recovering from a disaster event by activating the disaster VDC for access by the replication service customer in place of the production system by promoting the first dormant VM definition to a live VM when the production system fails; and

(d) testing recovery of the production system in a sandbox by;

(i) moving or copying the first dormant VM from the first dormant to the second dormant VM in the test VDC;

(ii) promoting the second dormant VM to a live VM within the test VDC;

(iii) allocating a networking device on demand from a pool of networking devices reserved for sandbox testing;

(iv) activating the test VDC for access while the production system is still operating; and

(v) releasing the networking device to the pool when the sandbox testing step is finished.