Method, device, and computer program product for managing application system

Patent metadata

Field	Value
Publication number	US-11657019-B2
Application number	US-202016835755-A
Country	US
Kind code	B2
Filing date	Mar 31, 2020
Priority date	Jul 30, 2019
Publication date	May 23, 2023
Grant date	May 23, 2023

Abstract

Techniques manage application systems in an application environment. The application environment includes a first application system, a second application system and a third application system. First snapshot information of a first group of snapshots of the first application system is obtained, the first application system being in active state. Second snapshot information of a second group of snapshots of the second application system is obtained, the second application system being in standby state. It is determined whether the second application system and the third application system have a common snapshot based on the first snapshot information and the second snapshot information. Data is synchronized to the third application system depending on whether the second application system and the third application system have a common snapshot. Overheads required during data synchronization may be reduced as far as possible, and the efficiency of data synchronization may be improved.

First claim

We claim:

1. A method for managing application systems in an application environment, the application environment comprising a first application system, a second application system that takes over work of the first application system when the first application system is over-loaded, and a third application system that operates as a backup system, the method comprising:
performing synchronous replication from the first application system to the second application system;
performing asynchronous replication from the first application system to the third application system;
obtaining first snapshot information about a first group of snapshots of the first application system, including version information of snapshots in the first group of snapshots of the first application system, wherein the first group of snapshots of the first application system comprises at least two snapshots stored in the first application system and previously transmitted from the first application system to the third application system, the first application system being in active state;
obtaining second snapshot information about a second group of snapshots of the second application system, including version information of snapshots in the second group of snapshots of the second application system, wherein the second group of snapshots of the second application system comprises at least two snapshots stored in the second application system, the second application system being in standby state;
determining whether the second application system and the third application system have at least one common snapshot at least in part by comparing the first snapshot information and the second snapshot information, wherein the second application system and the third application system are determined to have at least one common snapshot in response to a determination that the first application system and the second application system have at least one common snapshot; and
synchronizing data to the third application system depending on whether the second application system and the third application system have at least one common snapshot.

2. The method of claim 1 , wherein determining whether the second application system and the third application system have the common snapshot further comprises:
in response to determining the first snapshot information does not match the second snapshot information, determining the second application system and the third application system have no common snapshot.

3. The method of claim 1 , wherein determining whether the second application system and the third application system have the common snapshot further comprises:
determining the number of common snapshots between the first group of snapshots and the second group of snapshots based on the first snapshot information and the second snapshot information; and
in response to determining the number is 2, determining the second application system and the third application system have at least one common snapshot.

4. The method of claim 1 , wherein determining whether the second application system and the third application system have the common snapshot further comprises:
determining the number of common snapshots between the first group of snapshots and the second group of snapshots based on the first snapshot information and the second snapshot information;
in response to determining the number is 1,
obtaining third snapshot information of a third group of snapshots of the third application system, including version information of snapshots in the third group of snapshots of the third application system; and
determining whether the second application system and the third application system have a common snapshot at least in part by comparing the second snapshot information and the third snapshot information.

5. The method of claim 4 , wherein determining whether the second application system and the third application system have the common snapshot further comprises at least one of:
in response to determining at least one part of the second snapshot information matches at least one part of the third snapshot information, determining the second application system and the third application system have a common snapshot; and
in response to determining the second snapshot information does not match the third snapshot information, determining the second application system and the third application system have no common snapshot.

6. The method of claim 1 , wherein synchronizing the data to the third application system depending on whether the second application system and the third application system have the common snapshot comprises:
in response to determining the second application system and the third application system have at least one common snapshot, synchronizing data to the third application system based on the at least one common snapshot.

7. The method of claim 6 , wherein synchronizing the data to the third application system based on the at least one common snapshot comprises:
determining a latest version snapshot of the at least one common snapshot;
determining a difference portion between a storage system in the second application system and the latest version snapshot; and
synchronizing the difference portion to the third application system.

8. The method of claim 1 , wherein synchronizing the data to the third application system depending on whether the second application system and the third application system have the common snapshot comprises:
in response to determining the second applications system and the third application system have no common snapshot, synchronizing the data to the third application system based on full copy.

9. The method of claim 1 , further comprising: performing the method in response to detecting a workload of the first application system is higher than a predetermined threshold.

10. The method of claim 9 , further comprising:
performing failover from the first application system to the second application system so that the second application system is in active state.

11. The method of claim 1 , wherein the synchronous replication from the first application system to the second application system is performed over a synchronous replication connection between the first application system and the second application system;
wherein the asynchronous replication from the first application system to the third application system is performed over an asynchronous replication connection between the first application system and the third application system; and
wherein the method further comprises:
transmitting the first group of snapshots of the first application system from the first application system to the third application system through the asynchronous replication connection between the first application system and the third application system prior to both i) obtaining the first snapshot information about the first group of snapshots of the first application system, and ii) obtaining the second snapshot information about the second group of snapshots of the second application system.

12. The method of claim 11 , wherein the work of the first application system includes serving at least one request from a client to access data.

13. The method of claim 12 , wherein the second application system is further configured to take over the work of the first application system when the first application system fails.

14. A device for managing application systems in an application environment, the application environment comprising a first application system, a second application system that takes over work of the first applicatio

Assignees

• Emc Ip Holding Co Llc

Inventors

• Xu Hongru
• Xiong Tianfang
• Shang Qiu
• Long Fei

Classifications

• G06F11/203 Primary

  using migration · CPC title

• G06F16/182

  Distributed file systems · CPC title

• G06F16/2365 Primary

  Ensuring data consistency and integrity · CPC title

• G06F11/2041

  with more than one idle spare processing component · CPC title

• G06F16/128 Primary

  Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16) · CPC title