Mechanism to provide assured recovery for distributed application

• US 8,856,592 B2
• Filed: 01/18/2013
• Issued: 10/07/2014
• Est. Priority Date: 07/29/2010
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Peng, Hailin, Xu, Zhenghua, Liu, Victor
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): BRYAN, JASON B
• Application Number:
  US13/744,449
• Publication Number:
  US 20130132765A1
• Time in Patent Office: 627 Days
• US Class Current: 714/15
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A system and method is provided for providing assured recovery for a distributed application. Replica servers associated with the distributed application may be coordinated to perform integrity testing together for the whole distributed application. The replica servers connect to each other in a manner similar to the connection between master servers associated with the distributed application, thereby preventing the replica servers from accessing and/or changing application data on the master servers during integrity testing.

Claims

1. A method for providing assured recovery for a distributed application executing on at least two master servers, the method comprising:

receiving an indication to initiate integrity testing of at least two replica servers, wherein the at least two replica servers are backup servers for corresponding ones of the at least two master servers and wherein the at least two replica servers connect to the at least two master servers during normal operation;

causing the at least two replica servers to connect to each other instead of connecting to the at least two master servers in response to the indication to initiate integrity testing, wherein the at least two replica servers operate through a connection between them to substantially simulate operation between the at least two master servers; and

re-directing a connection request of a source replica server from connecting with a particular master server to connecting with a corresponding one of the at least two replica servers.

2. The method of claim 1, wherein the re-directing further comprises creating a temporary server alias.

3. The method of claim 1, further comprising:

configuring a second application service instance at one of the at least two replica servers that is similar to a first application service instance at a corresponding one of the at least two master servers; and

redirecting a service access request by the source replica server from accessing the first application service instance to accessing the second application service instance.

4. A method for providing assured recovery for a distributed application executing on at least two master servers, the method comprising:

receiving an indication to initiate integrity testing of at least two replica servers, wherein the at least two replica servers are backup servers for corresponding ones of the at least two master servers and wherein the at least two replica servers connect to the at least two master servers during normal operation;

causing the at least two replica servers to connect to each other instead of connecting to the at least two master servers in response to the indication to initiate integrity testing, wherein the at least two replica servers operate through a connection between them to simulate operation between the at least two master servers;

performing a first type of re-direct for a first connection request by a source replica server from accessing a first type of data source from a particular master server to accessing the first type of data source from a corresponding one of the at least two replica servers; and

performing a second type of re-direct for a second connection request by the source replica server from accessing a second type of data source from the particular master server to accessing the second type of data source from the corresponding replica server, wherein the second type of data source is different than the first type of data source,

wherein the first type of re-direct is different than the second type of re-direct and wherein the first type of redirect is based on the corresponding first type of data source and the second type of redirect is based on the corresponding second type of data source.

5. The method of claim 4, wherein the first type of re-direct comprises creating a temporary server alias to access the first type of data source.

6. The method of claim 4, wherein performing the second type of re-direct comprises:

configuring a second application service instance at the corresponding replica server that is similar to a first application service instance at the particular master server; and

redirecting the second connection request by the source replica server from accessing the first application service instance to accessing the second application service instance.

7. The method of claim 4, wherein receiving an indication to initiate integrity testing of at least two replica servers comprises receiving an indication to perform a first part of testing that is performed within a replica server itself and a second part of testing that involves the at least two replica servers which operate through communication therebetween to complete the testing functions.

8. A first replica server comprising:

a processor; and

one or more tangible computer-readable storage media configured to store computer-readable instructions,

wherein the computer-readable instructions, when executed by the processor, cause the processor to;

receive an indication to initiate integrity testing of the first replica server and a second replica server, wherein the first and second replica servers are backup servers for corresponding ones of at least two master servers, and wherein the first and second replica servers connect to the at least two master servers during normal operation;

connect to the second replica server instead of connecting to one of the at least two master servers in response to the indication to initiate integrity testing,

operate through a connection between the first and second replica servers to substantially simulate operation between the at least two master servers; and

re-direct a connection request of the first replica server from connecting with a particular master server to connecting with the second replica server.

9. The first replica server of claim 8, wherein the computer-readable instructions, when executed by the processor, cause the processor to, responsive to an indication to initiate integrity testing, connect to the second replica server by creating a temporary server alias.

10. The first replica server of claim 8, wherein the computer-readable instructions, when executed by the processor, cause the processor to:

redirect a service access request by the first replica server from accessing a first application service instance at one of the at least two master servers to accessing a second application service instance at the second replica server,

wherein the second application service instance at the second replica server is similar to the first application service instance at the one of the at least two master servers.

11. The first replica server of claim 8, wherein the computer-readable instructions, when executed by the processor, cause the processor to:

receive an indication to initiate integrity testing, wherein the first replica server and a second replica server are backup servers for corresponding ones of at least two master servers and wherein the first and second replica servers connect to the at least two master servers during normal operation;

connect to the second replica server instead of connecting to one of the at least two master servers in response to the indication to initiate integrity testing,

operate through a connection between the first and second replica servers to substantially simulate operation between the at least two master servers; and

perform a first type of re-direct for a first connection request by the first replica server from accessing a first type of data source from a particular master server to accessing the first type of data source from the second replica server; and

perform a second type of re-direct for a second connection request by the first replica server from accessing a second type of data source from the particular master server to accessing the second type of data source from the second replica server, wherein the second type of data source is different than the first type of data source, and

wherein the first type of re-direct is different than the second type of re-direct and wherein the first type of redirect is based on the corresponding first type of data source and the second type of redirect is based on the corresponding second type of data source.

12. The first replica server of claim 11, wherein performing the first type of redirect comprises creating a temporary server alias to access the first type of data source.

13. The first replica server of claim 11,

wherein performing a second type of redirect comprises

redirecting the second connection request by the first replica server from accessing a first application service instance at one of the at least two master servers to accessing a second application service instance at the second replica server,

wherein the second application service instance at the second replica server is similar to the first application service instance at the one of the at least two master servers.