Disaster recover/continuity of business adaptive solution framework

• US 7,934,116 B2
• Filed: 09/22/2006
• Issued: 04/26/2011
• Est. Priority Date: 09/30/2005
• Status: Active Grant

• Current Assignee: Leidos Innovations Technology, Inc.
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: Mehrdad, Aidun
• Primary Examiner(s): McCarthy; Christopher S
• Application Number:
  US11/534,521
• Publication Number:
  US 20070078861A1
• Time in Patent Office: 1,677 Days
• Field of Search: None
• US Class Current: 714/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A framework and method for use in determining appropriate information technology system disaster recovery and operational continuity solutions for an enterprise. In one embodiment the method includes identifying (504) business processes associated with achieving a defined mission of the enterprise. Assets of the information technology system are grouped (508) into one or more functional sub-system/data class groups and one or more of the business processes are selected. The functional sub-system/data class groups are mapped (524) to the selected business processes to establish a correspondence between each selected business process and one or more of the functional sub-system/data class groups. Thereafter, each functional sub-system/data class group corresponding with each selected business process is associated (602) with a solution class included in a three-dimensional disruption tolerance decision matrix.

Claims

1. A method for use in determining appropriate information technology system disaster recovery and operational continuity solutions for an enterprise, the information technology system including at least one primary site at which data is stored and at least one secondary site at which the data stored at the primary site is to be replicated, said method comprising:

(a) identifying business processes associated with achieving a defined mission of the enterprise;

(b) grouping assets of the information technology system into one or more functional sub-system/data class groups;

(c) selecting one or more of the business processes;

(d) mapping the functional sub-system/data class groups to the selected business processes to establish a correspondence between each selected business process and one or more of the functional sub-system/data class groups;

(e) associating each functional sub-system/data class group corresponding with each selected business process with a solution class selected from among a plurality of data recovery and server recovery solution classes included in a three-dimensional disruption tolerance decision matrix that includes a first axis representing a range of data loss if an event that causes loss of the data at the primary site occurs, a second axis representing a range of operational resumption times until business critical information technology applications are again available following the event that causes loss of the data at the primary site, and a third axis representing a packet delay time between the primary site and the secondary site, wherein said step of associating each functional sub-system/data class group corresponding with each selected business process with a solution class comprises;

(i) identifying a location on the third axis based on a packet delay time expected between the primary and secondary sites;

(ii) identifying a location on the second axis within the range of operational resumption times based on an acceptable operational resumption time if availability of the functional sub-system/data class group is effected;

(iii) identifying a location on the first axis within the range of data loss based on an acceptable level of data loss if availability of the functional sub-system/data class group is effected, wherein the identified location on the first axis is identified from a plurality of categories of data loss consisting of a no data loss category, a minimal data loss category, a some data loss category, and a major data loss category; and

(iv) selecting a solution class included in the three-dimensional disruption tolerance decision matrix and cross-referenced by the combination of identified locations on the first, second and third axes; and

(f) implementing within the information technology system the selected solution class associated with each functional sub-system/data class group.

2. The method of claim 1 wherein, in said step of identifying a location on the third axis, one of a small packet delay situation and a large packet delay situation are identified.

3. The method of claim 1 further comprising:

classifying each identified business process as being within one of a plurality of criticality levels; and

wherein in said step of selecting one or more business processes, the one or more business processes are selected based on their criticality levels.

4. The method of claim 3 wherein the plurality of criticality levels include critical and non-critical.

5. The method of claim 1 wherein, in said step of grouping, one or more assets are included in two or more groups.

6. The method of claim 1 wherein, in said step of mapping, a correspondence is established between one or more functional sub-system/data class groups and two or more selected business processes.

7. The method of claim 1 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the no data loss category on the first axis include the following solutions:

(1) an active/active synchronous replication solution;

(2) a synchronous replication active/passive solution;

(3) a synchronous replication hot backup solution; and

(4) a synchronous replication cold backup solution.

8. The method of claim 1 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the minimal data loss category on the first axis include the following solutions:

(1) an active/active asynchronous replication solution;

(2) an asynchronous replication active/passive solution;

(3) an asynchronous replication hot backup solution; and

(4) an asynchronous replication cold backup solution.

9. The method of claim 1 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the some data loss category on the first axis include the following solutions:

(1) an active/active snap-shot replication solution;

(2) a snap-shot replication active/passive solution;

(3) a snap-shot replication hot backup solution; and

(4) a snap-shot replication cold backup solution.

10. The method of claim 1 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the major data loss category on the first axis include the following solutions:

(1) an active/active manual data synchronizing solution;

(2) a tape backup active/passive solution;

(3) a tape backup hot backup solution; and

(4) a tape backup cold backup solution.

11. A method for use in determining appropriate information technology system disaster recovery and operational continuity solutions for an enterprise, the information technology system including at least one primary site at which data is stored and at least one secondary site at which the data stored at the primary site is to be replicated, said method comprising:

(a) identifying business processes associated with achieving a defined mission of the enterprise;

(b) grouping assets of the information technology system into one or more functional sub-system/data class groups;

(c) selecting one or more of the business processes;

(d) mapping the functional sub-system/data class groups to the selected business processes to establish a correspondence between each selected business process and one or more of the functional sub-system/data class groups;

(e) associating each functional sub-system/data class group corresponding with each selected business process with a solution class selected from among a plurality of data recovery and server recovery solution classes included in a three-dimensional disruption tolerance decision matrix that includes a first axis representing a range of data loss if an event that causes loss of the data at the primary site occurs, a second axis representing a range of operational resumption times until business critical information technology applications are again available following the event that causes loss of the data at the primary site, and a third axis representing a packet delay time between the primary site and the secondary site, wherein said step of associating each functional sub-system/data class group corresponding with each selected business process with a solution class comprises;

(i) identifying a location on the third axis based on a packet delay time expected between the primary and secondary sites;

(ii) identifying a location on the second axis within the range of operational resumption times based on an acceptable operational resumption time if availability of the functional sub-system/data class group is effected, wherein the identified location on the second axis is identified from a plurality of categories of operational resumption times consisting of seconds, minutes, hours, and days;

(iii) identifying a location on the first axis within the range of data loss based on an acceptable level of data loss if availability of the functional sub-system/data class group is effected; and

(iv) selecting a solution class included in the three-dimensional disruption tolerance decision matrix and cross-referenced by the combination of identified locations on the first, second and third axes; and

(f) implementing within the information technology system the selected solution class associated with each functional sub-system/data class group.

12. The method of claim 11 wherein, in said step of identifying a location on the third axis, one of a small packet delay situation and a large packet delay situation are identified.

13. The method of claim 11 further comprising:

classifying each identified business process as being within one of a plurality of criticality levels; and

wherein in said step of selecting one or more business processes, the one or more business processes are selected based on their criticality levels.

14. The method of claim 13 wherein the plurality of criticality levels include critical and non-critical.

15. The method of claim 11 wherein, in said step of grouping, one or more assets are included in two or more groups.

16. The method of claim 11 wherein, in said step of mapping, a correspondence is established between one or more functional sub-system/data class groups and two or more selected business processes.

17. The method of claim 11 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the seconds category on the second axis include the following solutions:

(1) an active/active synchronous replication solution;

(2) an active/active asynchronous replication solution;

(3) an active/active snap-shot replication solution; and

(4) an active/active manual data synchronizing solution.

18. The method of claim 11 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the minutes category on the second axis include the following solutions:

(1) a synchronous replication active/passive solution;

(2) an asynchronous replication active/passive solution;

(3) a snap-shot replication active/passive solution; and

(4) a tape backup active/passive solution.

19. The method of claim 11 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the hours category on the second axis include the following solutions:

(1) a synchronous replication hot backup solution;

(2) an asynchronous replication hot backup solution;

(3) a snap-shot replication hot backup solution; and

(4) a tape backup hot backup solution.

20. The method of claim 11 wherein, in said step of selecting a solution class, possible solutions cross-referenced by a location within the days category on the second axis include the following solutions:

(1) a synchronous replication cold backup solution;

(2) an asynchronous replication cold backup solution;

(3) a snap-shot replication cold backup solution; and

(4) a tape backup cold backup solution.

21. A method for use in determining appropriate information technology system disaster recovery and operational continuity solutions for an enterprise, the information technology system including at least one primary site at which data is stored and at least one secondary site at which the data stored at the primary site is to be replicated, said method comprising:

(a) identifying business processes associated with achieving a defined mission of the enterprise;

(b) grouping assets of the information technology system into one or more functional sub-system/data class groups;

(c) selecting one or more of the business processes;

(d) mapping the functional sub-system/data class groups to the selected business processes to establish a correspondence between each selected business process and one or more of the functional sub-system/data class groups;

(e) associating each functional sub-system/data class group corresponding with each selected business process with a solution class selected from among a plurality of data recovery and server recovery solution classes included in a three-dimensional disruption tolerance decision matrix that includes a first axis representing a range of data loss if an event that causes loss of the data at the primary site occurs, a second axis representing a range of operational resumption times until business critical information technology applications are again available following the event that causes loss of the data at the primary site, and a third axis representing a packet delay time between the primary site and the secondary site, wherein said step of associating each functional sub-system/data class group corresponding with each selected business process with a solution class comprises;

(i) identifying a location on the third axis based on a packet delay time expected between the primary and secondary sites;

(ii) identifying a location on the second axis within the range of operational resumption times based on an acceptable operational resumption time if availability of the functional sub-system/data class group is effected, wherein the identified location on the second axis is identified from a plurality of categories of operational resumption times consisting of seconds, minutes, hours, and days;

(iii) identifying a location on the first axis within the range of data loss based on an acceptable level of data loss if availability of the functional sub-system/data class group is effected, wherein the identified location on the first axis is identified from a plurality of categories of data loss consisting of a no data loss category, a minimal data loss category, a some data loss category, and a major data loss category; and

(iv) selecting a solution class included in the three-dimensional disruption tolerance decision matrix and cross-referenced by the combination of identified locations on the first, second and third axes; and

(f) implementing within the information technology system the selected solution class associated with each functional sub-system/data class group.