Disaster recovery internet protocol address failover

• US 9,104,625 B2
• Filed: 12/11/2012
• Issued: 08/11/2015
• Est. Priority Date: 12/11/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bartholomy, Erik, Giordano, Frank J., Greenlee, Gordan G., Menon, Gourishankar R., Walter, Victor L.
• Primary Examiner(s): Bonzo, Bryce
• Assistant Examiner(s): Mehrmanesh, Elmira
• Application Number:
  US13/673,098
• Publication Number:
  US 20140164817A1
• Time in Patent Office: 973 Days
• Field of Search: 714/4.11
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089

Abstract

An approach is provided for internet protocol (IP) address failover. An application on a primary site is assigned a private IP address. This private IP address is accessible within a local network. This private IP address is mapped to a public IP address, which is accessible to users outside the local network. The application is then replicated to a backup site with the same private IP address used to access it on the primary site. In case of a disaster recover event on the primary site, the replicated application can be accessed on the backup site by way of the public IP address.

Claims

1. A method for disaster recovery internet protocol (IP) address failover, the method comprising:

assigning a private IP address to an application on a primary site, the private IP address being accessible within a local network;

mapping a public IP address to the private IP address, the public IP address being accessible to a plurality of users outside the local network;

replicating the application to a backup site, the replicated application having the private IP address assigned to the application on the primary site; and

in response to a disaster recovery (DR) event, accessing via a domain name system the replicated application on the backup site via the public IP address, wherein the domain name system translates the public IP address to a backup local public IP address, wherein the backup local public IP address is different from the public IP address;

comparing the public IP address and the backup local public IP address for detecting a difference;

indicating, in response to the detecting, the application is hosted on the backup site; and

in response to a request for the application from at least one user, providing the at least one user with access to the replicated application at the back up site via the public IP address, the backup local public IP address and the private IP address.

2. The method of claim 1, wherein the replicated application resides in a dormant state on the backup site prior to the DR event.

3. The method of claim 2, wherein the accessing further comprises activating the replicated application on the backup site.

4. The method of claim 1, wherein the mapping is performed using a Network Address Translation (NAT) protocol.

5. The method of claim 1, further comprising:

assigning a second private IP address to a second application on the primary site;

mapping a second public IP address with the second private IP address;

replicating the second application to a different backup site, the replicated application having the second private IP address assigned to the second application on the second primary site; and

in response to a disaster recovery (DR) event, accessing the second replicated application on the different backup site via the second public IP address.

6. The method of claim 1, further comprising:

receiving, prior to the DR event, a communication to access the application from a user using the public IP address;

retrieving, using the public IP address, the private IP address; and

routing the user to the application via the public IP address and the private IP address.

7. A system for disaster recovery internet protocol (IP) address failover, the system comprising at least one computer device comprising a processor and a non-transitory computer readable storage medium, said storage medium containing program instructions configured to be executed by the processor to implement a method, the method comprising:

assigning a private IP address to an application on a primary site, the private IP address being accessible within a local network;

mapping a public IP address to the private IP address, the public IP address being accessible to a plurality of users outside the local network;

replicating the application to a backup site, the replicated application having the private IP address assigned to the application on the primary site; and

in response to a disaster recovery (DR) event, accessing via a domain name system the replicated application on the backup site via the public IP address, wherein the domain name system translates the public IP address to a backup local public IP address, wherein the backup local public IP address is different from the public IP address;

comparing the public IP address and the backup local public IP address for detecting a difference;

indicating, in response to the detecting, the application is hosted on the backup site; and

in response to a request for the application from at least one user, providing the at least one user with access to the replicated application at the back up site via the public IP address, the backup public IP address and the private IP address.

8. The system of claim 7, wherein the replicated application resides in a dormant state on the backup site prior to the DR event.

9. The system of claim 8, wherein the accessing further comprises activating the replicated application on the backup site.

10. The system of claim 7, wherein the mapping is performed using a Network Address Translation (NAT) protocol.

11. The system of claim 7, wherein the method further comprises:

assigning a second private IP address to a second application on the primary site;

mapping a second public IP address with the second private IP address;

replicating the second application to a different backup site, the replicated application having the second private IP address assigned to the second application on the second primary site; and

in response to a disaster recovery (DR) event, accessing the second replicated application on the different backup site via the second public IP address.

12. The system of claim 7, wherein the method further comprises:

receiving, prior to the DR event, a communication to access the application from a user using the public IP address;

retrieving, using the public IP address, the private IP address; and

routing the user to the application via the public IP address and the private IP address.

13. A computer program product comprising a non-transitory computer readable storage medium having program instructions stored therein, said program instructions configured to be executed by a processor of a computer system to implement a method for disaster recovery internet protocol (IP) address failover, the method comprising:

assigning a private IP address to an application on a primary site, the private IP address being accessible within a local network;

mapping a public IP address to the private IP address, the public IP address being accessible to a plurality of users outside the local network;

replicating the application to a backup site, the replicated application having the private IP address assigned to the application on the primary site; and

in response to a disaster recovery (DR) event, accessing via a domain name system the replicated application on the backup site via the public IP address, wherein the domain name system translates the public IP address to a backup local public IP address, wherein the backup local public IP address is different from the public IP address;

comparing the public IP address and the backup local public IP address for detecting a difference;

indicating, in response to the detecting, the application is hosted on the backup site; and

in response to a request for the application from at least one user, providing the at least one user with access to the replicated application at the back up site via the public IP address, the backup public IP address and the private IP address.

14. The computer program product of claim 13, wherein the replicated application resides in a dormant state on the backup site prior to the DR event.

15. The computer program product of claim 14, wherein the accessing further comprises activating the replicated application on the backup site.

16. The computer program product of claim 13, wherein the mapping is performed using a Network Address Translation (NAT) protocol.

17. The computer program product of claim 13, wherein the method further comprises:

assigning a second private IP address to a second application on the primary site;

mapping a second public IP address to the second private IP address;

replicating the second application to a different backup site, the replicated application having the second private IP address assigned to the second application on the second primary site; and

in response to a disaster recovery (DR) event, accessing the second replicated application on the different backup site via the second public IP address.

18. The computer program product of claim 13, wherein the method further comprises:

receiving, prior to the DR event, a communication to access the application from a user using the public IP address;

retrieving, using the public IP address, the private IP address; and

routing the user to the application via the public IP address and the private IP address.

19. A method for deploying a system for disaster recovery internet protocol (IP) address failover, the method comprising,

providing a computer system operable to:

assign a private IP address to an application on a primary site, the private IP address being accessible within a local network;

map a public IP address to the private IP address, the public IP address being accessible to a plurality of users outside the local network;

replicate the application to a backup site, the replicated application having the private IP address assigned to the application on the primary site; and

in response to a disaster recovery (DR) event, access via a domain name system the replicated application on the backup site via the public IP address, wherein the domain name system translates the public IP address to a backup local public IP address, wherein the backup local public IP address is different from the public IP address;

compare the public IP address and the backup local public IP address for detecting a difference;

indicate, in response to the detecting, the application is hosted on the backup site; and

in response to a request for the application from at least one user, provide the at least one user with access to the replicated application at the back up site via the public IP address, the backup public IP address and the private IP address.