Incremental forever backups for exchange

• US 10,146,631 B1
• Filed: 09/30/2015
• Issued: 12/04/2018
• Est. Priority Date: 09/30/2015
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Pradeep, Anappa, Yadav, Sunil, Tokuri, Suman, Mandic, Vladimir, Buchman, Matthew D
• Primary Examiner(s): Corrielus, Jean M
• Application Number:
  US14/870,717
• Time in Patent Office: 1,161 Days
• Field of Search: 707645, 707646
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

An incremental backup of a database includes issuing a request to a copy service requesting a snapshot of a volume having the database, and identifying a writer of the database that should participate in creating the snapshot. From the snapshot, changes to the database since a last backup of the database and log files associated with the database that include data not yet committed to the database, are transmitted to a backup storage unit.

Claims

1. A method for an incremental block-based backup of a database stored on a volume of a backup client comprising:

registering the database with a driver to track changes to blocks on the volume that are associated with the database;

issuing a request to a copy service requesting a snapshot of the volume having the database, and identifying a writer of the database that participates in creating the snapshot;

receiving an indication from the copy service that the snapshot of the volume has been created on the backup client;

receiving, from the driver, an identification of changed file blocks associated with the database, the changed file blocks comprising changes to the database since a last backup of the database;

requesting a dump of a header of the database;

reviewing the dump of the header to identify uncommitted log files associated with the database;

based on the review and upon the snapshot having been created, identifying on the snapshot the uncommitted log files associated with the database, the uncommitted log files comprising data not yet committed to the database on the snapshot; and

transmitting for the incremental block-based backup of the database the changed file blocks and the uncommitted log files to a backup storage unit, wherein the incremental block-based backup of the database is performed without backing up other file blocks of the database that have not changed since the last backup, without backing up other changed file blocks of the volume that are not associated with the database, and wherein the incremental block-based backup of the database allows the database to be backed up within an amount of time that is less than an amount of time required for a file-based backup of the database.

2. The method of claim 1 wherein the changes to the database are stored in a first container on the backup storage unit, and the uncommitted log files are stored in a second container on the backup storage unit, separate from the first container.

3. The method of claim 1 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein a synthetic full backup of the database is created on the backup storage unit based on the virtual hard disk file and the virtual hard disk differencing file.

4. The method of claim 1 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein the virtual hard disk file and the virtual hard disk differencing file are maintained on the backup storage unit as separate files.

5. The method of claim 1 wherein the transmitting for the incremental backup comprises:

excluding from the transmission other log files associated with the database, wherein the other log files comprise data committed to the database on the snapshot.

6. The method of claim 1 wherein the database comprises a Microsoft Exchange Database.

7. The method of claim 1 wherein data in an uncommitted log file is committed to the database when a size of the uncommitted log file reaches a pre-determined size.

8. A system for an incremental block-based backup of a database stored on a volume of a backup client, the system comprising:

a processor-based system executed on a computer system and configured to;

issue a request to a copy service requesting a snapshot of the volume having the database, and identifying a writer of the database that participates in creating the snapshot;

receive an indication from the copy service that the snapshot of the volume has been created on the backup client;

identify on the snapshot changed file blocks associated with the database, the changed file blocks comprising changes to the database since a last backup of the database;

upon the snapshot having been created, search the snapshot for uncommitted log files associated with the database, the uncommitted log files comprising data not yet committed to the database on the snapshot; and

transmit for the incremental block-based backup of the database the changed file blocks and the uncommitted log files to a backup storage unit, wherein the incremental block-based backup of the database is performed without backing up other file blocks of the database that have not changed since the last backup, without backing up other changed file blocks of the volume that are not associated with the database, and wherein the incremental block-based backup of the database allows the database to be backed up within an amount of time that is less than an amount of time required for a file-based backup of the database.

9. The system of claim 8 wherein the changes to the database are stored in a first container on the backup storage unit, and the uncommitted log files are stored in a second container on the backup storage unit, separate from the first container.

10. The system of claim 8 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein a synthetic full backup of the database is created on the backup storage unit based on the virtual hard disk file and the virtual hard disk differencing file.

11. The system of claim 8 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein the virtual hard disk file and the virtual hard disk differencing file are maintained on the backup storage unit as separate files.

12. The system of claim 8 wherein the processor-based system is configured to:

exclude from the transmission other log files associated with the database, wherein the other log files comprise data committed to the database on the snapshot.

13. The system of claim 8 wherein the processor-based system executed on the computer system is configured to:

request a dump of a header of the database; and

review the dump of the header to identify the uncommitted log files of the database.

14. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to implement a method for an incremental block-based backup of a database stored on a volume of a backup client, the method comprising:

issuing a request to a copy service requesting a snapshot of the volume having the database, and identifying a writer of the database that participates in creating the snapshot;

receiving an indication from the copy service that the snapshot of the volume has been created on the backup client;

identifying on the snapshot changed file blocks associated with the database, the changed file blocks comprising changes to the database since a last backup of the database;

requesting a dump of a header of the database;

reviewing the dump of the header to identify uncommitted log files associated with the database;

based on the review and upon the snapshot having been created, searching the snapshot for the uncommitted log files associated with the database, the uncommitted log files comprising data not yet committed to the database on the snapshot; and

transmitting for the incremental block-based backup of the database the changed file blocks and the uncommitted log files to a backup storage unit, wherein the incremental block-based backup of the database is performed without backing up other file blocks of the database that have not changed since the last backup, without backing up other changed file blocks of the volume that are not associated with the database, and wherein the incremental block-based backup of the database allows the database to be backed up within an amount of time that is less than an amount of time required for a file-based backup of the database.

15. The computer program product of claim 14 wherein the changes to the database are stored in a first container on the backup storage unit, and the uncommitted log files are stored in a second container on the backup storage unit, separate from the first container.

16. The computer program product of claim 14 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein a synthetic full backup of the database is created on the backup storage unit based on the virtual hard disk file and the virtual hard disk differencing file.

17. The computer program product of claim 14 wherein a first container on the backup storage unit comprises a virtual hard disk file that stores a full backup of the database, a second container on the backup storage unit comprises a virtual hard disk differencing file that stores the changes to the database, and

wherein the virtual hard disk file and the virtual hard disk differencing file are maintained on the backup storage unit as separate files.

18. The computer program product of claim 14 wherein the transmitting for the incremental backup comprises:

excluding from the transmission other log files associated with the database, wherein the other log files comprise data committed to the database on the snapshot.

19. The computer program product of claim 14 wherein the database comprises a Microsoft Exchange Database.

20. The computer program product of claim 14 wherein the method comprises:

registering the database with a driver to track changes to blocks on the volume that are associated with the database; and

receiving, from the driver, an identification of the changed file blocks.