US20070250626A1 - System and method for uniform disaster recovery system access - Google Patents
System and method for uniform disaster recovery system access Download PDFInfo
- Publication number
- US20070250626A1 US20070250626A1 US11/408,485 US40848506A US2007250626A1 US 20070250626 A1 US20070250626 A1 US 20070250626A1 US 40848506 A US40848506 A US 40848506A US 2007250626 A1 US2007250626 A1 US 2007250626A1
- Authority
- US
- United States
- Prior art keywords
- data processing
- processing system
- server data
- network address
- uniform resource
- 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
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/202—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 processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2025—Failover techniques using centralised failover control functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
Definitions
- the present invention is directed, in general, to networked data processing systems, and in particular to networked data processing system disaster recovery activities.
- Businesses rely on data processing systems to manage a wide range of internal and external functions, including accounting and inventory functions, data management functions, and many others. Further, many of these systems must be available to be accessed over local or wide-area data processing system networks, including both private networks and public networks such as the internet.
- a primary system may be “down” or otherwise unavailable, which can be costly and damaging.
- many businesses and other enterprises maintain “disaster recovery” systems or environments, which can include redundant systems that provide some or all of the functions of the primary systems, and typically include full backups of all the data available to the primary systems. In this way, in the event of a disaster, users can transition to the disaster recovery environment until the primary system can be restored, thus minimizing lost productivity.
- Various embodiments include a method and corresponding systems and computer program products, for directing access to a server data processing system.
- the method includes storing a first uniform resource locator associated with a first network address, where the first network address corresponds to a primary server data processing system and storing a second uniform resource locator associated with a second network address, where the second network address corresponds to a disaster recovery server data processing system.
- the method also includes returning the first network address in response to calls for the first uniform resource locator when the primary server data processing system is operating normally and returning the second network address in response to calls for the first uniform resource locator when the primary server data processing system is unavailable (i.e. In the event of a “disaster”).
- an alternative method includes returning the second network address in response to calls for the second uniform resource locator while the primary server data processing system is operating normally.
- FIG. 1 depicts a block diagram of a data processing system in which a preferred embodiment can be implemented
- FIG. 2 depicts a data processing system network in which an embodiment of the present disclosure can be implemented.
- FIG. 3 depicts a flowchart of a process in accordance with a preferred embodiment.
- FIGS. 1 through 3 discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand that the principles of the present invention may be implemented in any suitably arranged device. The numerous innovative teachings of the present application will be described with particular reference to the presently preferred embodiment.
- FIG. 1 depicts a block diagram of a data processing system in which a preferred embodiment can be implemented.
- the data processing system depicted includes a processor 102 connected to a level two cache/bridge 104 , which is connected in turn to a local system bus 106 .
- Local system bus 106 may be, for example, a peripheral component interconnect (PCI) architecture bus.
- PCI peripheral component interconnect
- Also connected to local system bus in the depicted example are a main memory 108 and a graphics adapter 110 .
- LAN local area network
- WiFi Wireless Fidelity
- Expansion bus interface 114 connects local system bus 106 to input/output (I/O) bus 116 .
- I/O bus 116 is connected to keyboard/mouse adapter 118 , disk controller 120 , and I/O adapter 122 .
- audio adapter 124 Also connected to I/O bus 116 in the example shown is audio adapter 124 , to which speakers (not shown) may be connected for playing sounds.
- Keyboard/mouse adapter 118 provides a connection for a pointing device (not shown), such as a mouse, trackball, trackpointer, etc.
- FIG. 1 may vary for particular.
- other peripheral devices such as an optical disk drive and the like, also may be used in addition or in place of the hardware depicted.
- the depicted example is provided for the purpose of explanation only and is not meant to imply architectural limitations with respect to the present invention.
- a data processing system in accordance with a preferred embodiment of the present invention includes an operating system employing a graphical user interface.
- the operating system permits multiple display windows to be presented in the graphical user interface simultaneously, with each display window providing an interface to a different application or to a different instance of the same application.
- a cursor in the graphical user interface may be manipulated by a user through the pointing device. The position of the cursor may be changed and/or an event, such as clicking a mouse button, generated to actuate a desired response.
- One of various commercial operating systems such as a version of Microsoft WindowsTM, a product of Microsoft Corporation located in Redmond, Wash. may be employed if suitably modified.
- the operating system is modified or created in accordance with the present invention as described.
- FIG. 2 depicts a data processing system network in which an embodiment of the present disclosure can be implemented.
- FIG. 2 depicts client data processing system 210 , domain name server (DNS) 220 , server data processing system 230 , and disaster-recovery (DR) server data processing system 240 , all connected to communicate with network 250 .
- Network 250 can be implemented using any known public or private data processing system network, or can be more than one network configured to communicate with each other, and can include the Internet.
- Each of the data processing systems 210 , 220 , 230 , and 240 can be implemented, for example, as in data processing system 100 , or can be modified as required for each particular implementation, as known to those of skill in the art, so long as they each can perform the respective functions as described herein.
- client data processing system 210 is a data processing system connected to communicate with network 250 , and thereby to communicate with various other network-connected systems.
- Data processing system 210 preferably includes a browser such as MICROSOFT INTERNET EXPLORER.
- DNS 220 in this example, is a domain name server system. Although only one block is used here to represent DNS 220 , those of skill in the art will recognize that domain name resolution processes will often involve multiple different servers, such as a local DNS server, a root server, a top level domain name server, etc., all of which act together to resolve domain names and uniform resource locators (URLs) into the corresponding internet protocol (IP) addresses.
- IP internet protocol
- the conventional processes for such a resolution are well known to those of skill in the art, and so to simplify the illustration of FIG. 2 , only a single block for DNS 220 is shown.
- Server data processing system 230 can represent any server system or a combination of multiple systems that deliver data or other services over the network 250 .
- DR server data processing system 240 is preferably a fully redundant backup system or systems to server data processing system 230 that is capable of delivering or performing some or all of the same services as server data processing system 230 in the event that server data processing system is unavailable over network 250 .
- DNS 220 includes one or more DNS entries in a storage 225 indicating the URL addresses and corresponding IP addresses for server data processing system 230 , which will be referred to herein as production URLS. Further, DNS 220 includes one or more secondary URLs, referred to herein as disaster recovery URLS or DR URLs, corresponding to the production URLS, that indicate instead the IP address(es) of DR server data processing system 240 .
- DNS 220 is preferably configured to return the IP address of the server data processing system 230 in response to calls for the production URL when the server data processing system is operating normally, to return the IP address of the server data processing system 240 in response to calls for the production URL when the server data processing system 230 is unavailable.
- the DR URL in the DNS 220 points to the IP addresses of the DR server data processing system 240 whether or not the server data processing system 230 is operating normally.
- a DR URL there will be two URLs defined in the DNS for each server system instead of one, i.e., a DR URL and a production URL, to point to a DR IP address and production IP address respectively.
- the DR URL can be used (as described above).
- the DNS entry in DNS 220 for production URL should be updated to point to the IP address of the DR data processing server 240 for seamless replacement.
- the DNS 220 can store the IP address of the DR data processing server 240 associated with the production URL when the server data processing system 230 is unavailable.
- the DR URL has a standard naming convention where the term “DR” is placed in front of the production URL to form the DR URL.
- the DR URL is preferably defined as http://dr.example.com, using “dr” as the subdomain.
- a standard internet web URL such as http://dr.example.com, the hierarchical order of the five elements is com (generic top-level domain)—example (second-level domain)—dr (subdomain).
- the corresponding DR URL will include the dr subdomain as http://dr.example.com.
- the DR URL can be any suitable URL and achieve the same result, including a DR URL formed by modifying or changing the production URL by adding another word or character in front of the production URL. So long as the DR URL points to the DR server data processing system, it will still achieve the same result.
- the use of a consistent naming convention for DR URLs as described above will encourage a smooth transition to the DR servers in the event that becomes necessary.
- the DNS server can associate the production URL with both the network address of the production server and the network address of the DR server, and automatically redirect calls to the DR server when the production server is unavailable or when the DR URL or URL subdomain is used.
- FIG. 3 depicts a flowchart of a process in accordance with a preferred embodiment.
- a first URL is assigned to a server data processing system (step 305 ).
- the first URL is stored together with a first network address corresponding to the server data processing system (step 310 ).
- the URL and the first network address are stored in a DNS server, and the first network address is an IP address.
- the server data processing system is a production data processing system as described above.
- a second URL is assigned to a DR server data processing system (step 315 ), which preferably is a backup system for some of all of the functions of the server data processing system.
- the second URL is stored together with a second network address corresponding to the DR server data processing system (step 320 ).
- the DR URL and second network address are stored in a DNS server, and the second network address is an IP address.
- the second URL is substantially similar to the first URL, with a “dr” subdomain indicator indicating it is the URL address for the disaster recovery system.
- step 325 If the server data processing system is operating normally (step 325 ), then calls to the first URL are directed to the first network address (step 330 ). If the production server data processing system is unavailable, e.g., in the event of a “disaster,” then calls to the first URL are directed to the second network address (step 335 ).
- One way in which this can be implemented is by updating the DNS record associated with the first URL to indicate the second network address.
- machine usable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs), and transmission type mediums such as digital and analog communication links.
- ROMs read only memories
- EEPROMs electrically programmable read only memories
- user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs
- transmission type mediums such as digital and analog communication links.
Abstract
Description
- The present invention is directed, in general, to networked data processing systems, and in particular to networked data processing system disaster recovery activities.
- Businesses rely on data processing systems to manage a wide range of internal and external functions, including accounting and inventory functions, data management functions, and many others. Further, many of these systems must be available to be accessed over local or wide-area data processing system networks, including both private networks and public networks such as the internet.
- In the event of a “disaster,” which can include both actual natural disasters and other events, a primary system may be “down” or otherwise unavailable, which can be costly and damaging. In response, many businesses and other enterprises maintain “disaster recovery” systems or environments, which can include redundant systems that provide some or all of the functions of the primary systems, and typically include full backups of all the data available to the primary systems. In this way, in the event of a disaster, users can transition to the disaster recovery environment until the primary system can be restored, thus minimizing lost productivity.
- Unfortunately, there is currently no uniform and reliable way for a user to effectively contact the disaster recovery environment in the event of a disaster, and no standard and effective way for the disaster recovery system to be tested on a routine basis without disrupting operation of the primary system. There is, therefore, a need in the art for a system and method for uniform disaster recovery system access.
- Various embodiments include a method and corresponding systems and computer program products, for directing access to a server data processing system. The method includes storing a first uniform resource locator associated with a first network address, where the first network address corresponds to a primary server data processing system and storing a second uniform resource locator associated with a second network address, where the second network address corresponds to a disaster recovery server data processing system. The method also includes returning the first network address in response to calls for the first uniform resource locator when the primary server data processing system is operating normally and returning the second network address in response to calls for the first uniform resource locator when the primary server data processing system is unavailable (i.e. In the event of a “disaster”). For purpose of testing, an alternative method includes returning the second network address in response to calls for the second uniform resource locator while the primary server data processing system is operating normally.
- The foregoing has outlined rather broadly the features and technical advantages of the present invention so that those skilled in the art may better understand the detailed description of the invention that follows. Additional features and advantages of the invention will be described hereinafter that form the subject of the claims of the invention. Those skilled in the art will appreciate that they may readily use the conception and the specific embodiment disclosed as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. Those skilled in the art will also realize that such equivalent constructions do not depart from the spirit and scope of the invention in its broadest form.
- Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, it may be advantageous to set forth definitions of certain words or phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term “controller” means any device, system or part thereof that controls at least one operation, whether such a device is implemented in hardware, firmware, software or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, and those of ordinary skill in the art will understand that such definitions apply in many, if not most, instances to prior as well as future uses of such defined words and phrases.
- For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, wherein like numbers designate like objects, and in which:
-
FIG. 1 depicts a block diagram of a data processing system in which a preferred embodiment can be implemented; -
FIG. 2 depicts a data processing system network in which an embodiment of the present disclosure can be implemented; and -
FIG. 3 depicts a flowchart of a process in accordance with a preferred embodiment. -
FIGS. 1 through 3 , discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand that the principles of the present invention may be implemented in any suitably arranged device. The numerous innovative teachings of the present application will be described with particular reference to the presently preferred embodiment. -
FIG. 1 depicts a block diagram of a data processing system in which a preferred embodiment can be implemented. The data processing system depicted includes aprocessor 102 connected to a level two cache/bridge 104, which is connected in turn to alocal system bus 106.Local system bus 106 may be, for example, a peripheral component interconnect (PCI) architecture bus. Also connected to local system bus in the depicted example are amain memory 108 and agraphics adapter 110. - Other peripherals, such as local area network (LAN)/Wide Area Network/Wireless (e.g. WiFi)
adapter 112, may also be connected tolocal system bus 106.Expansion bus interface 114 connectslocal system bus 106 to input/output (I/O)bus 116. I/O bus 116 is connected to keyboard/mouse adapter 118,disk controller 120, and I/O adapter 122. - Also connected to I/
O bus 116 in the example shown isaudio adapter 124, to which speakers (not shown) may be connected for playing sounds. Keyboard/mouse adapter 118 provides a connection for a pointing device (not shown), such as a mouse, trackball, trackpointer, etc. - Those of ordinary skill in the art will appreciate that the hardware depicted in
FIG. 1 may vary for particular. For example, other peripheral devices, such as an optical disk drive and the like, also may be used in addition or in place of the hardware depicted. The depicted example is provided for the purpose of explanation only and is not meant to imply architectural limitations with respect to the present invention. - A data processing system in accordance with a preferred embodiment of the present invention includes an operating system employing a graphical user interface. The operating system permits multiple display windows to be presented in the graphical user interface simultaneously, with each display window providing an interface to a different application or to a different instance of the same application. A cursor in the graphical user interface may be manipulated by a user through the pointing device. The position of the cursor may be changed and/or an event, such as clicking a mouse button, generated to actuate a desired response.
- One of various commercial operating systems, such as a version of Microsoft Windows™, a product of Microsoft Corporation located in Redmond, Wash. may be employed if suitably modified. The operating system is modified or created in accordance with the present invention as described.
-
FIG. 2 depicts a data processing system network in which an embodiment of the present disclosure can be implemented.FIG. 2 depicts clientdata processing system 210, domain name server (DNS) 220, serverdata processing system 230, and disaster-recovery (DR) serverdata processing system 240, all connected to communicate withnetwork 250. Network 250 can be implemented using any known public or private data processing system network, or can be more than one network configured to communicate with each other, and can include the Internet. Each of thedata processing systems - In this exemplary embodiment, client
data processing system 210 is a data processing system connected to communicate withnetwork 250, and thereby to communicate with various other network-connected systems.Data processing system 210 preferably includes a browser such as MICROSOFT INTERNET EXPLORER. - DNS 220, in this example, is a domain name server system. Although only one block is used here to represent DNS 220, those of skill in the art will recognize that domain name resolution processes will often involve multiple different servers, such as a local DNS server, a root server, a top level domain name server, etc., all of which act together to resolve domain names and uniform resource locators (URLs) into the corresponding internet protocol (IP) addresses. The conventional processes for such a resolution are well known to those of skill in the art, and so to simplify the illustration of
FIG. 2 , only a single block forDNS 220 is shown. - Server
data processing system 230 can represent any server system or a combination of multiple systems that deliver data or other services over thenetwork 250. DR serverdata processing system 240, as used in this example, is preferably a fully redundant backup system or systems to serverdata processing system 230 that is capable of delivering or performing some or all of the same services as serverdata processing system 230 in the event that server data processing system is unavailable overnetwork 250. - According to various disclosed embodiments, DNS 220 includes one or more DNS entries in a
storage 225 indicating the URL addresses and corresponding IP addresses for serverdata processing system 230, which will be referred to herein as production URLS. Further, DNS 220 includes one or more secondary URLs, referred to herein as disaster recovery URLS or DR URLs, corresponding to the production URLS, that indicate instead the IP address(es) of DR serverdata processing system 240. - By defining corresponding production URLs and DR URLs in the
DNS 220 to point to the IP addresses of the serverdata processing system 230 and DR serverdata processing system 240, respectively, users can be assured of a means for readily contacting the DR serverdata processing system 240 for either testing purposes or in the event that serverdata processing system 230 is unavailable. DNS 220 is preferably configured to return the IP address of the serverdata processing system 230 in response to calls for the production URL when the server data processing system is operating normally, to return the IP address of the serverdata processing system 240 in response to calls for the production URL when the serverdata processing system 230 is unavailable. For purpose of testing, preferably, the DR URL in theDNS 220 points to the IP addresses of the DR serverdata processing system 240 whether or not the serverdata processing system 230 is operating normally. - Preferably, there will be two URLs defined in the DNS for each server system instead of one, i.e., a DR URL and a production URL, to point to a DR IP address and production IP address respectively.
- For purposes of testing the DR server
data processing system 240, the DR URL can be used (as described above). In the event of a “disaster”, including unavailability of serverdata processing system 230, the DNS entry inDNS 220 for production URL should be updated to point to the IP address of the DRdata processing server 240 for seamless replacement. TheDNS 220 can store the IP address of the DRdata processing server 240 associated with the production URL when the serverdata processing system 230 is unavailable. - In various embodiments, the DR URL has a standard naming convention where the term “DR” is placed in front of the production URL to form the DR URL. For example, if a production URL has been defined as http://example.com then the DR URL is preferably defined as http://dr.example.com, using “dr” as the subdomain. Note that a standard internet web URL such as http://dr.example.com, the hierarchical order of the five elements is com (generic top-level domain)—example (second-level domain)—dr (subdomain). In preferred embodiments, for a server located at URL http://example.com, the corresponding DR URL will include the dr subdomain as http://dr.example.com.
- Of course, the DR URL can be any suitable URL and achieve the same result, including a DR URL formed by modifying or changing the production URL by adding another word or character in front of the production URL. So long as the DR URL points to the DR server data processing system, it will still achieve the same result. However, the use of a consistent naming convention for DR URLs as described above will encourage a smooth transition to the DR servers in the event that becomes necessary. In some embodiments, particularly when a uniform naming convention is used for the DR server, the DNS server can associate the production URL with both the network address of the production server and the network address of the DR server, and automatically redirect calls to the DR server when the production server is unavailable or when the DR URL or URL subdomain is used.
-
FIG. 3 depicts a flowchart of a process in accordance with a preferred embodiment. - A first URL, preferably the production URL, is assigned to a server data processing system (step 305). The first URL is stored together with a first network address corresponding to the server data processing system (step 310). In a preferred embodiment, the URL and the first network address are stored in a DNS server, and the first network address is an IP address. Preferably the server data processing system is a production data processing system as described above.
- A second URL, preferably the DR URL, is assigned to a DR server data processing system (step 315), which preferably is a backup system for some of all of the functions of the server data processing system. The second URL is stored together with a second network address corresponding to the DR server data processing system (step 320). In a preferred embodiment, the DR URL and second network address are stored in a DNS server, and the second network address is an IP address.
- Preferably, as described above, the second URL is substantially similar to the first URL, with a “dr” subdomain indicator indicating it is the URL address for the disaster recovery system.
- If the server data processing system is operating normally (step 325), then calls to the first URL are directed to the first network address (step 330). If the production server data processing system is unavailable, e.g., in the event of a “disaster,” then calls to the first URL are directed to the second network address (step 335). One way in which this can be implemented is by updating the DNS record associated with the first URL to indicate the second network address.
- Those skilled in the art will recognize that, for simplicity and clarity, the full structure and operation of all data processing systems suitable for use with the present invention is not being depicted or described herein. Instead, only so much of a data processing system as is unique to the present invention or necessary for an understanding of the present invention is depicted and described. The remainder of the construction and operation of data processing system 100 may conform to any of the various current implementations and practices known in the art.
- It is important to note that while the present invention has been described in the context of a fully functional system, those skilled in the art will appreciate that at least portions of the mechanism of the present invention are capable of being distributed in the form of a instructions contained within a machine usable medium in any of a variety of forms, and that the present invention applies equally regardless of the particular type of instruction or signal bearing medium utilized to actually carry out the distribution. Examples of machine usable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs), and transmission type mediums such as digital and analog communication links.
- Although an exemplary embodiment of the present invention has been described in detail, those skilled in the art will understand that various changes, substitutions, variations, and improvements of the invention disclosed herein may be made without departing from the spirit and scope of the invention in its broadest form.
- None of the description in the present application should be read as implying that any particular element, step, or function is an essential element which must be included in the claim scope: THE SCOPE OF PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE ALLOWED CLAIMS. Moreover, none of these claims are intended to invoke paragraph six of 35 USC §112 unless the exact words “means for” are followed by a participle.
Claims (21)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/408,485 US20070250626A1 (en) | 2006-04-21 | 2006-04-21 | System and method for uniform disaster recovery system access |
US11/618,617 US7770058B2 (en) | 2006-04-21 | 2006-12-29 | Disaster recovery within secure environments |
PCT/US2007/066110 WO2007124255A1 (en) | 2006-04-21 | 2007-04-05 | System and method for uniform disaster recovery system access |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/408,485 US20070250626A1 (en) | 2006-04-21 | 2006-04-21 | System and method for uniform disaster recovery system access |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/618,617 Continuation-In-Part US7770058B2 (en) | 2006-04-21 | 2006-12-29 | Disaster recovery within secure environments |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070250626A1 true US20070250626A1 (en) | 2007-10-25 |
Family
ID=38442591
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/408,485 Abandoned US20070250626A1 (en) | 2006-04-21 | 2006-04-21 | System and method for uniform disaster recovery system access |
US11/618,617 Active 2028-01-22 US7770058B2 (en) | 2006-04-21 | 2006-12-29 | Disaster recovery within secure environments |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/618,617 Active 2028-01-22 US7770058B2 (en) | 2006-04-21 | 2006-12-29 | Disaster recovery within secure environments |
Country Status (2)
Country | Link |
---|---|
US (2) | US20070250626A1 (en) |
WO (1) | WO2007124255A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090113233A1 (en) * | 2007-10-31 | 2009-04-30 | Electronic Data Systems Corporation | Testing Disaster Recovery Elements |
US20100250757A1 (en) * | 2009-03-30 | 2010-09-30 | Akhter Aamer S | Redirection of a request for information |
US20110047207A1 (en) * | 2009-08-24 | 2011-02-24 | General Electric Company | System and method for near-optimal media sharing |
US11082353B2 (en) * | 2015-09-28 | 2021-08-03 | Arris Enterprises Llc | Domain name system response spoofing at customer premise equipment device |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519857B2 (en) * | 2006-06-16 | 2009-04-14 | Hewlett-Packard Development Company, L.P. | Method, apparatus, and system for a software based business continuity solution for a computing environment |
US7765433B1 (en) * | 2007-03-14 | 2010-07-27 | Symantec Corporation | Technique for performing disaster rehearsal for a storage area network utilizing a replication appliance |
US20090210427A1 (en) * | 2008-02-15 | 2009-08-20 | Chris Eidler | Secure Business Continuity and Disaster Recovery Platform for Multiple Protected Systems |
US8037361B2 (en) * | 2009-11-04 | 2011-10-11 | International Business Machines Corporation | Selective write protect for disaster recovery testing |
US8112657B2 (en) * | 2010-06-14 | 2012-02-07 | At&T Intellectual Property I, L.P. | Method, computer, and computer program product for hardware mapping |
US8694822B2 (en) | 2010-11-09 | 2014-04-08 | International Business Machines Corporation | Disaster recovery in a networked computing environment |
US9176829B2 (en) * | 2011-07-01 | 2015-11-03 | Microsoft Technology Licensing, Llc | Managing recovery virtual machines in clustered environment |
US8954786B2 (en) * | 2011-07-28 | 2015-02-10 | Oracle International Corporation | Failover data replication to a preferred list of instances |
US9344494B2 (en) | 2011-08-30 | 2016-05-17 | Oracle International Corporation | Failover data replication with colocation of session state data |
US9424152B1 (en) * | 2012-10-17 | 2016-08-23 | Veritas Technologies Llc | Techniques for managing a disaster recovery failover policy |
US9092395B2 (en) | 2012-12-20 | 2015-07-28 | International Business Machines Corporation | Provide an appliance like test vehicle for IT disaster recovery |
US9208006B2 (en) * | 2013-03-11 | 2015-12-08 | Sungard Availability Services, Lp | Recovery Maturity Model (RMM) for readiness-based control of disaster recovery testing |
JP2016162324A (en) * | 2015-03-04 | 2016-09-05 | 富士通株式会社 | Information processing system, control program and control method |
US9973570B2 (en) | 2015-05-01 | 2018-05-15 | Hartford Fire Insurance Company | System for providing an isolated testing model for disaster recovery capabilites |
US9477555B1 (en) * | 2015-11-16 | 2016-10-25 | International Business Machines Corporation | Optimized disaster-recovery-as-a-service system |
US10255138B2 (en) | 2016-08-17 | 2019-04-09 | Bank Of America Corporation | Disaster recovery tool |
US10198330B2 (en) * | 2016-11-30 | 2019-02-05 | Sap Se | Configuring disaster recovery for a cloud based application |
US10671495B2 (en) | 2018-01-29 | 2020-06-02 | Hewlett Packard Enterprise Development Lp | Disaster recovery rehearsal of a workload |
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 |
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 |
US11341032B1 (en) | 2020-12-11 | 2022-05-24 | International Business Machines Corporation | Testing in a disaster recovery computer system |
US11687442B2 (en) * | 2021-08-06 | 2023-06-27 | International Business Machines Corporation | Dynamic resource provisioning for use cases |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5473599A (en) * | 1994-04-22 | 1995-12-05 | Cisco Systems, Incorporated | Standby router protocol |
US5917997A (en) * | 1996-12-06 | 1999-06-29 | International Business Machines Corporation | Host identity takeover using virtual internet protocol (IP) addressing |
US6108300A (en) * | 1997-05-02 | 2000-08-22 | Cisco Technology, Inc | Method and apparatus for transparently providing a failover network device |
US6301617B1 (en) * | 1997-08-25 | 2001-10-09 | Intel Corporation | Selection of resources utilizing virtual uniform resource locators |
US6366558B1 (en) * | 1997-05-02 | 2002-04-02 | Cisco Technology, Inc. | Method and apparatus for maintaining connection state between a connection manager and a failover device |
US6442709B1 (en) * | 1999-02-09 | 2002-08-27 | International Business Machines Corporation | System and method for simulating disaster situations on peer to peer remote copy machines |
US20030037133A1 (en) * | 2001-08-15 | 2003-02-20 | Thomas Owens | Method and system for implementing redundant servers |
US6813635B1 (en) * | 2000-10-13 | 2004-11-02 | Hewlett-Packard Development Company, L.P. | System and method for distributing load among redundant independent stateful world wide web server sites |
US20050021771A1 (en) * | 2003-03-03 | 2005-01-27 | Keith Kaehn | System enabling server progressive workload reduction to support server maintenance |
US20060075279A1 (en) * | 2004-08-17 | 2006-04-06 | Shaw Parsing, Llc | Techniques for upstream failure detection and failure recovery |
US7039008B1 (en) * | 1997-05-02 | 2006-05-02 | Cisco Technology, Inc. | Method and apparatus for maintaining connection state between a connection manager and a failover device |
US7099915B1 (en) * | 2000-06-30 | 2006-08-29 | Cisco Technology, Inc. | Server load balancing method and system |
Family Cites Families (24)
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 |
US6092066A (en) * | 1996-05-31 | 2000-07-18 | Emc Corporation | Method and apparatus for independent operation of a remote data facility |
US6389552B1 (en) * | 1998-12-31 | 2002-05-14 | At&T Corp | Methods and systems for remote electronic vaulting |
US7020697B1 (en) * | 1999-10-01 | 2006-03-28 | Accenture Llp | Architectures for netcentric computing systems |
US20060020530A1 (en) * | 2000-02-14 | 2006-01-26 | Hsu Phillip K | Systems for providing financial services |
US7194616B2 (en) * | 2001-10-27 | 2007-03-20 | International Business Machines Corporation | Flexible temporary capacity upgrade/downgrade in a computer system without involvement of the operating system |
US7139885B2 (en) * | 2001-12-27 | 2006-11-21 | Hitachi, Ltd. | Method and apparatus for managing storage based replication |
US6732294B2 (en) * | 2001-12-27 | 2004-05-04 | Storage Technology Corporation | Method of disaster recovery testing and storage system |
GB0227786D0 (en) * | 2002-11-29 | 2003-01-08 | Ibm | Improved remote copy synchronization in disaster recovery computer systems |
US7260841B2 (en) * | 2003-02-27 | 2007-08-21 | Nortel Networks Limited | System and method for maintaining access to content in an encrypted network environment |
US20040193476A1 (en) * | 2003-03-31 | 2004-09-30 | Aerdts Reinier J. | Data center analysis |
US7467168B2 (en) * | 2003-06-18 | 2008-12-16 | International Business Machines Corporation | Method for mirroring data at storage locations |
US7383463B2 (en) * | 2004-02-04 | 2008-06-03 | Emc Corporation | Internet protocol based disaster recovery of a server |
US7139782B2 (en) * | 2004-09-21 | 2006-11-21 | Hitachi, Ltd. | Method of and system for testing remote storage |
US7475204B2 (en) * | 2004-11-24 | 2009-01-06 | International Business Machines Corporation | Automatically managing the state of replicated data of a computing environment |
US7631213B2 (en) * | 2004-12-06 | 2009-12-08 | Johnson R Brent | Data center virtual tape off-site disaster recovery planning and implementation system |
US20060195340A1 (en) * | 2004-12-15 | 2006-08-31 | Critical Connection Inc. | System and method for restoring health data in a database |
US7644089B2 (en) * | 2004-12-29 | 2010-01-05 | Barclays Capital, Inc. | System and method for corporate-wide policy management |
JP2008533573A (en) * | 2005-03-10 | 2008-08-21 | テレコム・イタリア・エッセ・ピー・アー | Disaster recovery architecture |
US7302540B1 (en) * | 2005-07-26 | 2007-11-27 | Storage Technology Corporation | Virtual tape storage system having snapshot virtual tape library for disaster recovery testing |
US7571292B2 (en) * | 2006-03-21 | 2009-08-04 | International Business Machines Corporation | Producing tertiary instant virtual copies without volume suspension |
US20080263079A1 (en) * | 2006-10-24 | 2008-10-23 | Flextronics Ap, Llc | Data recovery in an enterprise data storage system |
US20080109804A1 (en) * | 2006-11-06 | 2008-05-08 | Richard Welcher Bloomstein | Additional uses of virtualization for disaster recovery and prevention |
US8073880B2 (en) * | 2006-11-10 | 2011-12-06 | Computer Associates Think, Inc. | System and method for optimizing storage infrastructure performance |
-
2006
- 2006-04-21 US US11/408,485 patent/US20070250626A1/en not_active Abandoned
- 2006-12-29 US US11/618,617 patent/US7770058B2/en active Active
-
2007
- 2007-04-05 WO PCT/US2007/066110 patent/WO2007124255A1/en active Application Filing
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5473599A (en) * | 1994-04-22 | 1995-12-05 | Cisco Systems, Incorporated | Standby router protocol |
US5917997A (en) * | 1996-12-06 | 1999-06-29 | International Business Machines Corporation | Host identity takeover using virtual internet protocol (IP) addressing |
US6108300A (en) * | 1997-05-02 | 2000-08-22 | Cisco Technology, Inc | Method and apparatus for transparently providing a failover network device |
US6366558B1 (en) * | 1997-05-02 | 2002-04-02 | Cisco Technology, Inc. | Method and apparatus for maintaining connection state between a connection manager and a failover device |
US7039008B1 (en) * | 1997-05-02 | 2006-05-02 | Cisco Technology, Inc. | Method and apparatus for maintaining connection state between a connection manager and a failover device |
US6301617B1 (en) * | 1997-08-25 | 2001-10-09 | Intel Corporation | Selection of resources utilizing virtual uniform resource locators |
US6442709B1 (en) * | 1999-02-09 | 2002-08-27 | International Business Machines Corporation | System and method for simulating disaster situations on peer to peer remote copy machines |
US7099915B1 (en) * | 2000-06-30 | 2006-08-29 | Cisco Technology, Inc. | Server load balancing method and system |
US6813635B1 (en) * | 2000-10-13 | 2004-11-02 | Hewlett-Packard Development Company, L.P. | System and method for distributing load among redundant independent stateful world wide web server sites |
US20030037133A1 (en) * | 2001-08-15 | 2003-02-20 | Thomas Owens | Method and system for implementing redundant servers |
US20050021771A1 (en) * | 2003-03-03 | 2005-01-27 | Keith Kaehn | System enabling server progressive workload reduction to support server maintenance |
US20060075279A1 (en) * | 2004-08-17 | 2006-04-06 | Shaw Parsing, Llc | Techniques for upstream failure detection and failure recovery |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090113233A1 (en) * | 2007-10-31 | 2009-04-30 | Electronic Data Systems Corporation | Testing Disaster Recovery Elements |
WO2009058427A1 (en) | 2007-10-31 | 2009-05-07 | Hewlett-Packard Development Company L.P. | Testing disaster recovery elements |
US8984326B2 (en) | 2007-10-31 | 2015-03-17 | Hewlett-Packard Development Company, L.P. | Testing disaster recovery elements |
US20100250757A1 (en) * | 2009-03-30 | 2010-09-30 | Akhter Aamer S | Redirection of a request for information |
US8892745B2 (en) * | 2009-03-30 | 2014-11-18 | Cisco Technology, Inc. | Redirection of a request for information |
US20110047207A1 (en) * | 2009-08-24 | 2011-02-24 | General Electric Company | System and method for near-optimal media sharing |
US8868635B2 (en) * | 2009-08-24 | 2014-10-21 | Nbcuniversal Media, Llc | System and method for near-optimal media sharing |
US11082353B2 (en) * | 2015-09-28 | 2021-08-03 | Arris Enterprises Llc | Domain name system response spoofing at customer premise equipment device |
Also Published As
Publication number | Publication date |
---|---|
US7770058B2 (en) | 2010-08-03 |
US20070250738A1 (en) | 2007-10-25 |
WO2007124255A1 (en) | 2007-11-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20070250626A1 (en) | System and method for uniform disaster recovery system access | |
US8327022B2 (en) | Method and apparatus for updating a domain name server | |
US8181071B2 (en) | Automatically managing system downtime in a computer network | |
EP1338133B1 (en) | Cache coherent peer-to-peer computing architecture | |
US7467203B2 (en) | System and methods for robust discovery of servers and services in a heterogeneous environment | |
US8316440B1 (en) | System for detecting change of name-to-IP resolution | |
EP1997026B1 (en) | Global names zone | |
CN102571972B (en) | The distributed file system access of site-aware is carried out from outside enterprise network | |
US20060047836A1 (en) | A method for maintaining transaction integrity across multiple remote access servers | |
US20100146132A1 (en) | Methods, Systems, And Computer Program Products For Accessing A Resource Having A Network Address Associated With A Location On A Map | |
US20070112812A1 (en) | System and method for writing data to a directory | |
US8060891B2 (en) | Management of external hardware appliances in a distributed operating system | |
US9275371B2 (en) | Keeping track of a detached e-mail attachment | |
US20100161732A1 (en) | Methods, Systems, And Computer Program Products For Maintaining Consistency Between Non-Geospatial And Geospatial Network Directory Systems | |
US8825877B2 (en) | Session persistence | |
US9363320B2 (en) | Persistent connection between network devices | |
US20040122916A1 (en) | Establishment of network connections | |
US11277372B2 (en) | Name server management of domain name systems using virtual name servers | |
US10044602B2 (en) | Network failover and loop detection in hierarchical networks | |
US20050203993A1 (en) | System and method for optimizing data store selection for write operations | |
US11297032B2 (en) | Method for detecting user migration from enterprise network to non-enterprise network and a device thereof | |
US20020078182A1 (en) | Failover service method and system | |
CN112583891B (en) | Interface document acquisition method and device and server | |
US8224996B2 (en) | Directory viewports | |
JP2003273905A (en) | Method and program for switching communication path |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ELECTRONIC DATA SYSTEMS CORPORATION, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PHAN, RICKY;REEL/FRAME:017801/0632 Effective date: 20060420 |
|
AS | Assignment |
Owner name: ELECTRONIC DATA SYSTEMS, LLC, DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:ELECTRONIC DATA SYSTEMS CORPORATION;REEL/FRAME:022460/0948 Effective date: 20080829 Owner name: ELECTRONIC DATA SYSTEMS, LLC,DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:ELECTRONIC DATA SYSTEMS CORPORATION;REEL/FRAME:022460/0948 Effective date: 20080829 |
|
AS | Assignment |
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ELECTRONIC DATA SYSTEMS, LLC;REEL/FRAME:022449/0267 Effective date: 20090319 Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.,TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ELECTRONIC DATA SYSTEMS, LLC;REEL/FRAME:022449/0267 Effective date: 20090319 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |