Methods and systems for protecting databases of a database availability group

Patent metadata

Field	Value
Publication number	US-11216341-B2
Application number	US-202016904362-A
Country	US
Kind code	B2
Filing date	Jun 17, 2020
Priority date	Apr 11, 2019
Publication date	Jan 4, 2022
Grant date	Jan 4, 2022

Abstract

Methods and systems for storage services is provided. One method includes configuring by a processor, a database availability group (DAG) storing an active database copy at a first computing node and a passive database copy of the active database copy at a second computing node; initiating a backup operation for backing up the passive database copy from the second computing node; and interfacing with the first computing node by the second computing node for completing the backup operation. The first computing node identifies logs for the backup operation, backs up the identified logs and provides metadata associated with the backup of the identified logs to the second computing node. The second computing node updates metadata for the backup operation such that a backup copy of the passive database copy points to the second node with metadata received from the first computing node.

First claim

What is claimed is:

1. A method, comprising:
initiating, by a second computing node, a backup operation to backup a passive database copy stored by the second computing node, the passive database copy corresponding to an active database copy stored by a first computing node, the passive database copy and the active database copy operating within a database availability group;
requesting, by the second computing node, log information for the backup operation from the first computing node;
receiving, by the second computing node, log backup metadata associated with a log backup taken by the first computing node, in response to the request from the second computing node;
updating, by the second computing node, metadata for the backup operation to point a backup copy of the passive database copy to the second computing node indicating that the backup copy and the received log backup metadata is based on the passive database copy; and
upon completion of the backup operation, enabling by the second computing node access to the passive database copy.

2. The method of claim 1 , further comprising:
indicating, by a policy object for the database availability group that the backup copy can be based on the passive database copy; and
receiving, by the second computing node, a request for the backup operation based on the policy object.

3. The method of claim 1 , further comprising:
selecting the backup copy for a restore operation; and
executing the restore operation by utilizing a database header associated with the backup operation to determine a log chain.

4. The method of claim 3 , further comprising:
updating the metadata for the backup copy to indicate current ownership of the active database copy.

5. The method of claim 1 , further comprising:
storing a single copy of the passive database copy within the database availability group at the second computing node.

6. The method of claim 1 , further comprising:
to complete the backup operation, using a plugin by the second computing node to interface with a database application.

7. The method of claim 1 , further comprising:
to complete the backup operation, using a plugin by the second computing node to interface with a storage system that stores the backup copy.

8. A non-transitory, machine readable storage medium having stored thereon instructions for performing a method, comprising machine executable code which when executed by at least one machine, causes the machine to:
initiate a backup operation to backup a passive database copy stored by a second computing node, the passive database copy corresponding to an active database copy stored by a first computing node, the passive database copy and the active database copy operating within a database availability group;
request log information for the backup operation by the second computing node from the first computing node;
receive log backup metadata associated with a log backup at the second computing node, the log backup taken by the first computing node, in response to the request from the second computing node;
update metadata for the backup operation to point a backup copy of the passive database copy to the second computing node indicating that the backup copy and the received log backup metadata is based on the passive database copy; and
select the backup copy for a restore operation.

9. The non-transitory storage medium of claim 8 , wherein upon completion of the backup operation, access to the passive database copy is enabled by the second computing node.

10. The non-transitory storage medium of claim 8 , wherein a policy object for the database availability group indicates that the backup copy can be based on the passive database copy.

11. The non-transitory storage medium of claim 8 , wherein to complete the backup operation, a plugin is used by the second computing node to interface with a database application.

12. The non-transitory storage medium of claim 8 , wherein to complete the backup operation, a plugin is used by the second computing node to interface with a storage system that stores the backup copy.

13. The non-transitory storage medium of claim 8 , wherein a single copy of the passive database copy is stored within the database availability group at the second computing node.

14. The non-transitory storage medium of claim 8 , wherein the machine executable code further causes the machine: execute the restore operation by utilizing a database header associated with the backup operation to determine a log chain.

15. A system, comprising:
a second computing node storing a passive database copy corresponding to an active database copy stored by a first computing node, the second computing node having a memory containing machine readable medium comprising machine executable code having stored thereon instructions; and a processor coupled to the memory configured to execute the machine executable code to:
initiate a backup operation to backup the passive database copy, the passive database copy and the active database copy configured to operate within a database availability group;
request log information for the backup operation from the first computing node;
receive log backup metadata associated with a log backup, the log backup taken by the first computing node, in response to the request from the second computing node; and
update metadata for the backup operation to point a backup copy of the passive database copy to the second computing node indicating that the backup copy and the received log backup metadata is based on the passive database copy.

16. The system of claim 15 , wherein the processor is further configured to execute the machine executable code to:
select the backup copy for a restore operation;
execute the restore operation by utilizing a database header associated with the backup operation to determine a log chain.

17. The system of claim 15 , wherein a policy object for the database availability group indicates that the backup copy can be based on the passive database copy.

18. The system of claim 15 , wherein to complete the backup operation, a plugin is used by the second computing node to interface with a database application.

19. The system of claim 15 , wherein to complete the backup operation, a plugin is used by the second computing node to interface with a storage system that stores the backup copy.

20. The system of claim 15 , wherein a single copy of the passive database copy is stored within the database availability group at the second computing node.

Assignees

• Netapp Inc

Inventors

• Palaiah Balamurali
• Karinta Vineeth
• Pahade Kavish
• Wu Grace Zhanglei

Classifications

• G06F11/1448

  Management of the data involved in backup or backup restore · CPC title

• G06F11/1471

  involving logging of persistent data for recovery · CPC title

• G06F11/2038

  with a single idle spare processing component · CPC title

• G06F11/1458

  Management of the backup or restore process · CPC title

• G06F16/1734

  Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title