SYNCHRONIZATION OF A DATABASE BY RESTORING COPIES OF CHANGED DATABASE OBJECTS
Systems and methods for performing backup and other secondary copy operations for large databases (e.g., “big data”), such as the Greenplum database, are described. In some cases, the systems and methods may maintain a second instance of a source database (e.g., Greenplum) using live synchronization (e.g., “Live Sync”), which performs incremental replication between a virtual machine containing a large database (e.g., a virtual machine containing a Greenplum database) and a synced copy of the virtual machine.
1 . A computer-implemented method for maintaining a second synchronized copy of a large database at a virtual machine, the computer-implemented method comprising:
causing a full or incremental backup of a production database to be performed resulting in a backup copy of the production database,
wherein the production database is stored at a source virtual machine,
wherein the backup copy is stored on a secondary storage device;
using the backup copy, identifying changed database objects that have changed since a prior synchronization of the production database with a second copy of the production database at a destination virtual machine;
storing in a changes index, application-level and block-level identification information associated with the identified changed database objects;
using the application-level and the block-level identification information, restoring the changed database objects from the backup copy of the production database; and
replicating the restored database objects to the second copy of the production database at the destination virtual machine to synchronize the second copy of the production database with the production database.
2 . The computer-implemented method of claim 1 , wherein the production database is a Greenplum database.
3 . The computer-implemented method of claim 1 , further comprising: identifying append-only tables of a Greenplum database that have changed since the prior synchronization.
4 . The computer-implemented method of claim 1 , wherein the changes index is stored separated from the source virtual machine.
5 . The computer-implemented method of claim 1 , wherein replicating the restored objects to the second copy of the production database at the destination virtual machine comprises performing continuous data replication on the restored objects.
6 . The computer-implemented method of claim 1 , wherein replicating the restored objects to the second copy of the production database at the destination virtual machine comprises performing block-level replication on the restored objects.
7 . The computer-implemented method of claim 1 , wherein the backup copy of the production database
comprises a copy of a catalog of database objects,
wherein the catalog is managed by the production database;
and the computer-implemented method further comprises using the copy of the catalog to identify changed objects.
8 . The computer-implemented method of claim 7 , wherein the copy of the catalog comprises, for each of the database objects in the catalog, a timestamp indicating time corresponding database object was last modified.
9 . The computer-implemented method of claim 1 , wherein the full or incremental backup of the production database is performed by the production database.
10 . The computer-implemented method of claim 1 , wherein the full or incremental backup of the production database is performed by a secondary storage management system that also manages the second copy of the production database at the destination virtual machine.
11 . A system, comprising:
at least one computing device coupled to at least one processor, wherein the at least one computing device is configured to:
cause a full or incremental backup of a production database to be performed resulting in a backup copy of the production database,
wherein the production database is stored at a source virtual machine,
wherein the backup copy is stored on a secondary storage device;
using the backup copy, identify changed database objects that have changed since a prior synchronization of the production database with a second copy of the production database at a destination virtual machine;
store in a changes index, application-level and block-level identification information associated with the identified changed database objects;
using the application-level and the block-level identification information, restore the changed database objects from the backup copy of the production database; and
replicate the restored database objects to the second copy of the production database at the destination virtual machine to synchronize the second copy of the production database with the production database.
12 . The system of claim 11 , wherein the production database is a Greenplum database.
13 . The system of claim 11 , wherein the at least computing device is further configured to: identify append-only tables of a Greenplum database that have changed since the prior synchronization.
14 . The system of claim 11 , wherein the changes index is stored separated from the source virtual machine.
15 . The system of claim 11 , wherein replicating the restored objects to the second copy of the production database at the destination virtual machine comprises performing continuous data replication on the restored objects.
16 . The system of claim 11 , wherein replicating the restored objects to the second copy of the production database at the destination virtual machine comprises performing block-level replication on the restored objects.
17 . The system of claim 11 , wherein the backup copy of the production database comprises a copy of a catalog of database objects,
wherein the catalog is managed by the production database;
and the at least computing device is further configured to: use the copy of the catalog to identify changed objects.
18 . The system of claim 17 , wherein the copy of the catalog comprises, for each of the database objects in the catalog, a timestamp indicating time corresponding database object was last modified.
19 . The system of claim 11 , wherein the full or incremental backup of the production database is performed by the production database.
20 . The system of claim 11 , wherein the full or incremental backup of the production database is performed by a secondary storage management system that also manages the second copy of the production database at the destination virtual machine.