Low impact snapshot database protection in a micro-service environment

Patent metadata

Field	Value
Publication number	US-11307939-B2
Application number	US-201916521853-A
Country	US
Kind code	B2
Filing date	Jul 25, 2019
Priority date	Dec 16, 2016
Publication date	Apr 19, 2022
Grant date	Apr 19, 2022

Abstract

An implementation of the disclosure provides a method including identifying, by a processing device, a plurality of transactions in a transaction queue within a cloud computing environment, each of the transactions comprising an operation associated with a storage device of the cloud computing environment, comparing a priority status of at least one operation comprised by the transaction queue with a status threshold level associated with the snapshot policy, and responsive to determining that the priority status of at least one operation meets the status threshold level, providing, by the processing device subsequent to an execution of the at least one operation, a request to generate a point-in-time snapshot of at least a portion of the storage device, the point-in-time snapshot comprising state information corresponding to an application in the storage device.

First claim

What is claimed is:

1. A system comprising:
a memory to store application data; and
a processing device coupled to the memory to:
identify a plurality of transactions in a transaction queue within a cloud computing environment, each of the transactions comprising an operation to be executed by an application with respect to a storage device of the cloud computing environment;
compare a priority status of at least one operation corresponding to a transaction in the transaction queue with a status threshold level associated with a snapshot policy; and
responsive to determining that the priority status of at least one operation corresponding to the transaction in the transaction queue meets the status threshold level, execute, subsequent to an execution of the at least one operation, a snapshot command to generate a point-in-time snapshot of at least a portion of the storage device modified by the operation corresponding to the transaction in the transaction queue, the point-in-time snapshot comprising state information corresponding to the application in the storage device.

2. The system of claim 1 , wherein the processing device is further to determine whether the transaction queue is in compliance with the snapshot policy by comparing a first number of operations comprised by the transaction queue with a threshold level.

3. The system of claim 2 , wherein the processing device is further to, responsive to determining that the first number of operations comprised by the transaction queue is below the threshold level, execute the snapshot command to generate the point-in-time snapshot.

4. The system of claim 2 , wherein to determine whether the transaction queue is in compliance with the snapshot policy, the processing device is further to:
determine a second number of executed operations comprised by the transaction queue that are executed following a previous point-in-time snapshot associated with the application; and
compare the second number of executed operations with a transaction threshold level associated with the snapshot policy.

5. The system of claim 4 , wherein the processing device is further to, responsive to determining that the second number of executed operations meets the transaction threshold level, execute the snapshot command to generate the point-in-time snapshot.

6. The system of claim 2 , wherein the processing device is further to, responsive to determining that the transaction queue is not in compliance with the snapshot policy, at least one of delay or reschedule the point-in-time snapshot until the transaction queue is in compliance with the snapshot policy.

7. The system of claim 1 , wherein the processing device is further to:
determine whether the transaction queue is in compliance with the snapshot policy by comparing a first number of operations comprised by the transaction queue with a determined depth threshold level; and
responsive to the first number of operations satisfying the determined depth threshold level, generate a request to at least one of halt, delay, or reschedule the point-in-time snapshot.

8. The system of claim 1 , wherein the priority status of the at least one operation is determined based on at least one of system settings, privileges of a user associated with the at least one operation, or whether the user paid a premium for prioritizing the at least one operation.

9. A method comprising:
identifying, by a processing device, a plurality of transactions in a transaction queue within a cloud computing environment, each of the transactions comprising an operation to be executed by an application with respect to a storage device of the cloud computing environment;
comparing a priority status of at least one operation corresponding to a transaction in the transaction queue with a status threshold level associated with a snapshot policy; and
responsive to determining that the priority status of at least one operation corresponding to the transaction in the transaction queue meets the status threshold level, providing, by the processing device subsequent to an execution of the at least one operation, a request to generate a point-in-time snapshot of at least a portion of the storage device modified by the operation corresponding to the transaction in the transaction queue, the point-in-time snapshot comprising state information corresponding to the application in the storage device.

10. The method of claim 9 , further comprising determining whether the transaction queue is in compliance with the snapshot policy, wherein the determining further comprises comparing a first number of operations comprised by the transaction queue with a threshold level.

11. The method of claim 10 , further comprising, responsive to determining that the first number of operations comprised by the transaction queue is below the threshold level, providing the request to generate the point-in-time snapshot.

12. The method of claim 10 , wherein determining whether the transaction queue is in compliance with the snapshot policy further comprises:
determining a second number of executed operations comprised by the transaction queue that are executed following a previous point-in-time snapshot associated with the application; and
comparing the second number of executed operations with a transaction threshold level associated with the snapshot policy.

13. The method of claim 12 , further comprising, responsive to determining that the second number of executed operations meets the transaction threshold level, providing the request to generate the point-in-time snapshot.

14. The method of claim 9 , further comprising:
determining whether the transaction queue is in compliance with the snapshot policy by comparing a first number of operations comprised by the transaction queue with a determined depth threshold level; and
responsive to the first number of operations satisfying the determined depth threshold level, generating a request to at least one of halt, delay, or reschedule the point-in-time snapshot.

15. The method of claim 9 , wherein the priority status of the at least one operation is determined based on at least one of system settings, privileges of a user associated with the at least one operation, or whether the user paid a premium for prioritizing the at least one operation.

16. A non-transitory computer-readable storage medium comprising instructions that when executed, by a processing device, cause the processing device to:
identify, by the processing device, a transaction queue comprising a plurality of transactions associated with a storage device in a cloud computing environment, each of the transactions comprising an operation to be executed by an application in the storage device, the transaction queue storing identifiers of operations performed by the application;
compare a priority status of at least one operation corresponding to a transaction in the transaction queue with a status threshold level associated with a snapshot policy; and
responsive to determining that the priority status of the at least one operation corresponding to the transaction in the transaction queue meets the status threshold level, execute, subsequent to an execution of the at least one operation, a snapshot command to generate a point-in-time snapshot for at least a portion of the storage device modified by the operation corresponding to the transaction in the transaction queue, the point-in-time snapshot comprising state information corresponding to the application in the storage device.

17. The non-transitory computer-readable storage medium of clai

Assignees

• Red Hat Inc

Inventors

• Chen Huamin
• Vyas Jay

Classifications

• G06F11/3006

  where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title

• G06F11/1461 Primary

  Backup scheduling policy · CPC title

• G06F2201/87

  Monitoring of transactions · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• G06F16/128

  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