Data Recovery Systems and Methods

• US 20080209142A1
• Filed: 02/14/2008
• Published: 08/28/2008
• Est. Priority Date: 02/23/2007
• Status: Active Grant

• Current Assignee: Lewis Rice and Fingersh (Lewis Rice LLC)
• Original Assignee: Lewis Rice and Fingersh (Lewis Rice LLC)
• Inventors: Obernuefemann, Paul R.
• Granted Patent: US 7,873,805 B2
• Time in Patent Office: Days
• US Class Current: 711/161
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques

Abstract

Nearline disaster recovery (“nearline DR”) storage systems and methods that permit the use of previously restored stored data from a near time period by virtual applications operating off a backup storage location during the period of disaster recovery at a primary site. This is generally referred to as a “nearline DR storage process.”

Claims

1. A nearline disaster recovery storage system, said system comprising.

a first site having a primary server for supporting an operating system and at least one application to run on at least one client;

a data set generated at said first site, manipulated by said first site, and stored on said primary server;

a backup data set duplicative of said data set, generated and stored at said first site;

a backup site geographically separated from said first site, said backup site comprising;

a connection to said first site via which said backup data set can be transported from said first site to said backup site after generation of said backup data set;

a storage facility for said backup data; and

a secondary server; and

a virtual application server, said virtual application server comprising said operating system, said at least one application, and a means for allowing remote access to said virtual application server;

wherein upon receipt of said backup data set, and prior to a disaster event, said backup data set is restored onto said secondary server in native format so that a server at said backup site can manipulate said backup data set as said primary server manipulates said data set; and

wherein after said backup data set is restored and in the event said primary server becomes unusable, said virtual application server can attach to said backup data set.

2. The system of claim 1 wherein said backup data set can be generated on command.

3. The system of claim 1 wherein said backup data set can be generated repeatedly upon a lapse of a set time period.

4. The system of claim 1 wherein said backup data set is transported by said restoration server.

5. The system of claim 1 wherein said backup data set is transported using the software used to generate said backup data set.

6. The system of claim 1 wherein said transport of said backup data set is incremental.

7. The system of claim 1 wherein said backup data set is restored by the software used to generate and transport said backup set.

8. The system of claim 1 wherein said virtual application server hosts programs for email, document use, and business accounting.

9. The system of claim 1 wherein said virtual application server may be used while said first site and said data set are brought back online.

10. The system of claim 1 wherein said virtual application server may be used remotely.

11. The system of claim 1 wherein said virtual application server may be used at said backup site.

12. A method for nearline disaster recovery, said method comprising:

generating a data set at a first site, said first site comprising a primary server for allowing an operating system and at least one application to run on at least one client;

storing said data set on said primary server;

generating a backup data set duplicative of said data set;

storing said backup data set at said first site.

transporting a copy of said backup data set to a backup site geographically separated from said first site, said backup site comprising a connection to said first site, a secondary server, and a storage facility for said backup data set;

restoring said copy of said backup data set to native format onto said secondary server, so that a server at said secondary site can manipulate said data set as said primary server manipulates said data set, said restoring occurring prior to a disaster event;

in the event of said primary server becoming unusable, attaching a virtual application server to said restored backup data set, said virtual application server including said operating system and at least one application, and

accessing remotely said virtual application server.

13. The method of claim 12 wherein said step of generating a backup data set may be performed on command.

14. The method of claim 12 wherein said step of generating a backup data set may be performed repeatedly upon a lapse of a set time period.

15. The method of claim 12 wherein said step of transporting is performed by said secondary server.

16. The method of claim 12 wherein said step of transporting is performed by software used in said step of generating said backup set.

17. The method of claim 12 wherein said step of transporting said backup data set is incremental.

18. The method of claim 12 wherein said step of restoring is performed by software used in said step of generating said backup data set and said step of transporting.

19. The method of claim 12 wherein said virtual application server hosts programs for email, document use, and business accounting.

20. The method of claim 12 further comprising using said restored data set while simultaneously bringing said first site and said data set back online.

21. The method of claim 12 further comprising using said virtual application server remotely.

22. The method of claim 12 further comprising using said virtual application server at said backup site.

23. The method of claim 12 further comprising:

generating a second backup data set duplicative of said backup data set;

storing said second backup data set at said backup site;

transporting a copy of said second backup data set to a third site geographically separated from said first site and said backup site, said third site comprising a connection to said backup site and said first site, a tertiary server, and a storage facility for said second backup data set;

restoring said copy of said second backup data set to native format onto said tertiary server, so that a server at said tertiary site can manipulate said second backup data set as said secondary server manipulates said backup data set, said restoring occurring prior to a disaster event;

in the event of said primary server and said secondary server becoming unusable, attaching a virtual application server to said restored backup data set, said virtual application server including said operating system and at least one application; and

accessing remotely said virtual application server.