IDLE POINT AUDITING FOR DATABASES
Idle points for a database, such as a database management system or a relational database management system (RDMS), may be marked in an audit log of a backup device coupled to the database. The backup device may receive an indication that the database has reached an idle point and verify the idle point through a data control system coupled to the database and the backup device. Once the idle point is verified, the idle point is logged in the audit log along with the date and time of the idle point. The idle point information may be used during recovery of the database from the backup device.
1 . A method, comprising:
determining when a database has reached an idle point;
verifying the idle point is reached; and
when the idle point is verified, marking the idle point in an audit log.
2 . The method of claim 1 , in which the verifying step comprises querying an operating system step control coupled to the database to verify the database has reached the idle point.
3 . The method of claim 2 , in which the database is at least one of a relational database management system (RDMS), a network database management system, and a transaction processor.
4 . The method of claim 1 , in which the step of marking the idle point comprises storing a date and time of the idle point.
5 . The method of claim 1 , in which the determining step comprises receiving a request to mark the idle point when the idle point is reached.
6 . The method of claim 1 , further comprising creating a backup of the database with an integrated recovery utility (IRU) after the idle point is verified.
7 . The method of claim 6 , further comprising restoring the database from the backup and the audit log from the idle point after creating the backup.
8 . A computer program product, comprising:
a non-transitory computer readable medium comprising:
code to determine when a database has reached an idle point;
code to verify the idle point is reached; and
code to mark the idle point in an audit log when the idle point is verified.
9 . The computer program product of claim 8 , in which the medium further comprises code to query an operating system step control coupled to the database to verify the database has reached the idle point.
10 . The computer program product of claim 9 , in which the database is at least one of a relational database management system (RDMS), a network database management system, and a transaction processor.
11 . The computer program product of claim 8 , in which the medium further comprises code to store a date and time of the idle point.
12 . The computer program product of claim 8 , in which the medium further comprises code to receive a request to mark the idle point when the idle point is reached.
13 . The computer program product of claim 8 , in which the medium further comprises code to create a backup of the database with an integrated recovery utility (IRU).
14 . The computer program product of claim 13 , in which the medium further comprises code to restore the database from the backup and the audit log from the idle point.
15 . An apparatus, comprising:
a memory storing an audit log; and
a processor coupled to the memory, in which the processor is configured:
to determine when a database has reached an idle point;
to verify the idle point is reached; and
to mark the idle point in the audit log when the idle point is verified.
16 . The apparatus of claim 15 , in which the processor is further configured to query an operating system step control coupled to the database to verify the database has reached the idle point.
17 . The apparatus of claim 16 , in which the database is at least one of a relational database management system (RDMS), a network database management system, and a transaction processor.
18 . The apparatus of claim 15 , in which the processor is further configured to store a date and time of the idle point.
19 . The apparatus of claim 15 , in which the processor is further configured to receive a request to mark the idle point when the idle point is reached
20 . The apparatus of claim 15 , in which the processor is further configured to create a backup of the database with an integrated recovery utility (IRU).