System and method for creating a series of online snapshots for recovery purposes

Claim 3

The method of claim 1 , wherein restoring one or more pre-update snapshot images upon notification that the recovery indication was recieved comprises: (a) restoring a first pre-update snapshot image of the one or more pre-update snapshot images; (b) testing the data to determined if the problem is resolved; (c) restoring a second pre-update snapshot image if the problem still exists; and (d) repeating (b) and (c) until the problem is resolved.

Claim 4

The method of claim 1 , wherein creating each file snapshot of the one or more file snapshots comprises: registering one or more files with a snapshot software component technology, wherein said registering is performed using a file backup and recovery management utility; the snapshot software component technology determining an appropriate methodology to handle read requests and write requests received during the file snapshot of each registered file; starting the snapshot software component technology; the file backup and recovery management utility snapshot processing each registered file such that the file snapshot is consistent with the state of each registered file at the point in time of the start of the snapshot software component technology; wherein read requests and write requests are operable to be performed concurrently with said snapshot processing each registered file.

Claim 5

The method of claim 3 , further comprising processing read requests from the registered files and write requests to the registered files concurrently with said snapshot processing each registered file.

Claim 6

The method of claim 3 , wherein the snapshot software component technology determining an appropriate methodology to handle read requests and write requests received during the file snapshot of each registered file comprises: choosing the appropriate methodology for each registered file independent of the chosen methodology for the other registered files; and choosing one of the following methodologies for each registered file: a software based methodology using a memory cache, a software based methodology using a disk cache, or a hardware based methodology using one or more intelligent storage devices.

Claim 7

The method of claim 5 , wherein, when the methodology used to handle read requests and write requests received during the file snapshot of each registered file is the software based methodology, the snapshot software component technology handling read requests received during the file snapshot of each registered file comprises: capturing client reads for each registered file; for each captured client read, if the read is for updated data, returning the data from the cache; and for each captured client read, if the read is for non-updated data, returning the data from the registered file.

Claim 8

The method of claim 3 , wherein, when the methodology used to handle read requests and write requests received during the file snapshot of each registered file is the software based methodology, the snapshot software component technology handling write requests received during the file snapshot of each registered file comprises: capturing writes to each registered file; and for each captured write to a registered file, prior to allowing the captured write to complete, saving a pre-image of an appropriate data block of the registered file to a cache if the appropriate data block of the registered file has no previously saved pre-image in the cache.

Claim 9

The method of claim 3 , wherein, when the methodology used to handle read requests and write requests received during the file snapshot of each registered file is the hardware based methodology, the snapshot software component technology handling read requests received during the file snapshot of each registered file comprises: capturing client reads for each registered file; and for each captured client read, returning the data from a mirrored volume.

Claim 10

The method of claim 3 , wherein, when the methodology used to handle read requests and write requests received during the file snapshot of each registered file is the hardware based methodology, the snapshot software component technology handling write requests received during the file snapshot of each registered file comprises allowing normal write processing to a primary volume.

Claim 11

The method of claim 3 , wherein the file backup and recovery management utility snapshot processing each registered file comprises copying a pre-image version of updated data to a cache.

Claim 12

(Original) The method of claim 10 , wherein the location from which the pre-image version of updated data is retrieved is dependent upon the chosen methodology.

Claim 13

The method of claim 11 , wherein the chosen methodology is the software based methodology; and the location from which the pre-image version of updated data is retrieved is the memory cache.

Claim 14

The method of claim 11 , wherein the chosen methodology is the software based methodology; and the location from which the pre-image version of updated data is retrieved is the disk cache.

Claim 15

The method of claim 11 , wherein the chosen methodology is the hardware based methodology; and the location from which the pre-image version of updated data is retrieved is the one or more intelligent storage devices.

Claim 16

The method of claim 3 , further comprising: performing initialization processing prior to registering one or more files with the snapshot software component technology, wherein the initialization processing operates to prepare the one or more files for the snapshot; stopping the snapshot software component technology, after the file backup and recovery management utility completes snapshot processing the one or more registered files; and performing termination processing, after stopping the snapshot software component technology.

Claim 17

The method of claim 1 , wherein creating each file snapshot of the one or more file snapshots comprises: registering one or more files with a snapshot software component technology, wherein said registering is performed using a file backup and recovery management software utility; the snapshot software component technology determining an appropriate methodology to handle read requests and write requests received during the file snapshot of each registered file; starting the snapshot software component technology; allowing concurrent read requests from the registered files and write requests to the registered files after the start of the snapshot software component technology; and the file backup and recovery management software utility snapshot processing each registered file such that the file snapshot is consistent with the state of each registered file at the point in time of the start of the snapshot software component technology.

Claim 20

The method of claim 17 , wherein restoring one or more pre-update snapshot images upon notification that the recovery indication was received comprises: (a) restoring a first pre-update snapshot image of the one or more pre-update snapshot images; (b) testing the data to determine if the problem is resolved; (c) restoring a second pre-update snapshot image if the problem still exists; and (d) repeating (b) and (c) until the problem is resolved.

Claim 21

The method of claim 17 , wherein creating each database file snapshot of the one or more database file snapshots comprises: registering one or more database files associated with a database with a snapshot software component technology, wherein said registering is performed using a database backup and recovery management utility; the snapshot software component an appropriate methodology to handle read requests and write requests received during the database snapshot of each registered database file; starting the snapshot software component technology; the database backup and recovery management utility snapshot processing each registered database file such that the database snapshot is consistent with the state of each registered database file at the point in time of the start of the snapshot software component technology; wherein read requests and write requests are operable to be performed concurrently with said snapshot processing each registered database file.

Claim 22

The method of claim 19 , wherein prior to starting the snapshot software component technology, the method further comprises: stopping the database; quiescing the database; and wherein prior to the database backup and recovery management utility snapshot processing each registered database file, the method further comprises restarting the database.

Claim 23

The method of claim 20 , wherein quiescing the database further comprises shutting the database down.

Claim 24

The method of claim 19 , further comprising: database objects associated with the database; wherein prior to starting the snapshot software component technology, the method further comprises: placing the database objects in an extended logging mode; wherein prior to the database backup and recovery management utility snapshot processing each registered database file, the method further comprises: removing the database objects from the extended logging mode; and synchronizing the database.

Claim 25

The method of claim 22 , wherein the database is Oracle and the extended logging mode is backup mode.

Claim 26

The method of claim 19 , further comprising processing read requests from the registered database files and write requests to the registered database files concurrently with said snapshot processing each registered database file.

Claim 27

The method of claim 19 , wherein the snapshot software component technology determining an appropriate methodology to handle read requests and write requests received during the database snapshot of each registered database file comprises: choosing the appropriate methodology for each registered database file independent of the chosen methodology for the other registered database files; and choosing one of the following methodologies for each registered database file: a software based methodology using a memory cache, a software based methodology using a disk cache, or a hardware based methodology using one or more intelligent storage devices.

Claim 28

The method of claim 25 , wherein, when the methodology used to handle read requests and write requests received during the database snapshot of each registered database file is the software based methodology, the snapshot software component technology handling read requests received during the database snapshot of each registered database file comprises: capturing client reads for each registered database file; for each captured client read, if the read is for updated data, returning the data from the cache; and for each captured client read, if the read is for non-updated data, returning the data from the registered database file.

Claim 29

The method of claim 25 , wherein, when the methodology used to handle read requests and write requests received during the database snapshot of each registered database file is the software based methodology, the snapshot software component technology handling write requests received during the database snapshot of each registered database file comprises: capturing writes to each registered database file; and for each captured write to a registered database file, prior to allowing the captured write to complete, saving a pre-image of an appropriate data block of the registered file to a cache if the appropriate data block of the registered file has no previously saved pre-image in the cache.

Claim 30

The method of claim 25 , wherein, when the methodology used to handle read requests and write requests received during the database snapshot of each registered database file is the hardware based methodology, the snapshot software component technology handling read requests received during the database snapshot of each registered database file comprises: capturing client reads for each registered database file; and for each captured client read, returning the data from a mirrored volume.

Claim 31

The method of claim 25 , wherein, when the methodology used to handle read requests and write requests received during the database snapshot of each registered database file is the hardware based methodology, the snapshot software component technology handling write requests received during the database snapshot of each registered database file comprises allowing normal write processing to a primary volume.

Claim 32

The method of claim 25 , wherein the database backup and recovery management utility snapshot processing each registered database file comprises copying a pre-image version of updated data to a cache.

Claim 33

The method of claim 30 , wherein the location from which the pre-image version of updated data is retrieved is dependent upon the chosen methodology.

Claim 34

The method of claim 31 , wherein the chosen methodology is the software based methodology; and the location from which the pre-image version of updated data is retrieved is the memory cache.

Claim 35

The method of claim 31 , wherein the chosen methodology is the software based methodology; and the location from which the pre-image version of updated data is retrieved is the disk cache.

Claim 36

The method of claim 31 , wherein the chosen methodology is the hardware based methodology; and the location from which the pre-image version of updated data is retrieved is the one or more intelligent storage devices.

Claim 37

The method of claim 19 , further comprising: performing initialization processing prior to registering one or more database files with the snapshot software component technology, wherein the initialization processing operates to prepare the one or more database files for the snapshot; stopping the snapshot software component technology, after the database backup and recovery management utility completes snapshot processing the one or more registered database files; and performing termination processing, after stopping the snapshot software component technology.