Intelligent log gap detection to prevent unnecessary backup promotion
An intelligent log gap detection to prevent unnecessary backup promotion. Specifically, the method and system disclosed herein entail determining whether to pursue a requested database backup type or to promote the requested database backup type to another database backup type, in order to preclude data loss across high availability databases. When a decision is made to pursue the requested database backup type, storage space, intended for backup consolidation on a backup system or media, is saved for future backup requests rather than being consumed as would be the case would the requested database backup type had been promoted.
1. A method for intelligent log gap detection, comprising:
receiving a first database backup request for a first database backup on a database availability cluster (DAC);
making a first determination that a first full database backup has already been performed;
obtaining, based on the first determination, a checkpoint log sequence number (LSN) associated with the first full database backup;
identifying a second database backup that depends from the first full database backup;
identifying a latest database backup from the second database backup;
obtaining a last LSN associated with the latest database backup;
making a second determination that the last LSN mismatches a first last log backup LSN (LLBL);
detecting, based on the second determination, a log gap across the DAC;
promoting, based on detecting the log gap, the first database backup to a second full database backup;
based on the promoting:
issuing a full backup command (FBC);
generating a new cluster trail log record (TLR) using an object ID identifying an active database of the DAC, a timestamp, the last LSN, a set log gap bit (LGB), and a set backup promotion bit (BPB); and
updating a cluster trail log table (TLT) using the new cluster TLR.
2. The method of claim 1 , wherein the first database backup is one selected from a group consisting of a first differential database backup and a first transaction log backup.
3. The method of claim 1 , wherein identifying the second database backup, comprises:
performing a search on a cluster backup chain table (BCT) in reverse chronological order, wherein the cluster BCT comprises a plurality of cluster backup chain records (BCRs); and
identifying one cluster BCR of the plurality of cluster BCRs based on a database backup LSN specified in the one cluster BCR matching the checkpoint LSN.
4. The method of claim 1 , wherein after promoting the first database backup and before generating the new cluster TLR, the method further comprises:
receiving a second database backup request for a third database backup on the DAC;
making a third determination that the last LSN matches a second LLBL;
detecting, based on the third determination, no log gap across the DAC; and
issuing, based on detecting no log gap, one selected from a group consisting of a differential backup command (DBC) and a transaction backup command (TBC).
5. A system, comprising:
a cluster backup agent (CBA); and
a cluster backup service (CBS) operatively connected to the CBA, programmed to:
receive a database backup request for a first database backup on a database availability cluster (DAC);
make a first determination that a first full database backup has already been performed;
obtain, based on the first determination, a checkpoint log sequence number (LSN) associated with the first full database backup;
identify a second database backup that depends from the first full database backup;
identify a latest database backup from the second database backup;
obtain a last LSN associated with the latest database backup;
make a second determination that the last LSN mismatches a last log backup LSN (LLBL); a
detect, based on the second determination, a log gap across the DAC;
promote, based on detecting the log gap, the first database backup to a second full database backup;
based on the promoting:
issue a full backup command (FBC) to the CBA;
generate a new cluster trail log record (TLR) using an object ID identifying an active database of the DAC, a timestamp, the last LSN, a set log gap bit (LGB), and a set backup promotion bit (BPB); and
update a cluster trail log table (TLT) using the new cluster TLR.
6. The system of claim 5 , further comprising:
a first user database replica (UDR) operatively connected to the CBA,
wherein the CBA is programmed to:
create, in response to the FBC, the second full database backup of the first UDR.
7. The system of claim 6 , further comprising:
a database engine instance (DEI) comprising the first UDR, a database metadata repository (DMR), and an engine system database (ESD),
wherein the DMR comprises the LLBL.
8. The system of claim 7 , further comprising:
a database failover cluster (DFC) comprising a plurality of database failover nodes (DFNs) and the DAC,
wherein the DAC comprises a plurality of UDRs comprising the first UDR,
wherein a DFN of the plurality of DFNs comprises the CBS and the DEI.
9. The system of claim 5 , further comprising:
a cluster admin client (CAC) operatively connected to the CBS,
wherein the database backup request is submitted by the CAC.
10. A non-transitory computer readable medium (CRM) comprising computer readable program code, which when executed by a computer processor, enables the computer processor to:
receive a first database backup request for a first database backup on a database availability cluster (DAC);
make a first determination that a first full database backup has already been performed;
obtain, based on the first determination, a checkpoint log sequence number (LSN) associated with the first full database backup;
identify a second database backup that depends from the first full database backup;
identify a latest database backup from the second database backup;
obtain a last LSN associated with the latest database backup;
make a second determination that the last LSN mismatches a last log backup LSN (LLBL);
detect, based on the second determination, a log gap across the DAC;
promote, based on detecting the log gap, the first database backup to a second full database backup;
based on the promoting:
issue a full backup command (FBC);
generate a new cluster trail log record (TLR) using an object ID identifying an active database of the DAC, a timestamp, the last LSN, a set log gap bit (LGB), and a set backup promotion bit (BPB); and
update a cluster trail log table (TLT) using the new cluster TLR.
11. The non-transitory CRM of claim 10 , wherein the first database backup is one selected from a group consisting of a first differential database backup and a first transaction log backup.
12. The non-transitory CRM of claim 10 , wherein to identify the second database backup, the computer readable program code, which when executed by the computer processor, enables the computer processor to:
perform a search on a cluster backup chain table (BCT) in reverse chronological order, wherein the cluster BCT comprises a plurality of cluster backup chain records (BCRs); and
identify a cluster BCR of the plurality of cluster BCRs based on a database backup LSN specified in the cluster BCR matching the checkpoint LSN.
13. The non-transitory CRM of claim 10 , wherein the computer readable program code, when executed by the computer processor, further enables the computer processor to:
after promoting the first database backup and before generating the new cluster TLR:
receive a second database backup request for a third database backup on the DAC;
make a third determination that the last LSN matches a second LLBL;
detect, based on the third determination, no log gap across the DAC; and
issue, based on detecting no log gap, one selected from a group consisting of a differential backup command (DBC) and a transaction backup command (TBC).