US20090271658A1 - No data loss it disaster recovery over extended distances - Google Patents

No data loss it disaster recovery over extended distances Download PDF

Info

Publication number
US20090271658A1
US20090271658A1 US12/500,016 US50001609A US2009271658A1 US 20090271658 A1 US20090271658 A1 US 20090271658A1 US 50001609 A US50001609 A US 50001609A US 2009271658 A1 US2009271658 A1 US 2009271658A1
Authority
US
United States
Prior art keywords
data
site
storage device
data storage
sites
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/500,016
Inventor
Mehrdad Aidun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lockheed Martin Corp
Original Assignee
Lockheed Martin Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lockheed Martin Corp filed Critical Lockheed Martin Corp
Priority to US12/500,016 priority Critical patent/US20090271658A1/en
Publication of US20090271658A1 publication Critical patent/US20090271658A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2058—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using more than 2 mirrored copies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2069—Management of state, configuration or failover
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
    • G06F11/2074—Asynchronous techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
    • G06F11/2076—Synchronous techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2082—Data synchronisation

Definitions

  • the present invention relates generally to information technology systems, and more particularly to providing zero loss data protection and automated data recovery over extended distances.
  • an event e.g., an equipment failure, a power failure, a natural disaster, or a terrorist attack or other man-made event
  • the data can be recovered from the second location.
  • the first location may be referred to as the primary site
  • the second location may be referred to as the disaster recovery site
  • such an occurrence may be referred to as a disaster event.
  • the disaster recovery site In order to provide sufficient assurance that the disaster recovery site will not be effected by the disaster event effecting the primary site, the disaster recovery site must be geographically separated from the primary site by a sufficient distance.
  • the present invention introduces an intermediary site between the primary site and the disaster recovery site.
  • the primary site may be referred to herein as the first site
  • the intermediary site may be referred to herein as the nearby safe site or the second site
  • the disaster recovery site may be referred to herein as the third site.
  • the data is replicated from the primary site to the nearby safe site and then subsequently replicated from the nearby safe site to the disaster recovery site.
  • the nearby safe site may be geographically remote from the primary site such that the nearby safe site would be expected to survive a disaster event effecting the primary site for some period of time after the primary site goes down, but not necessarily survive indefinitely.
  • the nearby safe site is located close enough to the primary site such that synchronous data replication is possible between the primary site and the nearby safe site without encountering unacceptable roundtrip packet delays.
  • the disaster recovery site is located far enough from the primary site that the disaster recovery site would be expected to survive the disaster event effecting the primary site. Because the data has already been replicated to the nearby safe site, asynchronous replication of the data from the nearby safe site to the disaster recovery site is acceptable.
  • the nearby safe site includes a number of desirable characteristics.
  • the nearby safe site is close enough to the primary site that roundtrip packet delays between the nearby safe site and the primary site would not be detrimental to the user software applications.
  • a typical maximum distance is, for example, one-hundred kilometers or even two-hundred kilometers, although actual allowable distances depend on the actual network paths traversed, roundtrip packet delays encountered, and the software application sensitivity to roundtrip packet delays.
  • the nearby safe site can be run in a “lights out” configuration with no regular staffing requirements and is expected to operate in case of chemical, biological, or nuclear contamination.
  • the primary hardware components at the nearby safe site are data storage devices as well as application servers.
  • the data on the data storage devices could optionally be encrypted allowing the nearby site and its assets to be shared among multiple customers at different physical locations.
  • the nearby site is physically protected to continue to operate for a relatively short period of time after the primary site has sustained a disaster, thereby allowing for the completion of the data transfer that has been buffered at this site to the disaster recovery site.
  • an extended distance data recovery system includes a first data storage device located at a first site, a second data storage device located at a second site, a third data storage device located at a third site, and a computer executable control process coordinating all three sites.
  • the first data storage device has data stored thereon.
  • the second data storage device is communicatively connected with the first data storage device, and the third data storage device is communicatively connected with the second data storage device.
  • the computer executable control process is executable to direct synchronous replication of the data onto the second data storage device.
  • the control process is also executable to direct asynchronous replication of the data from the second data storage device onto the third data storage device.
  • the computer executable control process is executable to coordinate among the three sites the state of application servers, storage replication, network address changes, and other prerequisite aspects of the IT infrastructure required to allow the application servers to successfully start at the disaster recovery site.
  • a method for providing recovery of data and operational continuity of computer applications accessing the data if an event occurs effecting access to the data on an information technology system includes the step of storing the data at a first site.
  • the data is synchronously replicated from the first site to a second site under the direction of a computer executable control process.
  • the data is asynchronously replicated from the second site onto a third site, also under the direction of the control process.
  • the operational status of the first site is monitored, and, upon occurrence of the event, location identifying information associated with the data is updated so that computer applications access the data from the second site and/or the third site.
  • FIG. 1 is block diagram showing one embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention
  • FIG. 2 is block diagram showing another embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention.
  • FIG. 3 is block diagram showing one more embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention.
  • FIG. 1 illustrates one embodiment of an extended distance data recovery system 100 .
  • the system 100 includes a first data storage device 112 located at a first site 110 (the primary site 110 ), a second data storage device 122 located at a second site 120 (the nearby safe site 120 or intermediary site 120 ), and a third data storage device 132 located at a third site 130 (the disaster recovery site 130 ).
  • the data storage devices 112 , 122 , 132 may, for example, be storage area network (SAN) devices each including a group of networked data storage devices (e.g., hard drives, CD or DVD drives, tape drives, flash memory devices, etc.).
  • SAN storage area network
  • one or more of the first, second and third data storage devices 112 , 122 , 132 may, for example, be devices other than a storage area network device such as, for example, an individual hard drive.
  • data replication may need to be handled at a middleware or application layer level.
  • the primary site 110 may be geographically remote from the other sites such that in the event of an occurrence (e.g., an equipment failure, a power failure, a natural disaster, a terrorist attack or other man-made event) that causes loss of data access at the primary site 110 , conditions effecting the operation of the primary site 110 may not necessarily effect the operations at the other two sites 120 , 130 .
  • an occurrence e.g., an equipment failure, a power failure, a natural disaster, a terrorist attack or other man-made event
  • the primary and nearby safe sites 110 , 120 may, for example, be located in different buildings or in different towns as long as the primary and nearby safe sites 110 , 120 are close enough to one another that a roundtrip packet delay time between the primary and nearby safe sites 110 , 120 is within an acceptable range
  • the primary and disaster recovery sites 110 , 130 may, for example, be located in different towns, in different states, or even in different countries without regard to a roundtrip packet delay time therebetween.
  • each site 110 , 120 , 130 are enabled for communication therebetween via a suitable data network so that data created and/or stored at one site can be communicated to and replicated at another site.
  • the data network may include various private and/or publicly shared wired and/or wireless portions.
  • One or more user applications 114 are executable by one or more computer processors or the like at the primary site 110 .
  • the user application(s) 114 create, update, and/or access data 116 that is stored, via a data input/output (I/O) interface 118 on the first data storage device 112 .
  • I/O data input/output
  • the extended distance data recovery system 100 also includes a virtual integration console 150 (VIC 150 ).
  • VIC 150 may also be referred to herein the control process 150 or control application 150 .
  • VIC 150 is implemented in software executable by a computer processor, and there can be instances of VIC 150 executing on computer systems at each of the primary site 110 , nearby safe site 120 and the disaster recovery site 130 .
  • Each instance of VIC 150 interfaces with the other instance of VIC 150 , and in FIG. 1 all three instances of VIC 150 are represented as a single block.
  • VIC 150 directs the replication of the data 116 from the primary site 110 to the nearby safe site 120 .
  • VIC 150 directs replication of the data 116 from the primary site 110 to the nearby safe site 120 to take place in a synchronous manner at the storage level.
  • the packets of the data 116 are also written to the second data storage device 122 and confirmation that the data replication operation has been completed is provided by the second data storage device 122 to the first data storage device 112 at the primary site 110 .
  • the roundtrip packet delay time between the primary and nearby safe sites 110 , 120 depends on a number of factors including the type of communication network equipment used and overall network traffic, the primary site 110 and the nearby safe site 120 should, in general, be sufficiently proximate to one another such that the roundtrip packet delay time between the primary and nearby safe sites 110 , 120 is not so long in duration that normal operation of the user application(s) is unacceptably impacted. While the geographic distance between the primary and nearby safe sites 110 , 120 providing such an acceptable roundtrip packet delay time can vary greatly from one situation to another, geographic distances in the range of 100 kilometers up to 200 kilometers may be possible.
  • VIC 150 In addition to directing replication of the data 116 to the second data storage device 122 at the nearby safe site, VIC 150 also directs replication of the data 116 from the second data storage device 122 to the third data storage device 132 at the disaster recovery site 130 . In the present embodiment, VIC 150 directs replication of the data 116 from the nearby safe site 120 to the disaster recovery site 130 to take place in an asynchronous manner. In this regard, the data 116 is replicated from the second data storage device 122 to the third data storage device 132 when resources at the nearby safe and disaster sites 120 , 130 are available to copy the data 116 . In this manner, the data 116 is initially replicated at the nearby safe site 120 and thereafter replicated to the disaster recovery site 130 .
  • the asynchronous data replication may occur periodically (e.g., every day, every hour, every minute, or as fast as the communication throughput between nearby safe site 120 and disaster recovery site 130 allow), or may occur in response to certain predefined events.
  • the asynchronous data transfer protocol allows the primary site 110 to effectively be decoupled from the disaster recovery site 130 .
  • This configuration permits the disaster recovery site 130 to be located at a distance from the primary site 110 that is much greater than the distance between the nearby safe site 120 and the primary site 110 .
  • the disaster recovery site 130 may be located in a different state or in a different country than the primary site 110 . This provides even greater protection of the data 116 and continuity of the user application(s) 114 from the occurrence of a disaster event.
  • VIC 150 also monitors the operational status of the primary site 110 . If a failure is detected and the application(s) 114 at the primary site 110 are not operating or are not able to access the data 116 from the first data storage device 112 , VIC 150 makes the data 116 available from the nearby safe site 120 and/or the disaster recovery site 130 as appropriate. In this regard, if asynchronous replication of the data 116 from the second data storage device 122 to the third data storage device 132 is complete, then VIC 150 directs resources to access the data 116 from the third data storage device 132 instead of from the first data storage device 112 .
  • one or more user application(s) 134 executable on computer systems located at the disaster recovery site 130 may access the data 116 from the third data storage device 132 via a data I/O interface 138 .
  • the disaster recovery site 130 user application(s) 134 may be the same as and/or provide the same functionality as the user application(s) 114 at the primary site 110 in order to provide continuity of operations formerly accomplished at the primary site 110 . If, however, asynchronous replication of the data 116 from the second data storage device 122 to the third data storage device 132 has not been completed, then VIC 150 directs completion of the asynchronous data replication process. In the meantime, VIC 150 may direct resources to access the data 116 from the second data storage device 122 until the asynchronous data replication process is complete.
  • the user application(s) 134 at the disaster recovery site 130 do not operate while the primary site 110 user application(s) 114 operate, but when the primary site 110 goes down, VIC 150 activates the application(s) 134 at the disaster recovery site.
  • the primary site 110 user application(s) 114 are considered active
  • the disaster recovery site 130 user application(s) 134 are considered passive, and therefore the present embodiment may be referred to as an active/passive extended distance data recovery system 100 .
  • Redirection of resources accessing the data 116 to the nearby safe site and/or disaster recovery site may be accomplished by VIC 150 in a number of manners.
  • One manner is by providing updated IP address information associated with the data 116 to one or more domain name servers 170 (DNSs 170 ).
  • DNSs 170 domain name servers 170
  • FIG. 2 shows another embodiment of an extended distance data recovery system 200 .
  • the extended distance data recovery system 200 of FIG. 2 includes a number of elements in common with the system 100 of FIG. 1 , and corresponding elements are referenced using the same numerals.
  • VIC 150 directs replication of the data 116 from the primary site 110 to the nearby safe site 120 to take place in a synchronous manner at the application level rather than the storage level.
  • packets of the data 116 are created or updated by the user application(s) 114 at the primary site 110
  • the packets of the data 116 are also created and/or updated by user application(s) 124 executable by one or more computer processors at the nearby safe site 120 .
  • the user application(s) 124 at the nearby safe site 120 store the data 116 via a data I/O interface 128 on the second data storage device 122 thereby achieving replication of the data 116 at the nearby safe site 120 . Additionally as packets of the data 116 are created or updated by the user application(s) 124 at the nearby safe site 120 , the packets of the data 116 are also created and/or updated by user application(s) 114 executable by one or more computer processors at the primary site 110 .
  • the user application(s) 114 at the primary site 110 store the data 116 via a data I/O interface 118 on the primary data storage device 112 thereby achieving replication of the data 116 at the primary site 110 . This is true since user application(s) 114 and 124 are both active simultaneously and potentially in a load balanced architecture.
  • the user application(s) 114 at the primary site 110 and the user application(s) 124 at the nearby safe site 120 may be corresponding instances of the same application(s). Since the user application(s) 124 are operating at the nearby safe site 120 simultaneously with the user application(s) 114 at the primary site 110 , both the primary site 110 user application(s) 114 and the nearby safe site 120 user application(s) 124 are considered active and the present embodiment may be referred to as an active/active extended distance data recovery system 200 .
  • VIC 150 monitors operation of the primary site 110 , and upon detection of a problem, redirects resources accessing the data 116 to the second data storage device 122 or the third data storage device 132 as appropriate depending upon whether the asynchronous data replication process between nearby safe site 120 and the disaster recovery site 110 has been completed.
  • user application(s) 114 upon failure of user application(s) 114 , since user application(s) 124 is(are) also active user communications will be directed solely to user application(s) 124 through normal load balancing mechanisms. Users would not experience an outage as user application(s) 124 provides(provide) dynamic redundancy.
  • user application(s) 124 is(are) stopped by VIC 150 and user application(s) 134 is(are) restarted by VIC 150 after it directs and verifies storage device 122 at nearby safe site 120 to complete replicating all of its changed data to storage device 132 at disaster recovery site 130 .
  • FIG. 3 shows another embodiment of an extended distance data recovery system 300 .
  • the extended distance data recovery system 300 of FIG. 3 includes a number of elements in common with the systems 100 , 200 of FIGS. 1 and 2 , and corresponding elements are referenced using the same numerals.
  • the primary site 110 in the system 300 of FIG. 3 includes a plurality of first data storage devices 312 A- 312 H each having data 316 A- 316 H stored thereon.
  • the data 316 A- 316 H may be created, updated, and/or accessed by one or more user applications (not shown).
  • the data 316 A- 316 H is synchronously replicated onto the second data storage device(s) 122 at the nearby safe site 120 .
  • the data 316 A- 316 H may be synchronously replicated at the application level and/or the storage level as previously described in connection with the system 200 of FIG. 2 or the system 100 of FIG. 1 . Regardless of the manner in which the data is replicated from the primary site 110 to the nearby safe site 120 , data replication is directed by VIC 150 .
  • the first data storage devices 312 A- 312 H may be organized into groups. For example, a first group may include first data storage devices 312 A- 312 D and a second group may include first data storage devices 312 E- 312 H.
  • a first group may include first data storage devices 312 A- 312 D
  • a second group may include first data storage devices 312 E- 312 H.
  • the data 316 A- 316 H may be asynchronously replicated to more than one disaster recovery site.
  • system 300 includes two disaster recovery sites 330 A- 330 B.
  • the data 316 A- 316 D originating from the first group of first data storage devices 312 A- 312 D is replicated to the first disaster recovery site 330 A
  • the data 316 E- 316 H originating from the second group of first data storage devices 312 E- 312 H is replicated to the second disaster recovery site 330 B
  • the first disaster recovery site 330 A may include a number of third data storage devices 332 A- 332 D on which the data 316 A- 316 D is replicated
  • the second disaster recovery site 330 B may include a number of third data storage devices 332 E- 332 H on which the data 316 E- 316 H is replicated.
  • VIC 150 monitors operation of the primary site 110 , and upon detection of a problem, redirects resources accessing the data 316 A- 316 H to the second data storage device 122 or the third data storage devices 332 A- 332 H as appropriate depending upon whether the asynchronous data replication process between the nearby safe site 120 and the disaster recovery sites 330 A- 330 B has been completed.

Abstract

Systems and methods operating over extended distances provide for recovery of data and operational continuity of computer applications accessing data within an information technology system if an event occurs effecting access to the data. In one embodiment, an extended distance data recovery system (100) includes first, second and third data storage devices (112, 122, 132) located at respective first, second and third sites (110, 120, 130). The second and third sites (120, 130) are remotely located from the first site (110) with the second site (120) being nearby the first site (110). The first data storage device (112) has data (116) stored thereon. A computer executable control process (150) directs synchronous replication of the data (116), either at the storage level or at the application level, onto the second data storage device (122). The control process (150) also directs asynchronous replication of the data (116) from the second data storage device (122) onto the third data storage device (132) and coordinates among the three sites (110, 120, 130) the state of application servers, storage replication, network address changes, and other prerequisite aspects of the IT infrastructure required to allow the application servers to successfully start at the disaster recovery site.

Description

    RELATED APPLICATION INFORMATION
  • This application is a continuation of and claims priority from U.S. patent application Ser. No. 11/534,546, entitled “NO DATA LOSS IT DISASTER RECOVERY OVER EXTENDED DISTANCES” filed on Sep. 22, 2006, which application claims priority from United States Provisional Application Ser. No. 60/722,369, entitled “NO DATA LOSS IT DISASTER RECOVERY OVER EXTENDED DISTANCES” filed on Sep. 30, 2005. The entire disclosures of the referenced applications are incorporated herein by reference.
    • FIELD OF THE INVENTION
  • The present invention relates generally to information technology systems, and more particularly to providing zero loss data protection and automated data recovery over extended distances.
    • BACKGROUND OF THE INVENTION
  • In an information technology (IT) system, it is often desirable to replicate data stored at one location at another location so that if an event occurs (e.g., an equipment failure, a power failure, a natural disaster, or a terrorist attack or other man-made event) that damages or otherwise renders the data at the first location inaccessible, the data can be recovered from the second location. The first location may be referred to as the primary site, the second location may be referred to as the disaster recovery site, and such an occurrence may be referred to as a disaster event. In order to provide sufficient assurance that the disaster recovery site will not be effected by the disaster event effecting the primary site, the disaster recovery site must be geographically separated from the primary site by a sufficient distance.
  • When replicating the data at the disaster recovery site, it may be desirable to do so in a synchronous manner such that when data is created, updated or stored at the primary site, such data is replicated to the disaster recovery site first and only after receiving an acknowledgement from the disaster recovery site of successful replication is the data write considered complete and successful at the primary site. This allows for no lost data if the primary site goes down. However, excessive roundtrip packet delays resulting from long distances and other network conditions between the primary and disaster recovery sites prevents synchronous replication of data from the primary site to the disaster recovery site. This difficulty is present regardless of whether data replication takes place in the storage, middleware, or application layer of the IT system. Excessive roundtrip packet delays can be unacceptable since operation of applications creating, updating or accessing the data will be delayed while awaiting confirmation that the data has been replicated at the disaster recovery site.
    • SUMMARY OF THE INVENTION
  • Accordingly, the present invention introduces an intermediary site between the primary site and the disaster recovery site. The primary site may be referred to herein as the first site, the intermediary site may be referred to herein as the nearby safe site or the second site, and the disaster recovery site may be referred to herein as the third site. The data is replicated from the primary site to the nearby safe site and then subsequently replicated from the nearby safe site to the disaster recovery site. The nearby safe site may be geographically remote from the primary site such that the nearby safe site would be expected to survive a disaster event effecting the primary site for some period of time after the primary site goes down, but not necessarily survive indefinitely. However, the nearby safe site is located close enough to the primary site such that synchronous data replication is possible between the primary site and the nearby safe site without encountering unacceptable roundtrip packet delays. The disaster recovery site is located far enough from the primary site that the disaster recovery site would be expected to survive the disaster event effecting the primary site. Because the data has already been replicated to the nearby safe site, asynchronous replication of the data from the nearby safe site to the disaster recovery site is acceptable.
  • The nearby safe site includes a number of desirable characteristics. For example, the nearby safe site is close enough to the primary site that roundtrip packet delays between the nearby safe site and the primary site would not be detrimental to the user software applications. A typical maximum distance is, for example, one-hundred kilometers or even two-hundred kilometers, although actual allowable distances depend on the actual network paths traversed, roundtrip packet delays encountered, and the software application sensitivity to roundtrip packet delays. The nearby safe site can be run in a “lights out” configuration with no regular staffing requirements and is expected to operate in case of chemical, biological, or nuclear contamination. The primary hardware components at the nearby safe site are data storage devices as well as application servers. The data on the data storage devices could optionally be encrypted allowing the nearby site and its assets to be shared among multiple customers at different physical locations. The nearby site is physically protected to continue to operate for a relatively short period of time after the primary site has sustained a disaster, thereby allowing for the completion of the data transfer that has been buffered at this site to the disaster recovery site.
  • According to one aspect of the present invention, an extended distance data recovery system includes a first data storage device located at a first site, a second data storage device located at a second site, a third data storage device located at a third site, and a computer executable control process coordinating all three sites. The first data storage device has data stored thereon. The second data storage device is communicatively connected with the first data storage device, and the third data storage device is communicatively connected with the second data storage device. The computer executable control process is executable to direct synchronous replication of the data onto the second data storage device. The control process is also executable to direct asynchronous replication of the data from the second data storage device onto the third data storage device. The computer executable control process is executable to coordinate among the three sites the state of application servers, storage replication, network address changes, and other prerequisite aspects of the IT infrastructure required to allow the application servers to successfully start at the disaster recovery site.
  • According to another aspect of the present invention, a method for providing recovery of data and operational continuity of computer applications accessing the data if an event occurs effecting access to the data on an information technology system is provided includes the step of storing the data at a first site. The data is synchronously replicated from the first site to a second site under the direction of a computer executable control process. The data is asynchronously replicated from the second site onto a third site, also under the direction of the control process. The operational status of the first site is monitored, and, upon occurrence of the event, location identifying information associated with the data is updated so that computer applications access the data from the second site and/or the third site.
  • These and other aspects and advantages of the present invention will be apparent upon review of the following Detailed Description when taken in conjunction with the accompanying figures.
    • DESCRIPTION OF THE DRAWINGS
  • For a more complete understanding of the present invention and further advantages thereof, reference is now made to the following Detailed Description, taken in conjunction with the drawings, in which:
  • FIG. 1 is block diagram showing one embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention;
  • FIG. 2 is block diagram showing another embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention; and
  • FIG. 3 is block diagram showing one more embodiment of an extended distance data recovery system and the operation thereof in accordance with the present invention.
    •  DETAILED DESCRIPTION
  • FIG. 1 illustrates one embodiment of an extended distance data recovery system 100. The system 100 includes a first data storage device 112 located at a first site 110 (the primary site 110), a second data storage device 122 located at a second site 120 (the nearby safe site 120 or intermediary site 120), and a third data storage device 132 located at a third site 130 (the disaster recovery site 130). The data storage devices 112, 122, 132 may, for example, be storage area network (SAN) devices each including a group of networked data storage devices (e.g., hard drives, CD or DVD drives, tape drives, flash memory devices, etc.). In other embodiments one or more of the first, second and third data storage devices 112, 122, 132 may, for example, be devices other than a storage area network device such as, for example, an individual hard drive. In this regard, data replication may need to be handled at a middleware or application layer level.
  • The primary site 110 may be geographically remote from the other sites such that in the event of an occurrence (e.g., an equipment failure, a power failure, a natural disaster, a terrorist attack or other man-made event) that causes loss of data access at the primary site 110, conditions effecting the operation of the primary site 110 may not necessarily effect the operations at the other two sites 120, 130. In this regard, the primary and nearby safe sites 110, 120 may, for example, be located in different buildings or in different towns as long as the primary and nearby safe sites 110, 120 are close enough to one another that a roundtrip packet delay time between the primary and nearby safe sites 110, 120 is within an acceptable range, and the primary and disaster recovery sites 110, 130 may, for example, be located in different towns, in different states, or even in different countries without regard to a roundtrip packet delay time therebetween. Regardless of the location of each site 110, 120, 130 relative to each other, they are enabled for communication therebetween via a suitable data network so that data created and/or stored at one site can be communicated to and replicated at another site. The data network may include various private and/or publicly shared wired and/or wireless portions.
  • One or more user applications 114 are executable by one or more computer processors or the like at the primary site 110. The user application(s) 114 create, update, and/or access data 116 that is stored, via a data input/output (I/O) interface 118 on the first data storage device 112.
  • The extended distance data recovery system 100 also includes a virtual integration console 150 (VIC 150). VIC 150 may also be referred to herein the control process 150 or control application 150. In one embodiment, VIC 150 is implemented in software executable by a computer processor, and there can be instances of VIC 150 executing on computer systems at each of the primary site 110, nearby safe site 120 and the disaster recovery site 130. Each instance of VIC 150 interfaces with the other instance of VIC 150, and in FIG. 1 all three instances of VIC 150 are represented as a single block.
  • VIC 150 directs the replication of the data 116 from the primary site 110 to the nearby safe site 120. In the present embodiment, VIC 150 directs replication of the data 116 from the primary site 110 to the nearby safe site 120 to take place in a synchronous manner at the storage level. In this regard, as packets of the data 116 are written to the first data storage device 112, the packets of the data 116 are also written to the second data storage device 122 and confirmation that the data replication operation has been completed is provided by the second data storage device 122 to the first data storage device 112 at the primary site 110. Although the roundtrip packet delay time between the primary and nearby safe sites 110, 120 depends on a number of factors including the type of communication network equipment used and overall network traffic, the primary site 110 and the nearby safe site 120 should, in general, be sufficiently proximate to one another such that the roundtrip packet delay time between the primary and nearby safe sites 110, 120 is not so long in duration that normal operation of the user application(s) is unacceptably impacted. While the geographic distance between the primary and nearby safe sites 110, 120 providing such an acceptable roundtrip packet delay time can vary greatly from one situation to another, geographic distances in the range of 100 kilometers up to 200 kilometers may be possible.
  • In addition to directing replication of the data 116 to the second data storage device 122 at the nearby safe site, VIC 150 also directs replication of the data 116 from the second data storage device 122 to the third data storage device 132 at the disaster recovery site 130. In the present embodiment, VIC 150 directs replication of the data 116 from the nearby safe site 120 to the disaster recovery site 130 to take place in an asynchronous manner. In this regard, the data 116 is replicated from the second data storage device 122 to the third data storage device 132 when resources at the nearby safe and disaster sites 120, 130 are available to copy the data 116. In this manner, the data 116 is initially replicated at the nearby safe site 120 and thereafter replicated to the disaster recovery site 130. The asynchronous data replication may occur periodically (e.g., every day, every hour, every minute, or as fast as the communication throughput between nearby safe site 120 and disaster recovery site 130 allow), or may occur in response to certain predefined events. The asynchronous data transfer protocol allows the primary site 110 to effectively be decoupled from the disaster recovery site 130. Thus, there is no need for the user application(s) 114 to wait for the data to be replicated to the disaster recovery site 130 before continuing with their operations. This configuration permits the disaster recovery site 130 to be located at a distance from the primary site 110 that is much greater than the distance between the nearby safe site 120 and the primary site 110. For example, the disaster recovery site 130 may be located in a different state or in a different country than the primary site 110. This provides even greater protection of the data 116 and continuity of the user application(s) 114 from the occurrence of a disaster event.
  • VIC 150 also monitors the operational status of the primary site 110. If a failure is detected and the application(s) 114 at the primary site 110 are not operating or are not able to access the data 116 from the first data storage device 112, VIC 150 makes the data 116 available from the nearby safe site 120 and/or the disaster recovery site 130 as appropriate. In this regard, if asynchronous replication of the data 116 from the second data storage device 122 to the third data storage device 132 is complete, then VIC 150 directs resources to access the data 116 from the third data storage device 132 instead of from the first data storage device 112. For example, one or more user application(s) 134 executable on computer systems located at the disaster recovery site 130 may access the data 116 from the third data storage device 132 via a data I/O interface 138. The disaster recovery site 130 user application(s) 134 may be the same as and/or provide the same functionality as the user application(s) 114 at the primary site 110 in order to provide continuity of operations formerly accomplished at the primary site 110. If, however, asynchronous replication of the data 116 from the second data storage device 122 to the third data storage device 132 has not been completed, then VIC 150 directs completion of the asynchronous data replication process. In the meantime, VIC 150 may direct resources to access the data 116 from the second data storage device 122 until the asynchronous data replication process is complete.
  • The user application(s) 134 at the disaster recovery site 130 do not operate while the primary site 110 user application(s) 114 operate, but when the primary site 110 goes down, VIC 150 activates the application(s) 134 at the disaster recovery site. In this regard, the primary site 110 user application(s) 114 are considered active, the disaster recovery site 130 user application(s) 134 are considered passive, and therefore the present embodiment may be referred to as an active/passive extended distance data recovery system 100.
  • Redirection of resources accessing the data 116 to the nearby safe site and/or disaster recovery site may be accomplished by VIC 150 in a number of manners. One manner is by providing updated IP address information associated with the data 116 to one or more domain name servers 170 (DNSs 170).
  • FIG. 2 shows another embodiment of an extended distance data recovery system 200. The extended distance data recovery system 200 of FIG. 2 includes a number of elements in common with the system 100 of FIG. 1, and corresponding elements are referenced using the same numerals. In the system 200 of FIG. 2, VIC 150 directs replication of the data 116 from the primary site 110 to the nearby safe site 120 to take place in a synchronous manner at the application level rather than the storage level. In this regard, as packets of the data 116 are created or updated by the user application(s) 114 at the primary site 110, the packets of the data 116 are also created and/or updated by user application(s) 124 executable by one or more computer processors at the nearby safe site 120. The user application(s) 124 at the nearby safe site 120 store the data 116 via a data I/O interface 128 on the second data storage device 122 thereby achieving replication of the data 116 at the nearby safe site 120. Additionally as packets of the data 116 are created or updated by the user application(s) 124 at the nearby safe site 120, the packets of the data 116 are also created and/or updated by user application(s) 114 executable by one or more computer processors at the primary site 110. The user application(s) 114 at the primary site 110 store the data 116 via a data I/O interface 118 on the primary data storage device 112 thereby achieving replication of the data 116 at the primary site 110. This is true since user application(s) 114 and 124 are both active simultaneously and potentially in a load balanced architecture.
  • The user application(s) 114 at the primary site 110 and the user application(s) 124 at the nearby safe site 120 may be corresponding instances of the same application(s). Since the user application(s) 124 are operating at the nearby safe site 120 simultaneously with the user application(s) 114 at the primary site 110, both the primary site 110 user application(s) 114 and the nearby safe site 120 user application(s) 124 are considered active and the present embodiment may be referred to as an active/active extended distance data recovery system 200.
  • As with the system 100 of FIG. 1, VIC 150 monitors operation of the primary site 110, and upon detection of a problem, redirects resources accessing the data 116 to the second data storage device 122 or the third data storage device 132 as appropriate depending upon whether the asynchronous data replication process between nearby safe site 120 and the disaster recovery site 110 has been completed. In this embodiment, upon failure of user application(s) 114, since user application(s) 124 is(are) also active user communications will be directed solely to user application(s) 124 through normal load balancing mechanisms. Users would not experience an outage as user application(s) 124 provides(provide) dynamic redundancy. At a convenient time which provides a minimal amount of operational impact, user application(s) 124 is(are) stopped by VIC 150 and user application(s) 134 is(are) restarted by VIC 150 after it directs and verifies storage device 122 at nearby safe site 120 to complete replicating all of its changed data to storage device 132 at disaster recovery site 130.
  • FIG. 3 shows another embodiment of an extended distance data recovery system 300. The extended distance data recovery system 300 of FIG. 3 includes a number of elements in common with the systems 100, 200 of FIGS. 1 and 2, and corresponding elements are referenced using the same numerals. The primary site 110 in the system 300 of FIG. 3 includes a plurality of first data storage devices 312A-312H each having data 316A-316H stored thereon. The data 316A-316H may be created, updated, and/or accessed by one or more user applications (not shown). The data 316A-316H is synchronously replicated onto the second data storage device(s) 122 at the nearby safe site 120. In this regard, the data 316A-316H may be synchronously replicated at the application level and/or the storage level as previously described in connection with the system 200 of FIG. 2 or the system 100 of FIG. 1. Regardless of the manner in which the data is replicated from the primary site 110 to the nearby safe site 120, data replication is directed by VIC 150.
  • The first data storage devices 312A-312H may be organized into groups. For example, a first group may include first data storage devices 312A-312D and a second group may include first data storage devices 312E-312H. When the data 316A-316H is asynchronously replicated from the nearby safe site 120, the data 316A-316H may be asynchronously replicated to more than one disaster recovery site. For example, system 300 includes two disaster recovery sites 330A-330B. The data 316A-316D originating from the first group of first data storage devices 312A-312D is replicated to the first disaster recovery site 330A, and the data 316E-316H originating from the second group of first data storage devices 312E-312H is replicated to the second disaster recovery site 330B. In this regard, the first disaster recovery site 330A may include a number of third data storage devices 332A-332D on which the data 316A-316D is replicated, and the second disaster recovery site 330B may include a number of third data storage devices 332E-332H on which the data 316E-316H is replicated. Regardless of the manner in which the data is replicated from the nearby safe site 120 to the disaster recovery sites 330A-330B, data replication is directed by VIC 150.
  • As with the systems 100, 200 of FIGS. 1 and 2, VIC 150 monitors operation of the primary site 110, and upon detection of a problem, redirects resources accessing the data 316A-316H to the second data storage device 122 or the third data storage devices 332A-332H as appropriate depending upon whether the asynchronous data replication process between the nearby safe site 120 and the disaster recovery sites 330A-330B has been completed.
  • While various embodiments of the present invention have been described in detail, further modifications and adaptations of the invention may occur to those skilled in the art. However, it is to be expressly understood that such modifications and adaptations are within the spirit and scope of the present invention.

Claims (19)

1-32. (canceled)
33. An active/active extended distance data recovery system comprising:
a first data storage device located at a first site, said first data storage device storing the data thereon;
a second data storage device located at a second site, said second data storage device being communicatively connected with said first data storage device;
a third data storage device located at a third site, said third data storage device being communicatively connected with said second data storage device; and
a computer executable control process executable to direct synchronous replication of the data onto said second data storage device;
said control process being further executable to direct asynchronous replication of the data from said second data storage device onto said third data storage device, wherein said control process directs the synchronous and asynchronous replication of the data such that the data is initially replicated onto said second data storage device and thereafter replicated from said second data storage device onto said third data storage device with operation of a user application at the first site involving the data being allowed to continue during the asynchronous replication of the data from said second data storage device to said third data storage device; and
said control process directing synchronous replication of the data onto said second storage device at an application level such that as packets of data are created or updated by one or more user applications executing at the first site the packets of data are also created or updated by user applications executing at the second site.
34. The system of claim 33, wherein said control process is further executable to monitor an operational status of said first data storage device and, upon occurrence of an event effecting availability of the data from said first data storage device, update location identifying information associated with the data wherein a computer application accesses the data from one of said second site and said third site.
35. The system of claim 33, wherein said third site is geographically separated from said first and second sites, and wherein said second site is geographically separated from said first and third sites.
36. The system of claim 35, wherein a maximum allowable geographical separation distance between said first and second sites varies depending upon application sensitivity to a roundtrip packet delay time between said first and second sites and architectural and operational conditions of a data network connecting said first and second sites.
37. The system of claim 33, wherein said control process is executable on a computer system located at a fourth site.
38. An active/passive extended distance data recovery system comprising:
a first data storage device located at a first site, said first data storage device storing the data thereon;
a second data storage device located at a second site, said second data storage device being communicatively connected with said first data storage device;
a third data storage device located at a third site, said third data storage device being communicatively connected with said second data storage device; and
a computer executable control process executable to direct synchronous replication of the data onto said second data storage device;
said control process being further executable to direct asynchronous replication of the data from said second data storage device onto said third data storage device, wherein said control process directs the synchronous and asynchronous replication of the data such that the data is initially replicated onto said second data storage device and thereafter replicated from said second data storage device onto said third data storage device with operation of a user application at the first site involving the data being allowed to continue during the asynchronous replication of the data from said second data storage device to said third data storage device; and
said control process directing synchronous replication of the data onto said second storage device at a data storage level such that as packets of data are written to the first data storage device, the packets of data are also written to the second data storage device and confirmation that writing of the data packets to the second data storage device has been completed is provided by the second data storage device to the first data storage device.
39. The system of claim 38, wherein said control process is further executable to monitor an operational status of said first data storage device and, upon occurrence of an event effecting availability of the data from said first data storage device, update location identifying information associated with the data wherein a computer application accesses the data from one of said second site and said third site.
40. The system of claim 38, wherein said third site is geographically separated from said first and second sites, and wherein said second site is geographically separated from said first and third sites.
41. The system of claim 40, wherein a maximum allowable geographical separation distance between said first and second sites varies depending upon application sensitivity to a roundtrip packet delay time between said first and second sites and architectural and operational conditions of a data network connecting said first and second sites.
42. The system of claim 38, wherein said control process is executable on a computer system located at a fourth site.
43. A method for providing recovery of data and operational continuity of computer applications accessing the data if an event occurs effecting access to the data on an information technology system, said method comprising the steps of:
storing the data at a first site;
synchronously replicating the data from the first site to a second site, wherein synchronous replication of the data is performed under the direction of a computer executable control process, and wherein said step of synchronously replicating the data from the first site to the second site is performed at an application level such that as packets of data are created or updated by one or more user applications executing at the first site the packets of data are also created or updated by user applications executing at the second site;
asynchronously replicating the data from the second site onto a third site, wherein asynchronous replication of the data is performed under the direction of the control process after synchronous replication of the data to the second site with operation of computer applications at the first site involving the data being allowed to continue during the asynchronous replication of the data from the second site to the third site;
monitoring an operational status of the first site; and
updating, upon occurrence of the event, location identifying information associated with the data wherein the computer applications access the data from at least one of the second site and the third site.
44. The method of claim 43 wherein, in said steps of synchronously replicating and asynchronously replicating, the third site is geographically separated from the first and second sites, and wherein the second site is geographically separated from the first and third sites.
45. The method of claim 44 wherein, in said step of synchronously replicating, a maximum allowable geographical separation distance from the first site and the second site varies depending upon application sensitivity to a roundtrip packet delay time between said first and second sites and architectural and operational conditions of a data network connecting said first and second sites.
46. The method of claim 43 further comprising:
executing the control process on a computer system located at a fourth site.
47. A method for providing recovery of data and operational continuity of computer applications accessing the data if an event occurs effecting access to the data on an information technology system, said method comprising the steps of:
storing the data at a first site;
synchronously replicating the data from the first site to a second site, wherein synchronous replication of the data is performed under the direction of a computer executable control process, and
wherein said step of synchronously replicating the data from the first site to the second site is performed at a data storage level such that such that as packets of data are written to a data storage device at the first site, the packets of data are also written to a data storage device at the second site and confirmation that writing of the data packets to the data storage device at the second site has been completed is provided by the data storage device at the second site to the data storage device at the first site;
asynchronously replicating the data from the second site onto a third site, wherein asynchronous replication of the data is performed under the direction of the control process after synchronous replication of the data to the second site with operation of computer applications at the first site involving the data being allowed to continue during the asynchronous replication of the data from the second site to the third site;
monitoring an operational status of the first site; and
updating, upon occurrence of the event, location identifying information associated with the data wherein the computer applications access the data from at least one of the second site and the third site.
48. The method of claim 47 wherein, in said steps of synchronously replicating and asynchronously replicating, the third site is geographically separated from the first and second sites, and wherein the second site is geographically separated from the first and third sites.
49. The method of claim 48 wherein, in said step of synchronously replicating, a maximum allowable geographical separation distance from the first site and the second site varies depending upon application sensitivity to a roundtrip packet delay time between said first and second sites and architectural and operational conditions of a data network connecting said first and second sites.
50. The method of claim 47 further comprising:
executing the control process on a computer system located at a fourth site.
US12/500,016 2005-09-30 2009-07-09 No data loss it disaster recovery over extended distances Abandoned US20090271658A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/500,016 US20090271658A1 (en) 2005-09-30 2009-07-09 No data loss it disaster recovery over extended distances

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US72236905P 2005-09-30 2005-09-30
US11/534,546 US7577868B2 (en) 2005-09-30 2006-09-22 No data loss IT disaster recovery over extended distances
US12/500,016 US20090271658A1 (en) 2005-09-30 2009-07-09 No data loss it disaster recovery over extended distances

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/534,546 Continuation US7577868B2 (en) 2005-09-30 2006-09-22 No data loss IT disaster recovery over extended distances

Publications (1)

Publication Number Publication Date
US20090271658A1 true US20090271658A1 (en) 2009-10-29

Family

ID=37903270

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/534,546 Expired - Fee Related US7577868B2 (en) 2005-09-30 2006-09-22 No data loss IT disaster recovery over extended distances
US12/500,016 Abandoned US20090271658A1 (en) 2005-09-30 2009-07-09 No data loss it disaster recovery over extended distances

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/534,546 Expired - Fee Related US7577868B2 (en) 2005-09-30 2006-09-22 No data loss IT disaster recovery over extended distances

Country Status (6)

Country Link
US (2) US7577868B2 (en)
AU (1) AU2006297142B2 (en)
CA (1) CA2621238C (en)
DE (1) DE112006002483T5 (en)
GB (1) GB2445700B (en)
WO (1) WO2007041286A2 (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090327805A1 (en) * 2008-06-26 2009-12-31 Microsoft Corporation Minimizing data loss in asynchronous replication solution using distributed redundancy
CN102591741A (en) * 2010-11-29 2012-07-18 国际商业机器公司 Method and system for realizing disaster recovery utilizing collapsible virtualized capacity
US8522068B2 (en) 2011-05-02 2013-08-27 International Business Machines Corporation Coordinated disaster recovery production takeover operations
US8671308B2 (en) 2011-05-02 2014-03-11 International Business Machines Corporation Optimizing disaster recovery systems during takeover operations
CN103744753A (en) * 2013-12-26 2014-04-23 北京交控科技有限公司 Data interaction method and device for dual systems
WO2014080438A1 (en) * 2012-11-20 2014-05-30 Hitachi, Ltd. Storage system and data management method
US8850139B2 (en) 2011-05-11 2014-09-30 International Business Machines Corporation Changing ownership of cartridges
US9104607B2 (en) 2012-10-31 2015-08-11 International Business Machines Corporation Simulation engine for use in disaster recovery virtualization
US9104625B2 (en) 2012-12-11 2015-08-11 International Business Machines Corporation Disaster recovery internet protocol address failover
US9508470B2 (en) 2013-10-29 2016-11-29 General Electric Company Vibration damage repair in dynamoelectric machines
US20170060710A1 (en) * 2015-08-28 2017-03-02 Netapp Inc. Trust relationship migration for data mirroring

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7934116B2 (en) * 2005-09-30 2011-04-26 Lockheed Martin Corporation Disaster recover/continuity of business adaptive solution framework
US7779147B1 (en) * 2006-06-30 2010-08-17 Amazon Technologies, Inc. Method and system for advertisement placement based on network trail proximity
US7702953B2 (en) * 2007-01-04 2010-04-20 International Business Machines Corporation Storage management in cascaded replication of data
CA2593169A1 (en) * 2007-07-06 2009-01-06 Tugboat Enterprises Ltd. System and method for computer data recovery
US7669080B2 (en) * 2007-08-16 2010-02-23 International Business Machines Corporation Reducing likelihood of data loss during failovers in high-availability systems
US8984326B2 (en) * 2007-10-31 2015-03-17 Hewlett-Packard Development Company, L.P. Testing disaster recovery elements
US8209443B2 (en) * 2008-01-31 2012-06-26 Hewlett-Packard Development Company, L.P. System and method for identifying lost/stale hardware in a computing system
US7925917B1 (en) 2008-04-03 2011-04-12 United Services Automobile Association (Usaa) Systems and methods for enabling failover support with multiple backup data storage structures
US8135838B2 (en) 2008-04-08 2012-03-13 Geminare Incorporated System and method for providing data and application continuity in a computer system
US8055943B2 (en) * 2009-04-24 2011-11-08 International Business Machines Corporation Synchronous and asynchronous continuous data protection
US9191437B2 (en) * 2009-12-09 2015-11-17 International Business Machines Corporation Optimizing data storage among a plurality of data storage repositories
US8359493B2 (en) * 2010-07-29 2013-01-22 Computer Associates Think, Inc. Mechanism to provide assured recovery for distributed application
WO2014002094A2 (en) 2012-06-25 2014-01-03 Storone Ltd. System and method for datacenters disaster recovery
US9594822B1 (en) * 2013-03-13 2017-03-14 EMC IP Holding Company LLC Method and apparatus for bandwidth management in a metro cluster environment
CN103593266B (en) * 2013-11-12 2016-06-22 浪潮(北京)电子信息产业有限公司 A kind of double hot standby method based on arbitration disk mechanism
CN104360918B (en) * 2014-10-15 2017-08-29 许继电气股份有限公司 A kind of intelligent Substation System self diagnosis and self-recovery method
CN104317679B (en) * 2014-11-17 2016-06-08 国电南京自动化股份有限公司 A kind of SCADA system is based on the communication fault-tolerance method of thread redundancy
CN105893386B (en) 2015-01-04 2021-08-06 伊姆西Ip控股有限责任公司 Method and apparatus for processing transactions in a synchronous replication system
US10387273B2 (en) 2016-09-16 2019-08-20 Oracle International Corporation Hierarchical fault tolerance in system storage
US10733053B1 (en) 2018-01-31 2020-08-04 Pure Storage, Inc. Disaster recovery for high-bandwidth distributed archives
US10795787B1 (en) * 2018-10-31 2020-10-06 EMC IP Holding Company LLC Disaster recovery for software defined network attached storage using storage array asynchronous data replication
US10795786B1 (en) * 2018-10-31 2020-10-06 EMC IP Holding Company LLC Disaster recovery for software defined network attached storage using storage array synchronous data replication

Citations (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5592618A (en) * 1994-10-03 1997-01-07 International Business Machines Corporation Remote copy secondary data copy validation-audit function
US5619644A (en) * 1995-09-18 1997-04-08 International Business Machines Corporation Software directed microcode state save for distributed storage controller
US5742792A (en) * 1993-04-23 1998-04-21 Emc Corporation Remote data mirroring
US5870537A (en) * 1996-03-13 1999-02-09 International Business Machines Corporation Concurrent switch to shadowed device for storage controller and device errors
US6044444A (en) * 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US6327671B1 (en) * 1998-11-18 2001-12-04 International Business Machines Corporation Delta compressed asynchronous remote copy
US6389552B1 (en) * 1998-12-31 2002-05-14 At&T Corp Methods and systems for remote electronic vaulting
US20030018927A1 (en) * 2001-07-23 2003-01-23 Gadir Omar M.A. High-availability cluster virtual server system
US20030074600A1 (en) * 2000-04-12 2003-04-17 Masaharu Tamatsu Data backup/recovery system
US6601187B1 (en) * 2000-03-31 2003-07-29 Hewlett-Packard Development Company, L. P. System for data replication using redundant pairs of storage controllers, fibre channel fabrics and links therebetween
US20030188233A1 (en) * 2002-03-28 2003-10-02 Clark Lubbers System and method for automatic site failover in a storage area network
US20030188218A1 (en) * 2002-03-26 2003-10-02 Clark Lubbers System and method for active-active data replication
US6643765B1 (en) * 1995-08-16 2003-11-04 Microunity Systems Engineering, Inc. Programmable processor with group floating point operations
US6658540B1 (en) * 2000-03-31 2003-12-02 Hewlett-Packard Development Company, L.P. Method for transaction command ordering in a remote data replication system
US6658590B1 (en) * 2000-03-30 2003-12-02 Hewlett-Packard Development Company, L.P. Controller-based transaction logging system for data recovery in a storage area network
US20040034808A1 (en) * 2002-08-16 2004-02-19 International Business Machines Corporation Method, system, and program for providing a mirror copy of data
US20040039888A1 (en) * 2002-08-21 2004-02-26 Lecrone Douglas E. Storage automated replication processing
US20040153708A1 (en) * 2002-05-31 2004-08-05 Joshi Darshan B. Business continuation policy for server consolidation environment
US6779073B2 (en) * 1993-10-15 2004-08-17 Image Telecommunications Corporation Memory device having a systematic arrangement of logical data locations and having plural data portals
US20040243650A1 (en) * 2003-06-02 2004-12-02 Surgient, Inc. Shared nothing virtual cluster
US20050015657A1 (en) * 2003-06-27 2005-01-20 Hitachi, Ltd. Data center system and method for controlling the same
US20050198452A1 (en) * 2004-03-02 2005-09-08 Naoki Watanabe Method and apparatus of remote copy for multiple storage subsystems
US20060047896A1 (en) * 2004-08-25 2006-03-02 Lu Nguyen Storing parity information for data recovery
US7370228B2 (en) * 2004-09-01 2008-05-06 Hitachi, Ltd. Data processing system and copy processing method thereof

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6643795B1 (en) 2000-03-30 2003-11-04 Hewlett-Packard Development Company, L.P. Controller-based bi-directional remote copy system with storage site failover capability
JP2005062928A (en) * 2003-08-11 2005-03-10 Hitachi Ltd Remote copy system using two or more sites

Patent Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5742792A (en) * 1993-04-23 1998-04-21 Emc Corporation Remote data mirroring
US6779073B2 (en) * 1993-10-15 2004-08-17 Image Telecommunications Corporation Memory device having a systematic arrangement of logical data locations and having plural data portals
US5592618A (en) * 1994-10-03 1997-01-07 International Business Machines Corporation Remote copy secondary data copy validation-audit function
US6643765B1 (en) * 1995-08-16 2003-11-04 Microunity Systems Engineering, Inc. Programmable processor with group floating point operations
US5619644A (en) * 1995-09-18 1997-04-08 International Business Machines Corporation Software directed microcode state save for distributed storage controller
US5870537A (en) * 1996-03-13 1999-02-09 International Business Machines Corporation Concurrent switch to shadowed device for storage controller and device errors
US6044444A (en) * 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US6327671B1 (en) * 1998-11-18 2001-12-04 International Business Machines Corporation Delta compressed asynchronous remote copy
US6389552B1 (en) * 1998-12-31 2002-05-14 At&T Corp Methods and systems for remote electronic vaulting
US6658590B1 (en) * 2000-03-30 2003-12-02 Hewlett-Packard Development Company, L.P. Controller-based transaction logging system for data recovery in a storage area network
US20040044865A1 (en) * 2000-03-31 2004-03-04 Sicola Stephen J. Method for transaction command ordering in a remote data replication system
US6601187B1 (en) * 2000-03-31 2003-07-29 Hewlett-Packard Development Company, L. P. System for data replication using redundant pairs of storage controllers, fibre channel fabrics and links therebetween
US6658540B1 (en) * 2000-03-31 2003-12-02 Hewlett-Packard Development Company, L.P. Method for transaction command ordering in a remote data replication system
US20030074600A1 (en) * 2000-04-12 2003-04-17 Masaharu Tamatsu Data backup/recovery system
US20030018927A1 (en) * 2001-07-23 2003-01-23 Gadir Omar M.A. High-availability cluster virtual server system
US20030188218A1 (en) * 2002-03-26 2003-10-02 Clark Lubbers System and method for active-active data replication
US20030188233A1 (en) * 2002-03-28 2003-10-02 Clark Lubbers System and method for automatic site failover in a storage area network
US20040153708A1 (en) * 2002-05-31 2004-08-05 Joshi Darshan B. Business continuation policy for server consolidation environment
US20040034808A1 (en) * 2002-08-16 2004-02-19 International Business Machines Corporation Method, system, and program for providing a mirror copy of data
US20040039888A1 (en) * 2002-08-21 2004-02-26 Lecrone Douglas E. Storage automated replication processing
US20040243650A1 (en) * 2003-06-02 2004-12-02 Surgient, Inc. Shared nothing virtual cluster
US20050015657A1 (en) * 2003-06-27 2005-01-20 Hitachi, Ltd. Data center system and method for controlling the same
US20050198452A1 (en) * 2004-03-02 2005-09-08 Naoki Watanabe Method and apparatus of remote copy for multiple storage subsystems
US20060047896A1 (en) * 2004-08-25 2006-03-02 Lu Nguyen Storing parity information for data recovery
US7370228B2 (en) * 2004-09-01 2008-05-06 Hitachi, Ltd. Data processing system and copy processing method thereof

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090327805A1 (en) * 2008-06-26 2009-12-31 Microsoft Corporation Minimizing data loss in asynchronous replication solution using distributed redundancy
US7908514B2 (en) * 2008-06-26 2011-03-15 Microsoft Corporation Minimizing data loss in asynchronous replication solution using distributed redundancy
CN102591741A (en) * 2010-11-29 2012-07-18 国际商业机器公司 Method and system for realizing disaster recovery utilizing collapsible virtualized capacity
US8762339B2 (en) 2010-11-29 2014-06-24 International Business Machines Corporation Disaster recovery utilizing collapsible virtualized capacity
US8549348B2 (en) 2011-05-02 2013-10-01 International Business Machines Corporation Coordinated disaster recovery production takeover operations
US8959391B2 (en) 2011-05-02 2015-02-17 International Business Machines Corporation Optimizing disaster recovery systems during takeover operations
US9983964B2 (en) 2011-05-02 2018-05-29 International Business Machines Corporation Optimizing disaster recovery systems during takeover operations
US9361189B2 (en) 2011-05-02 2016-06-07 International Business Machines Corporation Optimizing disaster recovery systems during takeover operations
US8522068B2 (en) 2011-05-02 2013-08-27 International Business Machines Corporation Coordinated disaster recovery production takeover operations
US8671308B2 (en) 2011-05-02 2014-03-11 International Business Machines Corporation Optimizing disaster recovery systems during takeover operations
US8892830B2 (en) 2011-05-11 2014-11-18 International Business Machines Corporation Changing ownership of cartridges
US8850139B2 (en) 2011-05-11 2014-09-30 International Business Machines Corporation Changing ownership of cartridges
US9104607B2 (en) 2012-10-31 2015-08-11 International Business Machines Corporation Simulation engine for use in disaster recovery virtualization
US9471447B2 (en) 2012-10-31 2016-10-18 International Business Machines Corporation Virtualization simulation engine including assuming a dormant state for a lower priority application
US9317381B2 (en) 2012-11-20 2016-04-19 Hitachi, Ltd. Storage system and data management method
WO2014080438A1 (en) * 2012-11-20 2014-05-30 Hitachi, Ltd. Storage system and data management method
US9104625B2 (en) 2012-12-11 2015-08-11 International Business Machines Corporation Disaster recovery internet protocol address failover
US9508470B2 (en) 2013-10-29 2016-11-29 General Electric Company Vibration damage repair in dynamoelectric machines
CN103744753A (en) * 2013-12-26 2014-04-23 北京交控科技有限公司 Data interaction method and device for dual systems
US9836367B2 (en) * 2015-08-28 2017-12-05 Netapp, Inc. Trust relationship migration for data mirroring
US20170060710A1 (en) * 2015-08-28 2017-03-02 Netapp Inc. Trust relationship migration for data mirroring
US20180150367A1 (en) * 2015-08-28 2018-05-31 Netapp Inc. Trust relationship migration for data mirroring
US10621056B2 (en) 2015-08-28 2020-04-14 Netapp Inc. Trust relationship migration for data mirroring
US11334454B2 (en) 2015-08-28 2022-05-17 Netapp Inc. Trust relationship migration for data mirroring

Also Published As

Publication number Publication date
CA2621238A1 (en) 2007-04-12
WO2007041286A2 (en) 2007-04-12
WO2007041286A3 (en) 2009-04-30
CA2621238C (en) 2014-01-14
GB2445700B (en) 2011-04-06
US20070079171A1 (en) 2007-04-05
GB2445700A (en) 2008-07-16
AU2006297142A1 (en) 2007-04-12
GB0807791D0 (en) 2008-06-04
AU2006297142B2 (en) 2011-09-15
US7577868B2 (en) 2009-08-18
DE112006002483T5 (en) 2008-08-07

Similar Documents

Publication Publication Date Title
US7577868B2 (en) No data loss IT disaster recovery over extended distances
US7340490B2 (en) Storage network data replicator
US10936447B2 (en) Resynchronizing to a first storage system after a failover to a second storage system mirroring the first storage system
US6360306B1 (en) Relocation of suspended data to a remote site in a distributed storage system
US7752403B1 (en) Methods and systems for secure dispersed redundant data storage
CN103765406B (en) For the method and apparatus remotely updating executive process
US7933987B2 (en) Application of virtual servers to high availability and disaster recovery solutions
CN1902595B (en) Coordinated storage management operations in replication environment
US20080077686A1 (en) System and Method for Replication of Network State for Transparent Recovery of Network Connections
CN100390744C (en) Method and system for error strategy in a storage system
US20070174660A1 (en) System and method for enabling site failover in an application server environment
US11709743B2 (en) Methods and systems for a non-disruptive automatic unplanned failover from a primary copy of data at a primary storage system to a mirror copy of the data at a cross-site secondary storage system
US20120109919A1 (en) High availability database management system and database management method using same
JP2007511008A (en) Hybrid real-time data replication
US8903766B2 (en) Data mirroring using a virtual connection
JP4713843B2 (en) Backup method
KR20080050276A (en) Distributed object-sharing system and method thereof
WO2013127147A1 (en) File synchronization system and method
US7698519B2 (en) Backup of hierarchically structured storage pools
JP2018010495A (en) Information processing device, information processing program and information processing system
CN106027313B (en) Network link disaster tolerance system and method
CN107291575B (en) Processing method and equipment for data center fault
US20030204539A1 (en) Facility protection utilizing fault tolerant storage controllers
CN106878063A (en) A kind of method for recovering network topological sum business configuration data from network element
US9436653B2 (en) Shared-bandwidth multiple target remote copy

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION