WO2016069423A1 - Point in time database restore from storage snapshots - Google Patents

Point in time database restore from storage snapshots Download PDF

Info

Publication number
WO2016069423A1
WO2016069423A1 PCT/US2015/057275 US2015057275W WO2016069423A1 WO 2016069423 A1 WO2016069423 A1 WO 2016069423A1 US 2015057275 W US2015057275 W US 2015057275W WO 2016069423 A1 WO2016069423 A1 WO 2016069423A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
snapshot
log
storage
data
Prior art date
Application number
PCT/US2015/057275
Other languages
French (fr)
Inventor
Kevin Farlee
Lin Chan
Andrew Jason Cherry
Original Assignee
Microsoft Technology Licensing, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Technology Licensing, Llc filed Critical Microsoft Technology Licensing, Llc
Priority to CN201580057716.8A priority Critical patent/CN107077404B/en
Priority to JP2017523303A priority patent/JP2017533520A/en
Priority to EP15794386.1A priority patent/EP3213212B1/en
Priority to RU2017114019A priority patent/RU2017114019A/en
Priority to BR112017005834A priority patent/BR112017005834A2/en
Publication of WO2016069423A1 publication Critical patent/WO2016069423A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80—Database-specific techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • One embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database.
  • the system includes a database.
  • the database includes data storage for storing data items and log storage for storing log records.
  • the system further includes one or more processors and one or more computer readable media.
  • the one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform various actions of a method.
  • the method includes taking a first snapshot of the data storage of the database at a first time.
  • the method further includes capturing a first state of the log storage corresponding to the first snapshot of the data storage of the database.
  • the log storage comprises an enumeration of operations on the data storage of the database.
  • the method further includes taking a second snapshot of the data storage of the database at a second subsequent time.
  • the method further includes capturing a second state of the log corresponding to the second snapshot of the database.
  • the second state of the log includes all log records occurring after the time of the first snapshot of the database to the time of the second snapshot of the database.
  • the method further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in data storage to the database, applying the captured first state of the log corresponding to the first snapshot of the log to the database and applying a portion of the second state of the log to perform a point in time recovery between the first time and the second time.
  • Another embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database.
  • the system includes a database.
  • the database includes data storage for storing data items and log storage for storing log records.
  • the system further includes one or more processors and one or more computer readable media.
  • the one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause a method to be performed.
  • the method includes taking a first snapshot of a database at a first time.
  • the first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage.
  • the log comprises an enumeration of operations on the database.
  • the method further includes taking a second snapshot of the database at a second subsequent time.
  • the second snapshot of the database includes a second snapshot of the data in data storage of the database and a second snapshot of the log records in the log storage.
  • the second snapshot of the log records in the log storage is a snapshot of all log records after the time of the first snapshot of the database to the time of the second snapshot of the database.
  • the method further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database to perform a point in time recovery between the first time and the second subsequent time.
  • FIG. 1 Another embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database.
  • the system includes a database.
  • the database includes data storage for storing data items and log storage for storing log records.
  • the system further includes one or more processors and one or more computer readable media.
  • the one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause a method to be performed.
  • the method includes taking a first snapshot of a database at a first time.
  • the first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage.
  • the log comprises an enumeration of operations on the database.
  • the method further includes taking one or more additional snapshots of the database at one or more times respectively subsequent to the first time.
  • the one or more additional snapshots of the database include additional snapshots of the data storage in the database and one or more additional snapshots of the log storage respectively.
  • the corresponding snapshot of the log storage is a snapshot of all log records occurring after the time of the additional snapshot of the database to the time of a most recent previous snapshot of the database.
  • the method further includes restoring the database to a particular point between a last occurring subsequent snapshot of the database and a most recent snapshot of the database occurring prior to the last occurring subsequent snapshot of the database by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying and log records from the one or more additional snapshots of the log storage to the database to perform a point in time recovery.
  • Figure 1 A illustrates a database and a first snapshot of the database
  • Figure IB illustrates the database and a second snapshot of the database
  • Figure 1C illustrates the database and a third snapshot of the database
  • Figure 2A illustrates the state of a database at a first time during a restore process
  • Figure 2B illustrates the state of a database at a second time during the restore process
  • Figure 2C illustrates the state of a database at a third time during the restore process
  • Figure 3 illustrates a method of archiving and restoring a database
  • Figure 4 illustrates another method of archiving and restoring a database
  • Figure 5 illustrates another method of archiving and restoring a database.
  • Some embodiments herein use a snapshot infrastructure to eliminate data movement during a backup stage, but enable the user to restore to an arbitrary point in time between two adjacent snapshots, without requiring streaming transaction log backups. This can be accomplished by laying down the database files from a first snapshot in sequence, and then using only the active transaction log data from a second snapshot to roll the newly restored database forward in time to the point that the user desires.
  • the transaction log for each snapshot is an enumeration of operations performed on the database from the most recent snapshot to the current snapshot which includes the snapshot of the transaction log.
  • Snapshots of the database can be created periodically using the snapshot infrastructure provided by the storage. The snapshot will require no data movement but just some metadata updates in the storage layer. The snapshots are treated as the backups of the database.
  • two consecutive snapshots (a first snapshot and a second snapshot) enclosing the time can be first identified. Then both the data and log records from the first snapshot can be copied to become the files of the database to be restored.
  • the database can start recovery by applying the log records of the first snapshot to update the data which has not yet been written to the data file. After applying the last log record from the first snapshot, the recovery is paused. After that, only the log portion from the second snapshot is copied to the restoring database's log storage. The snapshot portion of the data from the second snapshot is discarded.
  • Recovery can identify where it stopped in the log previously from the first snapshot and resume to scan the new log records from the second snapshot and start applying them one by one until it reaches the log record that has passed the time a user has identified as the stop time.
  • the remaining log records from the second snapshot can be wiped out by zeroing their portion in the file.
  • the database can be fully recovered by carrying out an undo phase.
  • the database system includes a database 102.
  • the database 102 includes data storage 104 and log storage 106.
  • the data storage 104 includes the data structure and values that make up the database. In this current example, a single row of data records are shown, but it should be appreciated that the data storage 104 may represent one or more tables or other complex database structures.
  • the database 102 is illustrated in a way that would appear to be a single entity at a single location, the database 102 is often distributed across storage devices and often times across different machines in different locations. That is, the database 102 may be a distributed database with different portions of the database residing in different locations. Often, such databases are implemented in a cloud environment where the different portions of the database are hosted by different virtual machines in the cloud environment.
  • a database will often include several different versions of a data item to allow the database to be rolled back as a result of transaction failures or for other reasons that may cause a versioned database to be useful.
  • the data storage 104 includes a data item G at location D 7 in the data storage 104.
  • the data storage 104 also includes a data item G', that is a new version of data item G, at location Ds of the data storage 104.
  • the log storage 106 memorializes this change. For example, at location Li of the log storage 106, the operation change G to G' is memorialized.
  • the log storage 106 stores a list of operations performed on the data storage 104.
  • the log storage 106 is a circular ring buffer with n records (i.e. from location Li to location L n ). Note that the size may be dynamic if there is a need to grow the size of the log storage 106 to ensure that records are not lost before they are snapshotted as will be explained in more detail below. Due to the ring buffer nature of the log storage, operations will be memorialized in log storage 106. Once an operation has been snapshotted, the location of that record will be marked as overwritable such that new records can be written into that location. Thus, for example, log records may be made into locations Li, L2, and L3 of the log storage. These may be snapshotted as part of a snapshot operation for the database 102, as will be illustrated below.
  • the log storage 106 can be expanded to accommodate the additional log records. However, it is preferable that the log storage 106 be of a somewhat limited size and not expand. This can be achieved by adjusting the frequency or time of snapshots as will be illustrated below.
  • the database 102 also includes a mapping structure 107.
  • the mapping structure 107 contains a set of pointers to storage locations.
  • the mapping structure 107 represents the state of the data in the database at that time. In particular, the mapping structure 107 will point to the storage location, and thus the data, that is current in the database 102.
  • the database 102 can be backed up by creating snapshots of the database.
  • the snapshots of the database 102 do not store the actual data from the data storage 104, but rather store pointers to records in the data storage 104.
  • a data portion of a snapshot will be a snapshot at a particular time of the mapping structure 107 at that time.
  • the snapshots can also store log operations from the log storage 106. Once log operations from the log storage 106 have been snapshotted, then the storage locations for those snapshotted operations can be marked as free or overwritable.
  • Figures 1A, IB and IB illustrate a set of three snapshots 108-1, 108-2 and 108- 3.
  • the three snapshots represent a sequence of adjacent (in time) snapshots (with snapshot 108-1 being first in time, snapshot 108-2 being second in time, and snapshot 108-3 being third in time), meaning that there are no additional snapshots intervening between any of the three snapshots.
  • the snapshots do not include data from the data storage 104, but rather include pointers to storage locations in the data storage 104.
  • snapshot 108-1 includes a data portion 110-1 with pointers to locations Di, D2, D3, D 4 , D5, D 6 and D7.
  • Snapshot 108-1 also includes a log portion 112-1. However, the log portion 112-1 is not shown with any records as, either there are none, or while they may exist in actual embodiments, and that existence is significant, the particular values in those recorded values are not needed for the present illustration.
  • the snapshot 108-2 in Figure IB is taken after changes are made to the data storage 104 and records are added to the log storage 106.
  • data item G at data storage location D 7 is changed to a new version G' stored at storage location Ds.
  • data item B at storage location D 2 is changed to a new version B' at data storage location Ds>.
  • the snapshot 108-2 includes a new mapping with mapping to locations Ds and D instead of the mappings to locations D 7 and D 2 respectively.
  • the snapshot 108-2 includes a data portion 110-2 with the new mapping, and a log portion 112-1 with the new log records.
  • the log storage 106 is updated at locations Li and L 2 respectively to memorialize the operations that caused these changes. While simply shown as a change from G->G' or from B->B', it should be appreciated that the log can memorialize details, such as what operation is performed. For example, the actual log record may indicate writing G' to a particular database table location.
  • the log records at locations Li and L 2 are snapshotted as part of the snapshot 108-2. Once the log records have been snapshotted, the log storage locations Li and L 2 can be marked as free or overwritable.
  • the snapshot 108-3 in Figure 1C is taken after additional changes are made to the data storage 104 and additional records are added to the log storage 106.
  • data item C is updated to a new version C
  • data item E is updated to a new version E'.
  • the log portion 112-3 of the snapshot 108-3 includes the log records from location L3 and L 4 of the log storage 106.
  • those locations i.e. L3 and L 4
  • the database can be recovered to any point in time after the time of the first snapshot 108-1 to the time of the third snapshot 108-3.
  • FIG. 2A, 2B and 2C An example of database recovery is illustrated in Figures 2A, 2B and 2C.
  • the database 102 is recovered at a point between the second snapshot 108-2 and the third snapshot 108-3.
  • the database is to be restored to the point in time after data item C is updated to C.
  • Figure 2A illustrates the database 102, including the data storage 104 and the log storage 106 at an initial time.
  • the second snapshot 108-2 and third snapshot 108-3 are identified.
  • the second snapshot 108- 2 including the snapshot of the log included in the log portion 112-2 is applied to the database 102.
  • this causes the records from the data portion 110-2 of the snapshot 108-2 to be applied to the mapping structure 107 and the records from the log portion 112-2 of the snapshot 108-2 to be applied to the log storage 106.
  • a portion of the log portion 112-3 from the third snapshot 108-3 is applied to the log storage 106 of the database 102 as illustrated in Figure 2C.
  • all records in the log portion 112-3 up to and including the operation that updates C to C are applied to the log storage 106.
  • the database is thereby restored to the point in time when data item C was updated to version C ' .
  • the log records in log storage in Figure 2C are in the same storage locations (i.e. Li, L 2 , and L 3 ) as those in Figure 1, this is purely coincidental.
  • the log records could be restored to any appropriate location in the ring buffer of the log storage 106 that are available for restoring the log records.
  • the log storage 106 can be treated as if all entries are invalid, and the log records can be restored as if the log storage 106 had all storage locations available for writing.
  • the log records from the second snapshot 108-2 are applied to the log storage 106.
  • those records would not need to be restored.
  • all changes to the data in the database were made durable (i.e. all transactions are committed or rolled back) prior to the second snapshot 108-2, there may be no need for the log records memorializing the changes from G to G' and from B to B' as they would not be needed to roll back any outstanding transactions.
  • all that would be needed to restore the database 102 is the data portion 110-2 of the second snapshot 108-2 and the log portion 112-3 of the third snapshot 108-3.
  • a database may be restored by using a single data portion obtained from one snapshot and several different log portions obtained from corresponding snapshots.
  • the examples illustrated above illustrate snapshots which include both the data portion and log portion.
  • the log portion of a snapshot (or a log snapshot corresponding to a data snapshot) generally only includes a memorialization of operations after the most recent previous snapshot of the data to the snapshot to which the log portion belongs.
  • the log portion will not include log records occurring before the most recent previous snapshot or log records occurring after the current snapshot.
  • the log portion 112-2 will typically only include log records occurring after the snapshot 108-1 up to and including the time of the snapshot 108-2.
  • the log portion will include log records occurring before the most recent previous snapshot and/or log records occurring after the current snapshot
  • the method 300 includes acts for archiving and restoring a database.
  • the method 300 includes taking a first snapshot of the data storage of the database at a first time (act 302).
  • the method 300 further includes capturing a first state of the log storage corresponding to the first snapshot of the data storage of the database (act 304).
  • the log storage comprises an enumeration of operations on the data storage of the database.
  • Figure 1A illustrates a snapshot 108-2 taken at a first time.
  • the snapshot 108-2 includes a data portion 110-2 and a log portion 112-2.
  • the method 300 further includes taking a second snapshot of the data storage of the database at a second subsequent time (act 306).
  • the method 300 further includes capturing a second state of the log corresponding to the second snapshot of the database (act 308).
  • the second state of the log includes all log records occurring after the time of the first snapshot of the database to the time of the second snapshot.
  • Figure IB illustrates taking a second snapshot 108-3 with a data portion 110-3 and a log portion 112-3.
  • the log portion includes a memorialization of the log records at location L3 and L 4 . These records were created after the first snapshot 108-2.
  • the method 300 further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in data storage to the database, applying the captured first state of the log corresponding to the first snapshot of the log to the database and applying a portion of the second state of the log to perform a point in time recovery between the first time and the second time (act 310).
  • the data portion 110-2 and the log portion 112-2 can be applied to the database 102 (as illustrated in Figure 2B), and then a portion of the log portion 112-3 can be applied as illustrated in Figure 2C to achieve a point in time recovery.
  • the method 300 may be practiced where taking a second snapshot of the data storage of the database and capturing the second state of the log corresponding to the second snapshot of the databased is performed in a unified snapshot of the database operation.
  • the snapshot 108-3 may be taken as a single snapshot or set of snapshot operations to capture both the data portion 110-2 and the log portion 112-2.
  • Some embodiments may be practiced in a system that includes a data mapping structure (such as the data mapping structure 107).
  • taking snapshots of the data storage may include capturing pointers in the data mapping structure pointing to locations in the data storage.
  • the snapshots illustrated in Figures 1A-1C illustrate such snapshots.
  • the method 300 may be practiced where capturing a state of the log storage comprises capturing one or more representations of data operations performed on data items in the data storage.
  • the log portion may indicate what operations were performed on particular data items.
  • Some embodiments may be practiced in a system that is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
  • the database is a versioned database storing different versions of data items.
  • the database contains both old versions and news versions of data items G, B C and E.
  • the method 300 may further includes causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured when capturing a state of the log storage corresponding to a snapshot.
  • the method 400 includes taking a first snapshot of a database at a first time (act 402).
  • the first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage.
  • the log storage comprises an enumeration of operations on the database;
  • the method 400 further includes taking a second snapshot of the database at a second subsequent time (act 404).
  • the second snapshot of the database includes a second snapshot of the data in data storage of the database and a second snapshot of the log records in the log storage.
  • the second snapshot of the log records in the log storage is a snapshot of all log records after the time of the first snapshot of the database to the time of the second snapshot of the database.
  • the method 400 further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database to perform a point in time recovery between the first time and the second subsequent time.
  • An example is illustrated in Figures 2A-2C discussed above.
  • the method may be practiced in a system comprising a data mapping structure.
  • taking snapshots of the database comprises capturing pointers in the data mapping structure pointing to locations in the data storage.
  • the method may be practiced in a system where the log records in the log storage comprise one or more representations of data operations performed on data items in the data storage.
  • the method may be practiced in a system where the database is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
  • the method may be practiced in a system where the database is a versioned database storing different versions of data items.
  • the method may be practiced in a system where the log storage comprises a ring buffer.
  • the method 400 may further includes causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured during a snapshot.
  • the method 500 includes taking a first snapshot of a database at a first time (act 502).
  • the first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage.
  • the log storage comprises an enumeration of operations on the database;
  • the method 500 further includes taking one or more additional snapshots of the database at one or more times respectively subsequent to the first time (act 504).
  • the one or more additional snapshots of the database include one or more additional snapshots of the data storage in the database and one or more additional snapshots of the log storage respectively.
  • the corresponding snapshot of the log storage is a snapshot of all log records occurring after the time of the additional snapshot of the database to the most recent time of a previous snapshot of the database.
  • the method 500 further includes restoring the database to a particular point between a last occurring subsequent snapshot of the database and a most recent snapshot of the database occurring prior to the last occurring subsequent snapshot of the database by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying and log records from the one or more additional snapshots of the log storage to the database to perform a point in time recovery.
  • the snapshot 108-1 including the data portion 110-1 and the log portion 112-1 could be applied to the database (such as by applying the data portion 110-1 to the mapping structure 107 and the log portion 112-1 to the log storage 106.
  • the log portion 112-2 of the second snapshot 108-2 could also be applied to the log storage 106.
  • a portion of the log portion 112-3 of the third snapshot 108-3 could be applied to the log storage 106 to perform the point in time recovery.
  • the method may be practiced in a system comprising a data mapping structure.
  • taking snapshots of the database includes capturing pointers in the data mapping structure pointing to locations in the data storage.
  • the method may be practiced in a system where the log records in the log storage comprise one or more representations of data operations performed on data items in the data storage.
  • the method may be practiced in a system where the database is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
  • the method may be practiced in a system where the database is a versioned database storing different versions of data items.
  • the method may be practiced in a system where the log storage comprises a ring buffer.
  • the method 500 may further include causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured during a snapshot.
  • the methods may be practiced by a computer system including one or more processors and computer readable media such as computer memory.
  • the computer memory may store computer executable instructions that when executed by one or more processors cause various functions to be performed, such as the acts recited in the embodiments.
  • Embodiments of the present invention may comprise or utilize a special purpose or general-purpose computer including computer hardware, as discussed in greater detail below.
  • Embodiments within the scope of the present invention also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
  • Computer-readable media that store computer-executable instructions are physical storage media.
  • Computer-readable media that carry computer-executable instructions are transmission media.
  • embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: physical computer readable storage media and transmission computer readable media.
  • Physical computer readable storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage (such as CDs, DVDs, etc), magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
  • a "network" is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium.
  • Transmissions media can include a network and/or data links which can be used to carry or desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above are also included within the scope of computer-readable media.
  • program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission computer readable media to physical computer readable storage media (or vice versa).
  • computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer readable physical storage media at a computer system.
  • a network interface module e.g., a "NIC”
  • NIC network interface module
  • computer readable physical storage media can be included in computer system components that also (or even primarily) utilize transmission media.
  • Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
  • the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
  • the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like.
  • the invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks.
  • program modules may be located in both local and remote memory storage devices.
  • the functionally described herein can be performed, at least in part, by one or more hardware logic components.
  • illustrative types of hardware logic components include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

Abstract

Archiving a database and point in time recovery of the database. A method includes taking a first snapshot of a database. The first snapshot of the database includes a first snapshot of the data in the data storage and a first snapshot of the log records in the log storage. The method further includes taking a second snapshot of the database. The second snapshot of the database includes a second snapshot of the data in data storage and a second snapshot of the log records. The method further includes restoring the database to a particular point by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database.

Description

POINT IN TIME DATABASE RESTORE FROM STORAGE SNAPSHOTS
BACKGROUND
Background and Relevant Art
[0001] Backups of very large databases have limitations in that they require a large movement of data from the database files to backup media. In a cloud environment, that may mean moving data from cloud storage to a virtual machine and back to cloud storage, crossing expensive boundaries. Storage system snapshots have helped this by providing a metadata-only mechanism to achieve an image of the storage at that point in time. However, this has had the disadvantage that such backups cannot restore the database to an arbitrary point in time between snapshot backups. Rather, the backup is only restored to the point of the snapshot, and any changes to the database after the backup are lost.
[0002] Other solutions have relied on streaming backups, which suffer from the data movement problem, or they rely completely on snapshots, which give the ability to restore only to the discrete times when the snapshot is taken.
[0003] The subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one exemplary technology area where some embodiments described herein may be practiced.
BRIEF SUMMARY
[0004] One embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database. The system includes a database. The database includes data storage for storing data items and log storage for storing log records. The system further includes one or more processors and one or more computer readable media. The one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform various actions of a method. The method includes taking a first snapshot of the data storage of the database at a first time. The method further includes capturing a first state of the log storage corresponding to the first snapshot of the data storage of the database. The log storage comprises an enumeration of operations on the data storage of the database. The method further includes taking a second snapshot of the data storage of the database at a second subsequent time. The method further includes capturing a second state of the log corresponding to the second snapshot of the database. The second state of the log includes all log records occurring after the time of the first snapshot of the database to the time of the second snapshot of the database. The method further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in data storage to the database, applying the captured first state of the log corresponding to the first snapshot of the log to the database and applying a portion of the second state of the log to perform a point in time recovery between the first time and the second time.
[0005] Another embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database. The system includes a database. The database includes data storage for storing data items and log storage for storing log records. The system further includes one or more processors and one or more computer readable media. The one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause a method to be performed. The method includes taking a first snapshot of a database at a first time. The first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage. The log comprises an enumeration of operations on the database. The method further includes taking a second snapshot of the database at a second subsequent time. The second snapshot of the database includes a second snapshot of the data in data storage of the database and a second snapshot of the log records in the log storage. The second snapshot of the log records in the log storage is a snapshot of all log records after the time of the first snapshot of the database to the time of the second snapshot of the database. The method further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database to perform a point in time recovery between the first time and the second subsequent time.
[0006] Another embodiment illustrated herein includes a system for archiving a database to allow for point in time recovery of the database. The system includes a database. The database includes data storage for storing data items and log storage for storing log records. The system further includes one or more processors and one or more computer readable media. The one or more computer readable media include computer executable instructions that when executed by at least one of the one or more processors cause a method to be performed. The method includes taking a first snapshot of a database at a first time. The first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage. The log comprises an enumeration of operations on the database. The method further includes taking one or more additional snapshots of the database at one or more times respectively subsequent to the first time. The one or more additional snapshots of the database include additional snapshots of the data storage in the database and one or more additional snapshots of the log storage respectively. For each additional snapshot of the data storage in the database, the corresponding snapshot of the log storage is a snapshot of all log records occurring after the time of the additional snapshot of the database to the time of a most recent previous snapshot of the database. The method further includes restoring the database to a particular point between a last occurring subsequent snapshot of the database and a most recent snapshot of the database occurring prior to the last occurring subsequent snapshot of the database by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying and log records from the one or more additional snapshots of the log storage to the database to perform a point in time recovery.
[0007] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
[0008] Additional features and advantages will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the teachings herein. Features and advantages of the invention may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. Features of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] In order to describe the manner in which the above-recited and other advantages and features can be obtained, a more particular description of the subject matter briefly described above will be rendered by reference to specific embodiments which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments and are not therefore to be considered to be limiting in scope, embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
[0010] Figure 1 A illustrates a database and a first snapshot of the database;
[0011] Figure IB illustrates the database and a second snapshot of the database;
[0012] Figure 1C illustrates the database and a third snapshot of the database;
[0013] Figure 2A illustrates the state of a database at a first time during a restore process;
[0014] Figure 2B illustrates the state of a database at a second time during the restore process;
[0015] Figure 2C illustrates the state of a database at a third time during the restore process;
[0016] Figure 3 illustrates a method of archiving and restoring a database;
[0017] Figure 4 illustrates another method of archiving and restoring a database; and
[0018] Figure 5 illustrates another method of archiving and restoring a database.
DETAILED DESCRIPTION
[0019] Some embodiments herein use a snapshot infrastructure to eliminate data movement during a backup stage, but enable the user to restore to an arbitrary point in time between two adjacent snapshots, without requiring streaming transaction log backups. This can be accomplished by laying down the database files from a first snapshot in sequence, and then using only the active transaction log data from a second snapshot to roll the newly restored database forward in time to the point that the user desires. The transaction log for each snapshot is an enumeration of operations performed on the database from the most recent snapshot to the current snapshot which includes the snapshot of the transaction log.
[0020] Snapshots of the database can be created periodically using the snapshot infrastructure provided by the storage. The snapshot will require no data movement but just some metadata updates in the storage layer. The snapshots are treated as the backups of the database.
[0021] To restore to any point in time desired, two consecutive snapshots (a first snapshot and a second snapshot) enclosing the time can be first identified. Then both the data and log records from the first snapshot can be copied to become the files of the database to be restored. The database can start recovery by applying the log records of the first snapshot to update the data which has not yet been written to the data file. After applying the last log record from the first snapshot, the recovery is paused. After that, only the log portion from the second snapshot is copied to the restoring database's log storage. The snapshot portion of the data from the second snapshot is discarded. Recovery can identify where it stopped in the log previously from the first snapshot and resume to scan the new log records from the second snapshot and start applying them one by one until it reaches the log record that has passed the time a user has identified as the stop time. The remaining log records from the second snapshot can be wiped out by zeroing their portion in the file. Finally, the database can be fully recovered by carrying out an undo phase.
[0022] Referring now to Figure 1A, a database system 100 that can implement embodiments of the invention is illustrated. The database system includes a database 102. The database 102 includes data storage 104 and log storage 106. The data storage 104 includes the data structure and values that make up the database. In this current example, a single row of data records are shown, but it should be appreciated that the data storage 104 may represent one or more tables or other complex database structures.
[0023] Further, while the database 102 is illustrated in a way that would appear to be a single entity at a single location, the database 102 is often distributed across storage devices and often times across different machines in different locations. That is, the database 102 may be a distributed database with different portions of the database residing in different locations. Often, such databases are implemented in a cloud environment where the different portions of the database are hosted by different virtual machines in the cloud environment.
[0024] A database will often include several different versions of a data item to allow the database to be rolled back as a result of transaction failures or for other reasons that may cause a versioned database to be useful. For example, as illustrated in Figure IB, which shows the database 102 at a subsequent time to that of Figure 1A, the data storage 104 includes a data item G at location D7 in the data storage 104. The data storage 104 also includes a data item G', that is a new version of data item G, at location Ds of the data storage 104. The log storage 106 memorializes this change. For example, at location Li of the log storage 106, the operation change G to G' is memorialized. Thus, the log storage 106 stores a list of operations performed on the data storage 104.
[0025] The log storage 106, in the illustrated example, is a circular ring buffer with n records (i.e. from location Li to location Ln). Note that the size may be dynamic if there is a need to grow the size of the log storage 106 to ensure that records are not lost before they are snapshotted as will be explained in more detail below. Due to the ring buffer nature of the log storage, operations will be memorialized in log storage 106. Once an operation has been snapshotted, the location of that record will be marked as overwritable such that new records can be written into that location. Thus, for example, log records may be made into locations Li, L2, and L3 of the log storage. These may be snapshotted as part of a snapshot operation for the database 102, as will be illustrated below. Once they are snapshotted, they can be marked as available for new log records. As changes are made to the database 102 (and in particular the data storage 104) new records will be made to the log storage 106. Once a record is made at log storage location Ln, so long as Li has been marked as overwritable, the next log record will be made at Li overwriting the record that previously existed there.
[0026] If however, Li is not marked as overwritable, the log storage 106 can be expanded to accommodate the additional log records. However, it is preferable that the log storage 106 be of a somewhat limited size and not expand. This can be achieved by adjusting the frequency or time of snapshots as will be illustrated below.
[0027] The database 102 also includes a mapping structure 107. The mapping structure 107 contains a set of pointers to storage locations. The mapping structure 107, at any given time, represents the state of the data in the database at that time. In particular, the mapping structure 107 will point to the storage location, and thus the data, that is current in the database 102.
[0028] The database 102 can be backed up by creating snapshots of the database. The snapshots of the database 102 do not store the actual data from the data storage 104, but rather store pointers to records in the data storage 104. Thus, for example, a data portion of a snapshot will be a snapshot at a particular time of the mapping structure 107 at that time. The snapshots can also store log operations from the log storage 106. Once log operations from the log storage 106 have been snapshotted, then the storage locations for those snapshotted operations can be marked as free or overwritable.
[0029] Figures 1A, IB and IB illustrate a set of three snapshots 108-1, 108-2 and 108- 3. The three snapshots represent a sequence of adjacent (in time) snapshots (with snapshot 108-1 being first in time, snapshot 108-2 being second in time, and snapshot 108-3 being third in time), meaning that there are no additional snapshots intervening between any of the three snapshots. As illustrated, the snapshots do not include data from the data storage 104, but rather include pointers to storage locations in the data storage 104. Thus, for example, snapshot 108-1 includes a data portion 110-1 with pointers to locations Di, D2, D3, D4, D5, D6 and D7. Snapshot 108-1 also includes a log portion 112-1. However, the log portion 112-1 is not shown with any records as, either there are none, or while they may exist in actual embodiments, and that existence is significant, the particular values in those recorded values are not needed for the present illustration.
[0030] The snapshot 108-2 in Figure IB is taken after changes are made to the data storage 104 and records are added to the log storage 106. In particular, data item G at data storage location D7 is changed to a new version G' stored at storage location Ds. Also, data item B at storage location D2 is changed to a new version B' at data storage location Ds>. The snapshot 108-2 includes a new mapping with mapping to locations Ds and D instead of the mappings to locations D7 and D2 respectively. Thus, the snapshot 108-2 includes a data portion 110-2 with the new mapping, and a log portion 112-1 with the new log records.
[0031] The log storage 106 is updated at locations Li and L2 respectively to memorialize the operations that caused these changes. While simply shown as a change from G->G' or from B->B', it should be appreciated that the log can memorialize details, such as what operation is performed. For example, the actual log record may indicate writing G' to a particular database table location. The log records at locations Li and L2 are snapshotted as part of the snapshot 108-2. Once the log records have been snapshotted, the log storage locations Li and L2 can be marked as free or overwritable.
[0032] The snapshot 108-3 in Figure 1C is taken after additional changes are made to the data storage 104 and additional records are added to the log storage 106. In this example, data item C is updated to a new version C, and data item E is updated to a new version E'. This is reflected in the snapshot 108-3 with the pointers to data storage locations D10 and Dl l in the data portion 110-3 of the snapshot 108-3. The log portion 112-3 of the snapshot 108-3 includes the log records from location L3 and L4 of the log storage 106. As the locations L3 and L4 of the log storage 106 of the database 102 have been snapshotted, those locations (i.e. L3 and L4) can be marked as free or overwritable. At this point, using the snapshots 108-1 through 108-3, the database can be recovered to any point in time after the time of the first snapshot 108-1 to the time of the third snapshot 108-3.
[0033] An example of database recovery is illustrated in Figures 2A, 2B and 2C. In the example illustrated, the database 102 is recovered at a point between the second snapshot 108-2 and the third snapshot 108-3. In particular, the database is to be restored to the point in time after data item C is updated to C.
[0034] Figure 2A illustrates the database 102, including the data storage 104 and the log storage 106 at an initial time. To restore the database to the desired point in time, the second snapshot 108-2 and third snapshot 108-3 are identified. The second snapshot 108- 2, including the snapshot of the log included in the log portion 112-2 is applied to the database 102. As illustrated in Figure 2B, this causes the records from the data portion 110-2 of the snapshot 108-2 to be applied to the mapping structure 107 and the records from the log portion 112-2 of the snapshot 108-2 to be applied to the log storage 106.
[0035] Then a portion of the log portion 112-3 from the third snapshot 108-3 is applied to the log storage 106 of the database 102 as illustrated in Figure 2C. In particular, all records in the log portion 112-3 up to and including the operation that updates C to C are applied to the log storage 106. As such, the database is thereby restored to the point in time when data item C was updated to version C ' .
[0036] While the casual observer will note that in the Figures, the log records in log storage in Figure 2C are in the same storage locations (i.e. Li, L2, and L3) as those in Figure 1, this is purely coincidental. The log records could be restored to any appropriate location in the ring buffer of the log storage 106 that are available for restoring the log records. Alternatively, the log storage 106 can be treated as if all entries are invalid, and the log records can be restored as if the log storage 106 had all storage locations available for writing.
[0037] In the example illustrated in Figures 2A through 2C, at Figure 2B, the log records from the second snapshot 108-2 are applied to the log storage 106. However, it should be appreciated that in some situations, those records would not need to be restored. For example, if all changes to the data in the database were made durable (i.e. all transactions are committed or rolled back) prior to the second snapshot 108-2, there may be no need for the log records memorializing the changes from G to G' and from B to B' as they would not be needed to roll back any outstanding transactions. In this case, all that would be needed to restore the database 102 is the data portion 110-2 of the second snapshot 108-2 and the log portion 112-3 of the third snapshot 108-3.
[0038] Note that in an alternative embodiment, a database may be restored by using a single data portion obtained from one snapshot and several different log portions obtained from corresponding snapshots. For example, one could restore the database to the point in time where data item C is updated to C by first applying the data portion 110-1 of the first snapshot 108-1 to the database 102, applying the log portion 112-1 of the first snapshot 108-1 to the log storage 106 of the database 102, applying the log portion 112-2 of the second snapshot 108-2 to the log storage 106 of the database, and finally by applying a portion of the log portion 112-3 to the log storage 106 of the database 102. [0039] The examples illustrated above illustrate snapshots which include both the data portion and log portion. It should be appreciated that these can be obtained in a number of different ways. Further, some embodiments may be implemented where the data portion and the log portion of a snapshot are stored separately. Further, these portions may be obtained through different sets of operations. However even in these cases, the log portion of a snapshot (or a log snapshot corresponding to a data snapshot) generally only includes a memorialization of operations after the most recent previous snapshot of the data to the snapshot to which the log portion belongs. Thus, in most embodiments, the log portion will not include log records occurring before the most recent previous snapshot or log records occurring after the current snapshot. Thus, for example, the log portion 112-2 will typically only include log records occurring after the snapshot 108-1 up to and including the time of the snapshot 108-2. However, in other embodiments, the log portion will include log records occurring before the most recent previous snapshot and/or log records occurring after the current snapshot
[0040] The following discussion now refers to a number of methods and method acts that may be performed. Although the method acts may be discussed in a certain order or illustrated in a flow chart as occurring in a particular order, no particular ordering is required unless specifically stated, or required because an act is dependent on another act being completed prior to the act being performed.
[0041] Referring now to Figure 3, a method 300 is illustrated. The method 300 includes acts for archiving and restoring a database. The method 300 includes taking a first snapshot of the data storage of the database at a first time (act 302). The method 300 further includes capturing a first state of the log storage corresponding to the first snapshot of the data storage of the database (act 304). The log storage comprises an enumeration of operations on the data storage of the database. For example, Figure 1A illustrates a snapshot 108-2 taken at a first time. The snapshot 108-2 includes a data portion 110-2 and a log portion 112-2.
[0042] The method 300 further includes taking a second snapshot of the data storage of the database at a second subsequent time (act 306). The method 300 further includes capturing a second state of the log corresponding to the second snapshot of the database (act 308). The second state of the log includes all log records occurring after the time of the first snapshot of the database to the time of the second snapshot. For example, Figure IB illustrates taking a second snapshot 108-3 with a data portion 110-3 and a log portion 112-3. The log portion includes a memorialization of the log records at location L3 and L4. These records were created after the first snapshot 108-2.
[0043] The method 300 further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in data storage to the database, applying the captured first state of the log corresponding to the first snapshot of the log to the database and applying a portion of the second state of the log to perform a point in time recovery between the first time and the second time (act 310). Thus, as illustrated in Figures 2A-2C, the data portion 110-2 and the log portion 112-2 can be applied to the database 102 (as illustrated in Figure 2B), and then a portion of the log portion 112-3 can be applied as illustrated in Figure 2C to achieve a point in time recovery.
[0044] The method 300 may be practiced where taking a second snapshot of the data storage of the database and capturing the second state of the log corresponding to the second snapshot of the databased is performed in a unified snapshot of the database operation. Thus, for example, the snapshot 108-3 may be taken as a single snapshot or set of snapshot operations to capture both the data portion 110-2 and the log portion 112-2.
[0045] Some embodiments may be practiced in a system that includes a data mapping structure (such as the data mapping structure 107). In these embodiments, taking snapshots of the data storage may include capturing pointers in the data mapping structure pointing to locations in the data storage. The snapshots illustrated in Figures 1A-1C illustrate such snapshots.
[0046] The method 300 may be practiced where capturing a state of the log storage comprises capturing one or more representations of data operations performed on data items in the data storage. Thus for example, the log portion may indicate what operations were performed on particular data items.
[0047] Some embodiments may be practiced in a system that is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
[0048] Some embodiments may be practiced in a system that where the database is a versioned database storing different versions of data items. Thus, in one example, as illustrated in Figure 1C, the database contains both old versions and news versions of data items G, B C and E.
[0049] Some embodiments may be practiced in a system where the log storage comprises a ring buffer. In such embodiments, the method 300 may further includes causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured when capturing a state of the log storage corresponding to a snapshot.
[0050] Referring now to Figure 4, another method for archiving and restoring a database is illustrated. The method may be practiced in a database environment. The method 400 includes taking a first snapshot of a database at a first time (act 402). The first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage. The log storage comprises an enumeration of operations on the database;
[0051] The method 400 further includes taking a second snapshot of the database at a second subsequent time (act 404). The second snapshot of the database includes a second snapshot of the data in data storage of the database and a second snapshot of the log records in the log storage. The second snapshot of the log records in the log storage is a snapshot of all log records after the time of the first snapshot of the database to the time of the second snapshot of the database.
[0052] The method 400 further includes restoring the database to a particular point between the first time and the second time by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database to perform a point in time recovery between the first time and the second subsequent time. An example is illustrated in Figures 2A-2C discussed above.
[0053] The method may be practiced in a system comprising a data mapping structure. In some such embodiments, taking snapshots of the database comprises capturing pointers in the data mapping structure pointing to locations in the data storage.
[0054] The method may be practiced in a system where the log records in the log storage comprise one or more representations of data operations performed on data items in the data storage.
[0055] The method may be practiced in a system where the database is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
[0056] The method may be practiced in a system where the database is a versioned database storing different versions of data items. [0057] The method may be practiced in a system where the log storage comprises a ring buffer. In some such embodiments, the method 400 may further includes causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured during a snapshot.
[0058] Referring now to Figure 5, a method of archiving and restoring a database is illustrated. The method 500 includes taking a first snapshot of a database at a first time (act 502). The first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage. The log storage comprises an enumeration of operations on the database;
[0059] The method 500 further includes taking one or more additional snapshots of the database at one or more times respectively subsequent to the first time (act 504). The one or more additional snapshots of the database include one or more additional snapshots of the data storage in the database and one or more additional snapshots of the log storage respectively. For each additional snapshot of the data storage in the database, the corresponding snapshot of the log storage is a snapshot of all log records occurring after the time of the additional snapshot of the database to the most recent time of a previous snapshot of the database.
[0060] The method 500 further includes restoring the database to a particular point between a last occurring subsequent snapshot of the database and a most recent snapshot of the database occurring prior to the last occurring subsequent snapshot of the database by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying and log records from the one or more additional snapshots of the log storage to the database to perform a point in time recovery. Thus for example, with reference to the figures, the snapshot 108-1, including the data portion 110-1 and the log portion 112-1 could be applied to the database (such as by applying the data portion 110-1 to the mapping structure 107 and the log portion 112-1 to the log storage 106. The log portion 112-2 of the second snapshot 108-2 could also be applied to the log storage 106. Then, a portion of the log portion 112-3 of the third snapshot 108-3 could be applied to the log storage 106 to perform the point in time recovery.
[0061] The method may be practiced in a system comprising a data mapping structure. In some such embodiments, taking snapshots of the database includes capturing pointers in the data mapping structure pointing to locations in the data storage. [0062] The method may be practiced in a system where the log records in the log storage comprise one or more representations of data operations performed on data items in the data storage.
[0063] The method may be practiced in a system where the database is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
[0064] The method may be practiced in a system where the database is a versioned database storing different versions of data items.
[0065] The method may be practiced in a system where the log storage comprises a ring buffer. In some such embodiments, the method 500 may further include causing storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured during a snapshot.
[0066] Further, the methods may be practiced by a computer system including one or more processors and computer readable media such as computer memory. In particular, the computer memory may store computer executable instructions that when executed by one or more processors cause various functions to be performed, such as the acts recited in the embodiments.
[0067] Embodiments of the present invention may comprise or utilize a special purpose or general-purpose computer including computer hardware, as discussed in greater detail below. Embodiments within the scope of the present invention also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are physical storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: physical computer readable storage media and transmission computer readable media.
[0068] Physical computer readable storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage (such as CDs, DVDs, etc), magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. [0069] A "network" is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links which can be used to carry or desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above are also included within the scope of computer-readable media.
[0070] Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission computer readable media to physical computer readable storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer readable physical storage media at a computer system. Thus, computer readable physical storage media can be included in computer system components that also (or even primarily) utilize transmission media.
[0071] Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
[0072] Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like. The invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.
[0073] Alternatively, or in addition, the functionally described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
[0074] The present invention may be embodied in other specific forms without departing from its spirit or characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A computing system for archiving a database to allow for point in time recovery of the database, the system comprising:
a database, wherein the database comprises:
data storage for storing data items; and
log storage for storing log records; and
one or more processors; and
one or more computer readable media, wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one or more processors cause the at least one or more processors to perform the following:
take a first snapshot of the data storage of the database at a first time;
capture a first state of the log storage corresponding to the first snapshot of the data storage of the database, wherein the log storage comprises an enumeration of operations on the data storage of the database; take a second snapshot of the data storage of the database at a second subsequent time;
capture a second state of the log corresponding to the second snapshot of the database, the second state of the log including all log records occurring after the time of the first snapshot of the database to the time of the second snapshot; and
restore the database to a particular point between the first time and the second time by applying the first snapshot of the data in data storage to the database, applying the captured first state of the log corresponding to the first snapshot of the log to the database and applying a portion of the second state of the log to perform a point in time recovery between the first time and the second time.
2. The system of claim 1, wherein taking a second snapshot of the data storage of the database and capturing the second state of the log corresponding to the second snapshot of the databased is performed in a unified snapshot of the database operation.
3. The system of claim 1, further comprising a data mapping structure, and wherein taking snapshots of the data storage comprises capturing pointers in the data mapping structure pointing to locations in the data storage.
4. The system of claim 1, wherein capturing a state of the log storage comprises capturing one or more representations of data operations performed on data items in the data storage.
5. The system of claim 1, wherein the database is a distributed database implemented in a cloud environment, such that different portions of the database are implemented on different virtual machines in the cloud environment.
6. The system of claim 1, wherein the database is a versioned database storing different versions of data items.
7. The system of claim 1, wherein the log storage comprises a ring buffer, and wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one of the one or more processors cause storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured when capturing a state of the log storage corresponding to a snapshot.
8. A computing system for archiving a database to allow for point in time recovery of the database, the system comprising:
a database, wherein the database comprises:
data storage for storing data items; and
log storage for storing log records;
one or more processors;
one or more computer readable media, wherein the one or more computer readable media comprise computer executable instructions that when executed by the one or more processors cause the one or more processors to perform the following:
take a first snapshot of a database at a first time wherein the first snapshot of the database includes a first snapshot of the data in the data storage of the database and a first snapshot of the log records in the log storage wherein the log storage comprises an enumeration of operations on the database;
take a second snapshot of the database at a second subsequent time, wherein the second snapshot of the database includes a second snapshot of the data in data storage of the database and a second snapshot of the log records in the log storage, wherein the second snapshot of the log records in the log storage is a snapshot of all log records after the time of the first snapshot of the database to the time of the second snapshot of the database; and
restore the database to a particular point between the first time and the second time by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database to perform a point in time recovery between the first time and the second subsequent time.
9. The system of claim 8, wherein the log storage comprises a ring buffer, and wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one of the one or more processors cause storage locations in the log storage to be made available, for new records, once existing records in those locations have been captured during a snapshot.
10. The system of claim 8, wherein applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database comprises applying the entire second snapshot of the log records to the log storage and zeroing out a portion of the log records from the second snapshot of the log records.
PCT/US2015/057275 2014-10-28 2015-10-26 Point in time database restore from storage snapshots WO2016069423A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201580057716.8A CN107077404B (en) 2014-10-28 2015-10-26 Recovery from a point-in-time database storing snapshots
JP2017523303A JP2017533520A (en) 2014-10-28 2015-10-26 Point-in-time restore from database storage snapshots
EP15794386.1A EP3213212B1 (en) 2014-10-28 2015-10-26 Point in time database restore from storage snapshots
RU2017114019A RU2017114019A (en) 2014-10-28 2015-10-26 RESTORE DATABASE TO STATE AT TIME FROM INSTANT STORAGE PICTURES
BR112017005834A BR112017005834A2 (en) 2014-10-28 2015-10-26 restore database timeframes from storage snapshots

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/526,137 2014-10-28
US14/526,137 US9558078B2 (en) 2014-10-28 2014-10-28 Point in time database restore from storage snapshots

Publications (1)

Publication Number Publication Date
WO2016069423A1 true WO2016069423A1 (en) 2016-05-06

Family

ID=54541193

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/057275 WO2016069423A1 (en) 2014-10-28 2015-10-26 Point in time database restore from storage snapshots

Country Status (7)

Country Link
US (1) US9558078B2 (en)
EP (1) EP3213212B1 (en)
JP (1) JP2017533520A (en)
CN (1) CN107077404B (en)
BR (1) BR112017005834A2 (en)
RU (1) RU2017114019A (en)
WO (1) WO2016069423A1 (en)

Families Citing this family (95)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8332365B2 (en) 2009-03-31 2012-12-11 Amazon Technologies, Inc. Cloning and recovery of data volumes
US9736065B2 (en) 2011-06-24 2017-08-15 Cisco Technology, Inc. Level of hierarchy in MST for traffic localization and load balancing
US8908698B2 (en) 2012-01-13 2014-12-09 Cisco Technology, Inc. System and method for managing site-to-site VPNs of a cloud managed network
US9043439B2 (en) 2013-03-14 2015-05-26 Cisco Technology, Inc. Method for streaming packet captures from network access devices to a cloud server over HTTP
US9755858B2 (en) 2014-04-15 2017-09-05 Cisco Technology, Inc. Programmable infrastructure gateway for enabling hybrid cloud services in a network environment
US9473365B2 (en) 2014-05-08 2016-10-18 Cisco Technology, Inc. Collaborative inter-service scheduling of logical resources in cloud platforms
US9785510B1 (en) 2014-05-09 2017-10-10 Amazon Technologies, Inc. Variable data replication for storage implementing data backup
US10122605B2 (en) 2014-07-09 2018-11-06 Cisco Technology, Inc Annotation of network activity through different phases of execution
US9734021B1 (en) 2014-08-18 2017-08-15 Amazon Technologies, Inc. Visualizing restoration operation granularity for a database
US9825878B2 (en) 2014-09-26 2017-11-21 Cisco Technology, Inc. Distributed application framework for prioritizing network traffic using application priority awareness
US10050862B2 (en) 2015-02-09 2018-08-14 Cisco Technology, Inc. Distributed application framework that uses network and application awareness for placing data
US10037617B2 (en) 2015-02-27 2018-07-31 Cisco Technology, Inc. Enhanced user interface systems including dynamic context selection for cloud-based networks
US10708342B2 (en) 2015-02-27 2020-07-07 Cisco Technology, Inc. Dynamic troubleshooting workspaces for cloud and network management systems
US10657004B1 (en) * 2015-03-23 2020-05-19 Amazon Technologies, Inc. Single-tenant recovery with a multi-tenant archive
US10382534B1 (en) 2015-04-04 2019-08-13 Cisco Technology, Inc. Selective load balancing of network traffic
EP3089051B1 (en) * 2015-04-28 2018-04-11 Micro Systemation AB Database rollback using wal
US10476982B2 (en) 2015-05-15 2019-11-12 Cisco Technology, Inc. Multi-datacenter message queue
US10034201B2 (en) 2015-07-09 2018-07-24 Cisco Technology, Inc. Stateless load-balancing across multiple tunnels
US10067780B2 (en) 2015-10-06 2018-09-04 Cisco Technology, Inc. Performance-based public cloud selection for a hybrid cloud environment
US11005682B2 (en) 2015-10-06 2021-05-11 Cisco Technology, Inc. Policy-driven switch overlay bypass in a hybrid cloud network environment
US10462136B2 (en) 2015-10-13 2019-10-29 Cisco Technology, Inc. Hybrid cloud security groups
US10523657B2 (en) 2015-11-16 2019-12-31 Cisco Technology, Inc. Endpoint privacy preservation with cloud conferencing
US10205677B2 (en) 2015-11-24 2019-02-12 Cisco Technology, Inc. Cloud resource placement optimization and migration execution in federated clouds
US10084703B2 (en) 2015-12-04 2018-09-25 Cisco Technology, Inc. Infrastructure-exclusive service forwarding
US10423493B1 (en) 2015-12-21 2019-09-24 Amazon Technologies, Inc. Scalable log-based continuous data protection for distributed databases
US10567500B1 (en) 2015-12-21 2020-02-18 Amazon Technologies, Inc. Continuous backup of data in a distributed data store
US10367914B2 (en) 2016-01-12 2019-07-30 Cisco Technology, Inc. Attaching service level agreements to application containers and enabling service assurance
US10831706B2 (en) * 2016-02-16 2020-11-10 International Business Machines Corporation Database maintenance using backup and restore technology
US10129177B2 (en) 2016-05-23 2018-11-13 Cisco Technology, Inc. Inter-cloud broker for hybrid cloud networks
US10659283B2 (en) 2016-07-08 2020-05-19 Cisco Technology, Inc. Reducing ARP/ND flooding in cloud environment
US10432532B2 (en) 2016-07-12 2019-10-01 Cisco Technology, Inc. Dynamically pinning micro-service to uplink port
US10382597B2 (en) 2016-07-20 2019-08-13 Cisco Technology, Inc. System and method for transport-layer level identification and isolation of container traffic
US10263898B2 (en) 2016-07-20 2019-04-16 Cisco Technology, Inc. System and method for implementing universal cloud classification (UCC) as a service (UCCaaS)
US10142346B2 (en) 2016-07-28 2018-11-27 Cisco Technology, Inc. Extension of a private cloud end-point group to a public cloud
US10567344B2 (en) 2016-08-23 2020-02-18 Cisco Technology, Inc. Automatic firewall configuration based on aggregated cloud managed information
US10698615B2 (en) 2016-08-31 2020-06-30 International Business Machines Corporation Trigger event detection for automatic log collection in an automated data storage library
US10223192B2 (en) 2016-08-31 2019-03-05 International Business Machines Corporation Automated data storage library snapshot for host detected errors
US10114708B2 (en) * 2016-08-31 2018-10-30 International Business Machines Corporation Automatic log collection for an automated data storage library
US10523592B2 (en) 2016-10-10 2019-12-31 Cisco Technology, Inc. Orchestration system for migrating user data and services based on user information
US11044162B2 (en) 2016-12-06 2021-06-22 Cisco Technology, Inc. Orchestration of cloud and fog interactions
US10326817B2 (en) 2016-12-20 2019-06-18 Cisco Technology, Inc. System and method for quality-aware recording in large scale collaborate clouds
US10334029B2 (en) 2017-01-10 2019-06-25 Cisco Technology, Inc. Forming neighborhood groups from disperse cloud providers
US10552191B2 (en) 2017-01-26 2020-02-04 Cisco Technology, Inc. Distributed hybrid cloud orchestration model
US10320683B2 (en) 2017-01-30 2019-06-11 Cisco Technology, Inc. Reliable load-balancer using segment routing and real-time application monitoring
US10671571B2 (en) 2017-01-31 2020-06-02 Cisco Technology, Inc. Fast network performance in containerized environments for network function virtualization
US11005731B2 (en) 2017-04-05 2021-05-11 Cisco Technology, Inc. Estimating model parameters for automatic deployment of scalable micro services
US10922287B2 (en) 2017-05-24 2021-02-16 Cisco Technology, Inc. Intelligent layout of composite data structures in tiered storage
US11442669B1 (en) 2018-03-15 2022-09-13 Pure Storage, Inc. Orchestrating a virtual storage system
US10382274B2 (en) 2017-06-26 2019-08-13 Cisco Technology, Inc. System and method for wide area zero-configuration network auto configuration
US10439877B2 (en) 2017-06-26 2019-10-08 Cisco Technology, Inc. Systems and methods for enabling wide area multicast domain name system
US10592353B2 (en) * 2017-06-27 2020-03-17 Salesforce.Com, Inc. Systems and methods of restoring a dataset of a database for a point in time
US10892940B2 (en) 2017-07-21 2021-01-12 Cisco Technology, Inc. Scalable statistics and analytics mechanisms in cloud networking
US10425288B2 (en) 2017-07-21 2019-09-24 Cisco Technology, Inc. Container telemetry in data center environments with blade servers and switches
US10601693B2 (en) 2017-07-24 2020-03-24 Cisco Technology, Inc. System and method for providing scalable flow monitoring in a data center fabric
US10541866B2 (en) 2017-07-25 2020-01-21 Cisco Technology, Inc. Detecting and resolving multicast traffic performance issues
US10990581B1 (en) 2017-09-27 2021-04-27 Amazon Technologies, Inc. Tracking a size of a database change log
US10754844B1 (en) 2017-09-27 2020-08-25 Amazon Technologies, Inc. Efficient database snapshot generation
EP3692442A4 (en) * 2017-10-03 2020-11-25 Rubrik, Inc. Partial database restoration
US10545823B2 (en) 2017-10-13 2020-01-28 Cisco Technology, Inc. Accelerating erasure code replication in distributed systems
US10353800B2 (en) 2017-10-18 2019-07-16 Cisco Technology, Inc. System and method for graph based monitoring and management of distributed systems
US10915516B2 (en) 2017-10-18 2021-02-09 Cisco Technology, Inc. Efficient trickle updates in large databases using persistent memory
US11182372B1 (en) 2017-11-08 2021-11-23 Amazon Technologies, Inc. Tracking database partition change log dependencies
US11481362B2 (en) 2017-11-13 2022-10-25 Cisco Technology, Inc. Using persistent memory to enable restartability of bulk load transactions in cloud databases
US11269731B1 (en) 2017-11-22 2022-03-08 Amazon Technologies, Inc. Continuous data protection
US11042503B1 (en) 2017-11-22 2021-06-22 Amazon Technologies, Inc. Continuous data protection and restoration
US10795777B1 (en) 2017-11-22 2020-10-06 Amazon Technologies, Inc. Continuous verified backups
US10691671B2 (en) 2017-12-21 2020-06-23 Cisco Technology, Inc. Using persistent memory to enable consistent data for batch processing and streaming processing
US10705882B2 (en) 2017-12-21 2020-07-07 Cisco Technology, Inc. System and method for resource placement across clouds for data intensive workloads
US11595474B2 (en) 2017-12-28 2023-02-28 Cisco Technology, Inc. Accelerating data replication using multicast and non-volatile memory enabled nodes
US10621049B1 (en) 2018-03-12 2020-04-14 Amazon Technologies, Inc. Consistent backups based on local node clock
CN111226200B (en) 2018-03-23 2023-06-27 华为云计算技术有限公司 Method, device and distributed system for creating consistent snapshot for distributed application
US10511534B2 (en) 2018-04-06 2019-12-17 Cisco Technology, Inc. Stateless distributed load-balancing
US10728361B2 (en) 2018-05-29 2020-07-28 Cisco Technology, Inc. System for association of customer information across subscribers
CN108958971A (en) * 2018-06-14 2018-12-07 北京小米移动软件有限公司 Information backup method, device and equipment
US10904322B2 (en) 2018-06-15 2021-01-26 Cisco Technology, Inc. Systems and methods for scaling down cloud-based servers handling secure connections
US10764266B2 (en) 2018-06-19 2020-09-01 Cisco Technology, Inc. Distributed authentication and authorization for rapid scaling of containerized services
US11019083B2 (en) 2018-06-20 2021-05-25 Cisco Technology, Inc. System for coordinating distributed website analysis
US10819571B2 (en) 2018-06-29 2020-10-27 Cisco Technology, Inc. Network traffic optimization using in-situ notification system
CN108958888A (en) * 2018-07-04 2018-12-07 联想(北京)有限公司 The data processing method and processing system of electronic equipment
US10678699B2 (en) 2018-07-26 2020-06-09 Cisco Technology, Inc. Cascading pre-filter to improve caching efficiency
US10904342B2 (en) 2018-07-30 2021-01-26 Cisco Technology, Inc. Container networking using communication tunnels
US11126505B1 (en) 2018-08-10 2021-09-21 Amazon Technologies, Inc. Past-state backup generator and interface for database systems
US10802926B2 (en) * 2018-09-21 2020-10-13 Microsoft Technology Licensing, Llc Accessing prior storage segment server state
US10963353B2 (en) * 2018-10-23 2021-03-30 Capital One Services, Llc Systems and methods for cross-regional back up of distributed databases on a cloud service
US11042454B1 (en) 2018-11-20 2021-06-22 Amazon Technologies, Inc. Restoration of a data source
CN110362429B (en) * 2019-07-12 2021-08-06 优刻得科技股份有限公司 Continuous data protection method, system, device and medium for database
US11609828B2 (en) 2020-01-30 2023-03-21 Rubrik, Inc. Utilizing a tablespace to export to a native database recovery environment
US11604761B2 (en) 2020-01-30 2023-03-14 Rubrik, Inc. Utilizing a tablespace to export from a foreign database recovery environment
US11360860B2 (en) 2020-01-30 2022-06-14 Rubrik, Inc. Exporting a database from a foreign database recovery environment
US11467925B2 (en) 2020-01-30 2022-10-11 Rubrik, Inc. Exporting a database to a native database recovery environment
US11704035B2 (en) 2020-03-30 2023-07-18 Pure Storage, Inc. Unified storage on block containers
US11216344B2 (en) 2020-05-13 2022-01-04 Rubrik, Inc. Real time database backup status indication and restore
CN114077517A (en) * 2020-08-13 2022-02-22 华为技术有限公司 Data processing method, equipment and system
US11507597B2 (en) 2021-03-31 2022-11-22 Pure Storage, Inc. Data replication to meet a recovery point objective
CN113360322B (en) * 2021-06-25 2023-06-13 上海上讯信息技术股份有限公司 Method and equipment for recovering data based on backup system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030158873A1 (en) * 2002-02-15 2003-08-21 International Business Machines Corporation Dynamic links to file system snapshots
US20050022213A1 (en) * 2003-07-25 2005-01-27 Hitachi, Ltd. Method and apparatus for synchronizing applications for data recovery using storage based journaling
US20070185922A1 (en) * 2006-02-07 2007-08-09 Aditya Kapoor Point-in-time database restore

Family Cites Families (311)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5175849A (en) 1988-07-28 1992-12-29 Amdahl Corporation Capturing data of a database system
JPH0664838B2 (en) 1988-09-02 1994-08-22 松下電器産業株式会社 Optical disk file device
CA1329432C (en) 1988-11-02 1994-05-10 William Davy Method of memory and cpu time allocation for a multi-user computer system
US5193162A (en) 1989-11-06 1993-03-09 Unisys Corporation Cache memory with data compaction for use in the audit trail of a data processing system having record locking capabilities
US5193181A (en) 1990-10-05 1993-03-09 Bull Hn Information Systems Inc. Recovery method and apparatus for a pipelined processing unit of a multiprocessor system
US5317731A (en) 1991-02-25 1994-05-31 International Business Machines Corporation Intelligent page store for concurrent and consistent access to a database by a transaction processor and a query processor
US5261102A (en) 1991-03-28 1993-11-09 International Business Machines Corporation System for determining direct and indirect user access privileges to data base objects
JP3160106B2 (en) 1991-12-23 2001-04-23 ヒュンダイ エレクトロニクス アメリカ How to sort disk arrays
US5446871A (en) 1993-03-23 1995-08-29 International Business Machines Corporation Method and arrangement for multi-system remote data duplexing and recovery
JP3176157B2 (en) 1992-12-28 2001-06-11 株式会社日立製作所 Disk array device and data updating method thereof
US5455946A (en) 1993-05-21 1995-10-03 International Business Machines Corporation Method and means for archiving modifiable pages in a log based transaction management system
US6604118B2 (en) 1998-07-31 2003-08-05 Network Appliance, Inc. File system image transfer
US5963962A (en) 1995-05-31 1999-10-05 Network Appliance, Inc. Write anywhere file-system layout
US5771354A (en) 1993-11-04 1998-06-23 Crawford; Christopher M. Internet online backup system provides remote storage for customers using IDs and passwords which were interactively established when signing up for backup services
US5495607A (en) 1993-11-15 1996-02-27 Conner Peripherals, Inc. Network management system having virtual catalog overview of files distributively stored across network domain
US5568639A (en) 1993-11-24 1996-10-22 Menai Corporation Method and apparatus for providing an object-oriented file structuring system on a computer
US5493649A (en) 1994-06-21 1996-02-20 Microsoft Corporation Detecting corruption in a computer program at execution time using a checksum
US5537533A (en) 1994-08-11 1996-07-16 Miralink Corporation System and method for remote mirroring of digital data from a primary network server to a remote network server
US5574906A (en) 1994-10-24 1996-11-12 International Business Machines Corporation System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
US6453325B1 (en) 1995-05-24 2002-09-17 International Business Machines Corporation Method and means for backup and restoration of a database system linked to a system for filing data
US5664148A (en) 1995-08-17 1997-09-02 Institute For The Development Of Emerging Architectures L.L.C. Cache arrangement including coalescing buffer queue for non-cacheable data
US5978813A (en) 1995-09-25 1999-11-02 International Business Machines Corporation System for providing synchronization between a local area network and a distributing computer environment
US6061769A (en) 1995-09-27 2000-05-09 International Business Machines Corporation Data set backup in a shared environment
JP3856855B2 (en) 1995-10-06 2006-12-13 三菱電機株式会社 Differential backup method
JP3477301B2 (en) 1995-12-19 2003-12-10 株式会社半導体エネルギー研究所 Active matrix type liquid crystal display device and manufacturing method thereof
US5898830A (en) 1996-10-17 1999-04-27 Network Engineering Software Firewall providing enhanced network security and user transparency
US5805785A (en) 1996-02-27 1998-09-08 International Business Machines Corporation Method for monitoring and recovery of subsystems in a distributed/clustered system
US5870758A (en) 1996-03-11 1999-02-09 Oracle Corporation Method and apparatus for providing isolation levels in a database system
US5857208A (en) 1996-05-31 1999-01-05 Emc Corporation Method and apparatus for performing point in time backup operation in a computer system
US5758359A (en) 1996-10-24 1998-05-26 Digital Equipment Corporation Method and apparatus for performing retroactive backups in a computer system
US5905988A (en) 1996-11-13 1999-05-18 Imaginon Method and apparatus for database transformation and adaptive playback
US5987506A (en) 1996-11-22 1999-11-16 Mangosoft Corporation Remote access and geographically distributed computers in a globally addressable storage environment
US5875479A (en) 1997-01-07 1999-02-23 International Business Machines Corporation Method and means for making a dual volume level copy in a DASD storage subsystem subject to updating during the copy interval
US5930824A (en) 1997-02-04 1999-07-27 International Business Machines Corporation System and method for demand-base data recovery
US6067550A (en) 1997-03-10 2000-05-23 Microsoft Corporation Database computer system with application recovery and dependency handling write cache
SE511514C2 (en) 1997-05-13 1999-10-11 Ericsson Telefon Ab L M Method and apparatus for image compression
US6249775B1 (en) 1997-07-11 2001-06-19 The Chase Manhattan Bank Method for mortgage and closed end loan portfolio management
US5884328A (en) 1997-08-29 1999-03-16 Tandem Computers, Inc. System and method for sychronizing a large database and its replica
DE69802294T2 (en) 1997-08-29 2002-05-16 Hewlett Packard Co SYSTEMS FOR DATA BACKUP AND RECOVERY
US6223269B1 (en) 1997-09-27 2001-04-24 Emc Corporation Stacked mapped storage system
US6061770A (en) 1997-11-04 2000-05-09 Adaptec, Inc. System and method for real-time data backup using snapshot copying with selective compaction of backup data
US6018746A (en) 1997-12-23 2000-01-25 Unisys Corporation System and method for managing recovery information in a transaction processing system
US6076148A (en) 1997-12-26 2000-06-13 Emc Corporation Mass storage subsystem and backup arrangement for digital data processing system which permits information to be backed up while host computer(s) continue(s) operating in connection with information stored on mass storage subsystem
US6105030A (en) 1998-02-27 2000-08-15 Oracle Corporation Method and apparatus for copying data that resides in a database
US6065018A (en) 1998-03-04 2000-05-16 International Business Machines Corporation Synchronizing recovery log having time stamp to a remote site for disaster recovery of a primary database having related hierarchial and relational databases
US6311288B1 (en) 1998-03-13 2001-10-30 Paradyne Corporation System and method for virtual circuit backup in a communication network
US6324654B1 (en) 1998-03-30 2001-11-27 Legato Systems, Inc. Computer network remote data mirroring system
US6047294A (en) 1998-03-31 2000-04-04 Emc Corp Logical restore from a physical backup in a computer storage system
US6175932B1 (en) 1998-04-20 2001-01-16 National Instruments Corporation System and method for providing state capture and restoration to an I/O system
US6072952A (en) 1998-04-22 2000-06-06 Hewlett-Packard Co. Method and apparatus for coalescing variables
US6260120B1 (en) 1998-06-29 2001-07-10 Emc Corporation Storage mapping and partitioning among multiple host processors in the presence of login state changes and host controller replacement
US6269431B1 (en) 1998-08-13 2001-07-31 Emc Corporation Virtual storage and block level direct access of secondary storage for recovery of backup data
US6931531B1 (en) 1998-09-02 2005-08-16 Matsushita Electric Industrial Co., Ltd. Image object recording, compression, and encryption method and system
US6247141B1 (en) 1998-09-24 2001-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Protocol for providing replicated servers in a client-server system
US6362870B2 (en) 1998-10-26 2002-03-26 Hewlett-Packard Company Image copier having enhanced duplex capabilities; method of printing a copy of a document to produce a duplex copy product
JP3273502B2 (en) 1998-11-26 2002-04-08 インターナショナル・ビジネス・マシーンズ・コーポレーション Disk drive device, disk drive error recovery method, and disk drive control device
US6920537B2 (en) 1998-12-31 2005-07-19 Emc Corporation Apparatus and methods for copying, backing up and restoring logical objects in a computer storage system by transferring blocks out of order or in parallel
US7107395B1 (en) 1998-12-31 2006-09-12 Emc Corporation Apparatus and methods for operating a computer storage system
US8121828B2 (en) 1999-01-28 2012-02-21 Ati Technologies Ulc Detecting conditions for transfer of execution from one computer instruction stream to another and executing transfer on satisfaction of the conditions
US20010011265A1 (en) 1999-02-03 2001-08-02 Cuan William G. Method and apparatus for deploying data among data destinations for website development and maintenance
US6438749B1 (en) 1999-03-03 2002-08-20 Microsoft Corporation Method and system for restoring a computer to its original state after an unsuccessful patch installation attempt
US6751228B1 (en) 1999-03-23 2004-06-15 Yamaha Corporation Packet handler of audio data by isochronous mode
US6449625B1 (en) 1999-04-20 2002-09-10 Lucent Technologies Inc. Use of a two-way stack approach to optimize flash memory management for embedded database systems
US7185081B1 (en) 1999-04-30 2007-02-27 Pmc-Sierra, Inc. Method and apparatus for programmable lexical packet classifier
EP1145519B1 (en) 1999-06-10 2005-08-31 Alcatel Internetworking, Inc. System and method for policy-based network management of virtual private networks
US6691140B1 (en) 1999-07-30 2004-02-10 Computer Associates Think, Inc. Method and system for multidimensional storage model with interdimensional links
US6618851B1 (en) 1999-08-31 2003-09-09 Autodesk, Inc. Method and apparatus for state-reversion
US6487677B1 (en) 1999-09-30 2002-11-26 Lsi Logic Corporation Methods and systems for dynamic selection of error recovery procedures in a managed device
US6647399B2 (en) 1999-11-29 2003-11-11 International Business Machines Corporation Method, system, program, and data structures for naming full backup versions of files and related deltas of the full backup versions
US6434681B1 (en) 1999-12-02 2002-08-13 Emc Corporation Snapshot copy facility for a data storage system permitting continued host read/write access
US6526418B1 (en) 1999-12-16 2003-02-25 Livevault Corporation Systems and methods for backing up data files
US6618822B1 (en) 2000-01-03 2003-09-09 Oracle International Corporation Method and mechanism for relational access of recovery logs in a database system
US6714980B1 (en) 2000-02-11 2004-03-30 Terraspring, Inc. Backup and restore of data associated with a host in a dynamically changing virtual server farm without involvement of a server that uses an associated storage device
US6856993B1 (en) 2000-03-30 2005-02-15 Microsoft Corporation Transactional file system
US6629264B1 (en) 2000-03-30 2003-09-30 Hewlett-Packard Development Company, L.P. Controller-based remote copy system with logical unit grouping
US6606651B1 (en) 2000-05-03 2003-08-12 Datacore Software Corporation Apparatus and method for providing direct local access to file level data in client disk images within storage area networks
US6711699B1 (en) 2000-05-04 2004-03-23 International Business Machines Corporation Real time backup system for information based on a user's actions and gestures for computer users
US6880086B2 (en) 2000-05-20 2005-04-12 Ciena Corporation Signatures for facilitating hot upgrades of modular software components
US6769074B2 (en) 2000-05-25 2004-07-27 Lumigent Technologies, Inc. System and method for transaction-selective rollback reconstruction of database objects
US6532527B2 (en) 2000-06-19 2003-03-11 Storage Technology Corporation Using current recovery mechanisms to implement dynamic mapping operations
US6665815B1 (en) 2000-06-22 2003-12-16 Hewlett-Packard Development Company, L.P. Physical incremental backup using snapshots
CA2413434A1 (en) 2000-06-26 2002-01-03 International Business Machines Corporation Data management application programming interface for a parallel file system
US6950871B1 (en) 2000-06-29 2005-09-27 Hitachi, Ltd. Computer system having a storage area network and method of handling data in the computer system
US6553388B1 (en) 2000-07-20 2003-04-22 International Business Machines Corporation Database deltas using Cyclic Redundancy Checks
US6732125B1 (en) 2000-09-08 2004-05-04 Storage Technology Corporation Self archiving log structured volume with intrinsic data protection
US7099900B1 (en) 2000-09-13 2006-08-29 Veritas Operating Corporation Mapping driver for use in data backup systems
CA2321019A1 (en) 2000-09-27 2002-03-27 Ibm Canada Limited-Ibm Canada Limitee Capturing snapshots of a debuggee's state during a debug session
US6742139B1 (en) 2000-10-19 2004-05-25 International Business Machines Corporation Service processor reset/reload
US7313614B2 (en) 2000-11-02 2007-12-25 Sun Microsystems, Inc. Switching system
JP2002150699A (en) 2000-11-06 2002-05-24 Sony Corp Information processor, information processing method, and recording medium with this method recorded thereon
US7206819B2 (en) 2001-01-18 2007-04-17 Sun Microsystems, Inc. Method and apparatus for providing virtual namespaces for active computing environments
EP1379949A4 (en) 2001-03-05 2006-09-27 Sanpro Systems Inc A system and a method for asynchronous replication for storage area networks
US6795895B2 (en) 2001-03-07 2004-09-21 Canopy Group Dual axis RAID systems for enhanced bandwidth and reliability
JP3769468B2 (en) 2001-03-21 2006-04-26 株式会社エヌ・ティ・ティ・ドコモ Communication quality control method, communication quality control system, packet analysis device, and data transmission terminal device
US20020147941A1 (en) 2001-04-05 2002-10-10 Robert Gentile Network based BIOS recovery method
US6771843B1 (en) 2001-05-11 2004-08-03 Lsi Logic Corporation Data timeline management using snapshot volumes
US20020178146A1 (en) 2001-05-24 2002-11-28 International Business Machines Corporation System and method for selective object history retention
GB0112781D0 (en) 2001-05-25 2001-07-18 Global Continuity Plc Method for rapid recovery from a network file server failure
US6915397B2 (en) 2001-06-01 2005-07-05 Hewlett-Packard Development Company, L.P. System and method for generating point in time storage copy
US6728848B2 (en) 2001-06-11 2004-04-27 Hitachi, Ltd. Method and system for backing up storage system data
US6996602B2 (en) 2001-06-18 2006-02-07 Ford Global Technologies, Llc Server-side page table framework for client application definition and execution
US6792517B1 (en) 2001-06-18 2004-09-14 Maxtor Corporation Firmware controlled backup in disk drives
US20020198699A1 (en) 2001-06-21 2002-12-26 International Business Machines Corporation Apparatus, system and method for providing open source language translation
US20040199549A1 (en) 2001-06-25 2004-10-07 Kenneth Oksanen Method and system for performing concurrency control in a relational database
US7613806B2 (en) 2001-06-28 2009-11-03 Emc Corporation System and method for managing replication sets of data distributed over one or more computer systems
US7305421B2 (en) 2001-07-16 2007-12-04 Sap Ag Parallelized redo-only logging and recovery for highly available main memory database systems
US6948038B2 (en) 2001-07-24 2005-09-20 Microsoft Corporation System and method for backing up and restoring data
US6662198B2 (en) 2001-08-30 2003-12-09 Zoteca Inc. Method and system for asynchronous transmission, backup, distribution of data and file sharing
US6978282B1 (en) 2001-09-04 2005-12-20 Emc Corporation Information replication system having automated replication storage
US7134041B2 (en) 2001-09-20 2006-11-07 Evault, Inc. Systems and methods for data backup over a network
US6748488B2 (en) 2001-09-28 2004-06-08 Sun Microsystems, Inc. Storage array having multiple erasure correction and sub-stripe writing
US7457846B2 (en) 2001-10-05 2008-11-25 International Business Machines Corporation Storage area network methods and apparatus for communication and interfacing with multiple platforms
US6833073B2 (en) 2001-10-09 2004-12-21 Pti Advanced Filtration, Inc. Composite nanofiltration and reverse osmosis membranes and method for producing the same
CA2467404A1 (en) 2001-11-15 2003-05-30 Visto Corporation System and methods for asychronous synchronization
US6775728B2 (en) 2001-11-15 2004-08-10 Intel Corporation Method and system for concurrent handler execution in an SMI and PMI-based dispatch-execution framework
US6799189B2 (en) 2001-11-15 2004-09-28 Bmc Software, Inc. System and method for creating a series of online snapshots for recovery purposes
US6877109B2 (en) 2001-11-19 2005-04-05 Lsi Logic Corporation Method for the acceleration and simplification of file system logging techniques using storage device snapshots
JP3757857B2 (en) 2001-12-12 2006-03-22 ソニー株式会社 Data communication system, data transmission apparatus, data reception apparatus and method, and computer program
JP3785361B2 (en) 2001-12-25 2006-06-14 株式会社ルネサステクノロジ ΔΣ modulator, A / D converter and D / A converter
US7036043B2 (en) 2001-12-28 2006-04-25 Storage Technology Corporation Data management with virtual recovery mapping and backward moves
US20030220929A1 (en) 2002-01-22 2003-11-27 Columbia Data Products, Inc. Managing finite data storage utilizing preservation weights
US7043503B2 (en) 2002-02-15 2006-05-09 International Business Machines Corporation Ditto address indicating true disk address for actual data blocks stored in one of an inode of the file system and subsequent snapshot
US6829617B2 (en) 2002-02-15 2004-12-07 International Business Machines Corporation Providing a snapshot of a subset of a file system
US7373364B1 (en) * 2002-03-05 2008-05-13 Network Appliance, Inc. System and method for creating a point-in-time restoration of a database file
US6950836B2 (en) 2002-03-14 2005-09-27 International Business Machines Corporation Method, system, and program for a transparent file restore
US7143307B1 (en) 2002-03-15 2006-11-28 Network Appliance, Inc. Remote disaster recovery and data migration using virtual appliance migration
US7475098B2 (en) 2002-03-19 2009-01-06 Network Appliance, Inc. System and method for managing a plurality of snapshots
US7010553B2 (en) 2002-03-19 2006-03-07 Network Appliance, Inc. System and method for redirecting access to a remote mirrored snapshot
US7051050B2 (en) 2002-03-19 2006-05-23 Netwrok Appliance, Inc. System and method for restoring a single file from a snapshot
US7093086B1 (en) 2002-03-28 2006-08-15 Veritas Operating Corporation Disaster recovery and backup using virtual machines
US7082446B1 (en) 2002-04-15 2006-07-25 Steel Eye Technology, Inc. Hybrid transaction/intent log for data replication
US6981177B2 (en) 2002-04-19 2005-12-27 Computer Associates Think, Inc. Method and system for disaster recovery
US6898608B2 (en) 2002-04-26 2005-05-24 Oracle International Corporation Techniques for managing what-if analysis of data managed by a relational database system
US20030208511A1 (en) 2002-05-02 2003-11-06 Earl Leroy D. Database replication system
US7426559B2 (en) 2002-05-09 2008-09-16 International Business Machines Corporation Method for sequential coordination of external database application events with asynchronous internal database events
US20030220935A1 (en) 2002-05-21 2003-11-27 Vivian Stephen J. Method of logical database snapshot for log-based replication
US7058849B2 (en) 2002-07-02 2006-06-06 Micron Technology, Inc. Use of non-volatile memory to perform rollback function
US7844577B2 (en) 2002-07-15 2010-11-30 Symantec Corporation System and method for maintaining a backup storage system for a computer system
US7103612B2 (en) 2002-08-01 2006-09-05 Oracle International Corporation Instantiation of objects for information-sharing relationships
US6792518B2 (en) 2002-08-06 2004-09-14 Emc Corporation Data storage system having mata bit maps for indicating whether data blocks are invalid in snapshot copies
US7953926B2 (en) 2002-08-15 2011-05-31 Board Of Governors For Higher Education, State Of Rhode Island And Providence Plantations SCSI-to-IP cache storage device and method
FI119407B (en) 2002-08-28 2008-10-31 Sap Ag A high-quality software-based contact server
US7165156B1 (en) 2002-09-06 2007-01-16 3Pardata, Inc. Read-write snapshots
DE60328796D1 (en) 2002-09-10 2009-09-24 Exagrid Systems Inc METHOD AND DEVICE FOR MANAGING DATA INTEGRITY OF SAFETY AND DISASTER RECOVERY DATA
US6976022B2 (en) 2002-09-16 2005-12-13 Oracle International Corporation Method and mechanism for batch processing transaction logging records
US6938134B2 (en) 2002-09-19 2005-08-30 Sun Microsystems, Inc. System for storing block allocation information on multiple snapshots
US6912631B1 (en) 2002-09-25 2005-06-28 Veritas Operating Corporation Method and apparatus for restoring a corrupted data volume
US20050131969A1 (en) 2002-10-01 2005-06-16 Fujitsu Limited Database duplicating method, database duplicating apparatus, database creating method, and database creating apparatus
US6910106B2 (en) 2002-10-04 2005-06-21 Microsoft Corporation Methods and mechanisms for proactive memory management
US20070129953A1 (en) 2002-10-09 2007-06-07 Business Objects Americas Methods and systems for information strategy management
KR100439675B1 (en) 2002-10-24 2004-07-14 한국전자통신연구원 An efficient snapshot technique for shated large storage
US20040088301A1 (en) 2002-10-31 2004-05-06 Mallik Mahalingam Snapshot of a file system
US7055010B2 (en) 2002-11-06 2006-05-30 Synology Inc. Snapshot facility allowing preservation of chronological views on block drives
WO2004047078A2 (en) 2002-11-20 2004-06-03 Filesx Ltd. Fast backup storage and fast recovery of data (fbsrd)
US7263593B2 (en) 2002-11-25 2007-08-28 Hitachi, Ltd. Virtualization controller and data transfer control method
JP3757933B2 (en) 2002-11-28 2006-03-22 ソニー株式会社 Communication device
US20040117437A1 (en) 2002-12-16 2004-06-17 Exanet, Co. Method for efficient storing of sparse files in a distributed cache
US7007043B2 (en) 2002-12-23 2006-02-28 Storage Technology Corporation Storage backup system that creates mountable representations of past contents of storage volumes
US7296382B2 (en) 2003-01-09 2007-11-20 Pennsylvania Insert Corp. Injection molded thermoplastic insert
US7478096B2 (en) 2003-02-26 2009-01-13 Burnside Acquisition, Llc History preservation in a computer storage system
US7430568B1 (en) 2003-02-28 2008-09-30 Sun Microsystems, Inc. Systems and methods for providing snapshot capabilities in a storage virtualization environment
US7237021B2 (en) 2003-04-04 2007-06-26 Bluearc Uk Limited Network-attached storage system, device, and method supporting multiple storage device types
US7523275B2 (en) 2003-04-10 2009-04-21 International Business Machines Corporation Method, system, and program for maintaining a copy relationship between primary volumes and corresponding secondary volumes
US8209680B1 (en) 2003-04-11 2012-06-26 Vmware, Inc. System and method for disk imaging on diverse computers
US7155465B2 (en) 2003-04-18 2006-12-26 Lee Howard F Method and apparatus for automatically archiving a file system
WO2004095758A2 (en) 2003-04-22 2004-11-04 Cognio, Inc. Signal classification methods for scanning receiver and other applications
US7263590B1 (en) 2003-04-23 2007-08-28 Emc Corporation Method and apparatus for migrating data in a computer system
US7577692B1 (en) 2003-04-25 2009-08-18 Netapp, Inc. System and method for reserving space to guarantee file writability in a file system supporting persistent consistency point images
US7085909B2 (en) 2003-04-29 2006-08-01 International Business Machines Corporation Method, system and computer program product for implementing copy-on-write of a file
US7181476B2 (en) 2003-04-30 2007-02-20 Oracle International Corporation Flashback database
EP1623300A2 (en) 2003-05-14 2006-02-08 Rhysome, Inc. Method and system for reducing information latency in a business enterprise
US20040260678A1 (en) 2003-06-18 2004-12-23 Microsoft Corporation State based configuration failure detection using checkpoint comparison
US20040268068A1 (en) 2003-06-24 2004-12-30 International Business Machines Corporation Efficient method for copying and creating block-level incremental backups of large files and sparse files
US7567991B2 (en) 2003-06-25 2009-07-28 Emc Corporation Replication of snapshot using a file system copy differential
US7398422B2 (en) 2003-06-26 2008-07-08 Hitachi, Ltd. Method and apparatus for data recovery system using storage based journaling
US20050015416A1 (en) 2003-07-16 2005-01-20 Hitachi, Ltd. Method and apparatus for data recovery using storage based journaling
US7899885B2 (en) 2003-06-27 2011-03-01 At&T Intellectual Property I, Lp Business enterprise backup and recovery system and method
US7395278B2 (en) 2003-06-30 2008-07-01 Microsoft Corporation Transaction consistent copy-on-write database
US8095511B2 (en) * 2003-06-30 2012-01-10 Microsoft Corporation Database data recovery system and method
US7165145B2 (en) 2003-07-02 2007-01-16 Falconstor Software, Inc. System and method to protect data stored in a storage system
JP4371724B2 (en) 2003-07-03 2009-11-25 株式会社日立製作所 Storage system and storage device system
US20050010835A1 (en) 2003-07-11 2005-01-13 International Business Machines Corporation Autonomic non-invasive backup and storage appliance
US6938136B2 (en) 2003-07-14 2005-08-30 International Business Machines Corporation Method, system, and program for performing an input/output operation with respect to a logical storage device
JP4321705B2 (en) 2003-07-29 2009-08-26 株式会社日立製作所 Apparatus and storage system for controlling acquisition of snapshot
JP4466001B2 (en) 2003-08-06 2010-05-26 株式会社日立製作所 Snapshot acceleration method
JP2005062928A (en) 2003-08-11 2005-03-10 Hitachi Ltd Remote copy system using two or more sites
WO2005017737A2 (en) 2003-08-14 2005-02-24 Compellent Technologies Virtual disk drive system and method
US7953819B2 (en) 2003-08-22 2011-05-31 Emc Corporation Multi-protocol sharable virtual storage objects
US7406487B1 (en) 2003-08-29 2008-07-29 Symantec Operating Corporation Method and system for performing periodic replication using a log
US7373548B2 (en) 2003-08-29 2008-05-13 Intel Corporation Hardware recovery in a multi-threaded architecture
US7680635B2 (en) 2003-09-19 2010-03-16 Hewlett-Packard Development Company, L.P. Configuration system and method
US7865485B2 (en) 2003-09-23 2011-01-04 Emc Corporation Multi-threaded write interface and methods for increasing the single file read and write throughput of a file server
US7577806B2 (en) 2003-09-23 2009-08-18 Symantec Operating Corporation Systems and methods for time dependent data storage and recovery
US7296008B2 (en) 2004-08-24 2007-11-13 Symantec Operating Corporation Generation and use of a time map for accessing a prior image of a storage device
US7287133B2 (en) 2004-08-24 2007-10-23 Symantec Operating Corporation Systems and methods for providing a modification history for a location within a data store
US7734909B1 (en) 2003-09-29 2010-06-08 Avaya Inc. Using voice over IP or instant messaging to connect to customer products
US8595185B2 (en) 2003-09-29 2013-11-26 International Business Machines Corporation Storage disaster recovery using a predicted superset of unhardened primary data
US7158991B2 (en) 2003-09-30 2007-01-02 Veritas Operating Corporation System and method for maintaining temporal data in data storage
US7225208B2 (en) 2003-09-30 2007-05-29 Iron Mountain Incorporated Systems and methods for backing up data files
US7133884B1 (en) 2003-11-26 2006-11-07 Bmc Software, Inc. Unobtrusive point-in-time consistent copies
US7133941B2 (en) 2003-12-03 2006-11-07 Oracle International Corporation Method and mechanism of accessing segments in data storage systems
CA2452251C (en) 2003-12-04 2010-02-09 Timothy R. Jewell Data backup system and method
US7373451B2 (en) 2003-12-08 2008-05-13 The Board Of Trustees Of The Leland Stanford Junior University Cache-based system management architecture with virtual appliances, network repositories, and virtual appliance transceivers
US20050132351A1 (en) 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback
US7281023B2 (en) 2003-12-15 2007-10-09 At&T Knowledge Ventures, L.P. Architecture of database application with robust online recoverability
US20050138090A1 (en) 2003-12-17 2005-06-23 Oliver Augenstein Method and apparatus for performing a backup of data stored in multiple source medium
US7155586B1 (en) 2003-12-30 2006-12-26 Emc Corporation Method of allowing point-in-time view of data on a disk using a map on cache disk
US20050198303A1 (en) 2004-01-02 2005-09-08 Robert Knauerhase Dynamic virtual machine service provider allocation
US7328307B2 (en) 2004-01-22 2008-02-05 Tquist, Llc Method and apparatus for improving update performance of non-uniform access time persistent storage media
US7325159B2 (en) 2004-02-04 2008-01-29 Network Appliance, Inc. Method and system for data recovery in a continuous data protection system
US7720817B2 (en) 2004-02-04 2010-05-18 Netapp, Inc. Method and system for browsing objects on a protected volume in a continuous data protection system
US7406488B2 (en) 2004-02-04 2008-07-29 Netapp Method and system for maintaining data in a continuous data protection system
US7426617B2 (en) 2004-02-04 2008-09-16 Network Appliance, Inc. Method and system for synchronizing volumes in a continuous data protection system
US7440965B1 (en) 2004-02-11 2008-10-21 Network Appliance, Inc. Method and system for generating and restoring a backup image
WO2005078606A2 (en) 2004-02-11 2005-08-25 Storage Technology Corporation Clustered hierarchical file services
US7440966B2 (en) 2004-02-12 2008-10-21 International Business Machines Corporation Method and apparatus for file system snapshot persistence
US7251749B1 (en) 2004-02-12 2007-07-31 Network Appliance, Inc. Efficient true image recovery of data from full, differential, and incremental backups
US7206911B2 (en) 2004-02-25 2007-04-17 International Business Machines Corporation Method, system, and program for a system architecture for an arbitrary number of backup components
US7421549B2 (en) 2004-03-02 2008-09-02 Hitachi, Ltd. Method and apparatus of remote copy for multiple storage subsystems
US7353241B2 (en) 2004-03-24 2008-04-01 Microsoft Corporation Method, medium and system for recovering data using a timeline-based computing environment
US7171511B2 (en) 2004-03-24 2007-01-30 Hitachi, Ltd. WORM proving storage system
US7130971B2 (en) 2004-03-30 2006-10-31 Hitachi, Ltd. Assuring genuineness of data stored on a storage device
US7277905B2 (en) 2004-03-31 2007-10-02 Microsoft Corporation System and method for a consistency check of a database backup
US20050223181A1 (en) 2004-03-31 2005-10-06 Jeppsen Roger C Integrated circuit capable of copy management
US7350046B2 (en) 2004-04-02 2008-03-25 Seagate Technology Llc Managed reliability storage system and method monitoring storage conditions
JP2005301497A (en) 2004-04-08 2005-10-27 Hitachi Ltd Storage management system, restoration method and its program
US7167880B2 (en) 2004-04-14 2007-01-23 Hitachi, Ltd. Method and apparatus for avoiding journal overflow on backup and recovery system using storage based journaling
JP4561168B2 (en) 2004-04-28 2010-10-13 株式会社日立製作所 Data processing system and method, and processing program therefor
US7213022B2 (en) 2004-04-29 2007-05-01 Filenet Corporation Enterprise content management network-attached system
US7340646B2 (en) 2004-05-03 2008-03-04 International Business Machines Corporation Apparatus, system, and method for resource group backup
US8019925B1 (en) 2004-05-06 2011-09-13 Seagate Technology Llc Methods and structure for dynamically mapped mass storage device
US8108429B2 (en) 2004-05-07 2012-01-31 Quest Software, Inc. System for moving real-time data events across a plurality of devices in a network for simultaneous data protection, replication, and access services
US7096392B2 (en) 2004-05-07 2006-08-22 Asempra Technologies, Inc. Method and system for automated, no downtime, real-time, continuous data protection
US7565661B2 (en) 2004-05-10 2009-07-21 Siew Yong Sim-Tang Method and system for real-time event journaling to provide enterprise data services
US20050267920A1 (en) 2004-05-13 2005-12-01 Fabrice Helliker System and method for archiving data in a clustered environment
US7386663B2 (en) 2004-05-13 2008-06-10 Cousins Robert E Transaction-based storage system and method that uses variable sized objects to store data
JP4624829B2 (en) 2004-05-28 2011-02-02 富士通株式会社 Data backup system and method
US8868858B2 (en) 2006-05-19 2014-10-21 Inmage Systems, Inc. Method and apparatus of continuous data backup and access using virtual machines
US9209989B2 (en) 2004-06-01 2015-12-08 Inmage Systems, Inc. Causation of a data read operation against a first storage system by a server associated with a second storage system according to a host generated instruction
US8949395B2 (en) 2004-06-01 2015-02-03 Inmage Systems, Inc. Systems and methods of event driven recovery management
US7979656B2 (en) 2004-06-01 2011-07-12 Inmage Systems, Inc. Minimizing configuration changes in a fabric-based data protection solution
US8224786B2 (en) 2004-06-01 2012-07-17 Inmage Systems, Inc. Acquisition and write validation of data of a networked host node to perform secondary storage
US7698401B2 (en) 2004-06-01 2010-04-13 Inmage Systems, Inc Secondary data storage and recovery system
US7676502B2 (en) 2006-05-22 2010-03-09 Inmage Systems, Inc. Recovery point data view shift through a direction-agnostic roll algorithm
US8055745B2 (en) 2004-06-01 2011-11-08 Inmage Systems, Inc. Methods and apparatus for accessing data from a primary data storage system for secondary storage
US7620785B1 (en) 2004-06-30 2009-11-17 Symantec Operating Corporation Using roll-forward and roll-backward logs to restore a data volume
JP2006031608A (en) 2004-07-21 2006-02-02 Hitachi Ltd Computer, storage system, file management method which computer performs, and program
US7254682B1 (en) 2004-07-28 2007-08-07 Symantec Corporation Selective file and folder snapshot image creation
US20060047714A1 (en) 2004-08-30 2006-03-02 Mendocino Software, Inc. Systems and methods for rapid presentation of historical views of stored data
US7664983B2 (en) 2004-08-30 2010-02-16 Symantec Corporation Systems and methods for event driven recovery management
US20060053139A1 (en) 2004-09-03 2006-03-09 Red Hat, Inc. Methods, systems, and computer program products for implementing single-node and cluster snapshots
US8645496B2 (en) 2004-09-07 2014-02-04 Emc Corporation Systems and methods for backing up data
US8145601B2 (en) 2004-09-09 2012-03-27 Microsoft Corporation Method, system, and apparatus for providing resilient data transfer in a data protection system
US20060059209A1 (en) 2004-09-14 2006-03-16 Lashley Scott D Crash recovery by logging extra data
US7296115B2 (en) 2004-09-17 2007-11-13 Hitachi, Ltd. Method of and system for controlling attributes of a plurality of storage devices
US20060080362A1 (en) 2004-10-12 2006-04-13 Lefthand Networks, Inc. Data Synchronization Over a Computer Network
US7814367B1 (en) 2004-11-12 2010-10-12 Double-Take Software Canada, Inc. Method and system for time addressable storage
US7822715B2 (en) 2004-11-16 2010-10-26 Petruzzo Stephen E Data mirroring method
US20060114497A1 (en) 2004-11-30 2006-06-01 Xerox Corporation Printing system
WO2006062513A1 (en) 2004-12-06 2006-06-15 Gresham Enterprise Storage Inc. Storage consolidation platform
US7400578B2 (en) 2004-12-16 2008-07-15 International Business Machines Corporation Method and system for throttling network transmissions using per-receiver bandwidth control at the application layer of the transmitting server
US8260753B2 (en) 2004-12-31 2012-09-04 Emc Corporation Backup information management
US7849257B1 (en) 2005-01-06 2010-12-07 Zhe Khi Pak Method and apparatus for storing and retrieving data
US8073926B2 (en) 2005-01-07 2011-12-06 Microsoft Corporation Virtual machine image server
US20060155912A1 (en) 2005-01-12 2006-07-13 Dell Products L.P. Server cluster having a virtual server
US7839865B2 (en) 2005-01-26 2010-11-23 Emulex Design & Manufacturing Corporation Dynamically controlling fair access to a system packet interface attached switch enclosure
US7546431B2 (en) 2005-03-21 2009-06-09 Emc Corporation Distributed open writable snapshot copy facility using file migration policies
US20060218434A1 (en) 2005-03-25 2006-09-28 Erik Solhjell Disk drive with integrated tape drive
US7814057B2 (en) 2005-04-05 2010-10-12 Microsoft Corporation Page recovery using volume snapshots and logs
US7743178B2 (en) 2005-04-11 2010-06-22 Emulex Design & Manufacturing Corporation Method and apparatus for SATA tunneling over fibre channel
US7672979B1 (en) 2005-04-22 2010-03-02 Symantec Operating Corporation Backup and restore techniques using inconsistent state indicators
US7373366B1 (en) 2005-06-10 2008-05-13 American Megatrends, Inc. Method, system, apparatus, and computer-readable medium for taking and managing snapshots of a storage volume
US7536529B1 (en) 2005-06-10 2009-05-19 American Megatrends, Inc. Method, system, apparatus, and computer-readable medium for provisioning space in a data storage system
US7577689B1 (en) 2005-06-15 2009-08-18 Adobe Systems Incorporated Method and system to archive data
US20070022117A1 (en) 2005-07-21 2007-01-25 Keohane Susann M Accessing file system snapshots directly within a file system directory
US20070033356A1 (en) 2005-08-03 2007-02-08 Boris Erlikhman System for Enabling Secure and Automatic Data Backup and Instant Recovery
US7434218B2 (en) 2005-08-15 2008-10-07 Microsoft Corporation Archiving data in a virtual application environment
US7426618B2 (en) 2005-09-06 2008-09-16 Dot Hill Systems Corp. Snapshot restore method and apparatus
US8683144B2 (en) 2005-09-16 2014-03-25 Inmage Systems, Inc. Causation of a data read against a first storage system to optionally store a data write to preserve the version to allow viewing and recovery
US8601225B2 (en) 2005-09-16 2013-12-03 Inmage Systems, Inc. Time ordered view of backup data on behalf of a host
US7610314B2 (en) 2005-10-07 2009-10-27 Oracle International Corporation Online tablespace recovery for export
JP4809040B2 (en) 2005-11-08 2011-11-02 株式会社日立製作所 Storage apparatus and snapshot restore method
JP4856955B2 (en) 2006-01-17 2012-01-18 株式会社日立製作所 NAS system and remote copy method
US8321377B2 (en) 2006-04-17 2012-11-27 Microsoft Corporation Creating host-level application-consistent backups of virtual machines
US7441092B2 (en) 2006-04-20 2008-10-21 Microsoft Corporation Multi-client cluster-based backup and restore
US8838528B2 (en) 2006-05-22 2014-09-16 Inmage Systems, Inc. Coalescing and capturing data between events prior to and after a temporal window
US8527721B2 (en) 2008-12-26 2013-09-03 Rajeev Atluri Generating a recovery snapshot and creating a virtual view of the recovery snapshot
US8732136B2 (en) 2006-05-22 2014-05-20 Inmage Systems, Inc. Recovery point data view shift through a direction-agnostic roll algorithm
US8527470B2 (en) 2006-05-22 2013-09-03 Rajeev Atluri Recovery point data view formation with generation of a recovery view and a coalesce policy
US8271452B2 (en) * 2006-06-12 2012-09-18 Rainstor Limited Method, system, and database archive for enhancing database archiving
US8024762B2 (en) 2006-06-13 2011-09-20 Time Warner Cable Inc. Methods and apparatus for providing virtual content over a network
US20080046710A1 (en) 2006-08-17 2008-02-21 Steven Maddocks Switching firmware images in storage systems
US8589341B2 (en) 2006-12-04 2013-11-19 Sandisk Il Ltd. Incremental transparent file updating
US20080147821A1 (en) 2006-12-19 2008-06-19 Dietrich Bradley W Managed peer-to-peer content backup service system and method using dynamic content dispersal to plural storage nodes
US8880480B2 (en) * 2007-01-03 2014-11-04 Oracle International Corporation Method and apparatus for data rollback
US8190572B2 (en) 2007-02-15 2012-05-29 Yahoo! Inc. High-availability and data protection of OLTP databases
US8364648B1 (en) * 2007-04-09 2013-01-29 Quest Software, Inc. Recovering a database to any point-in-time in the past with guaranteed data consistency
US7827350B1 (en) 2007-04-27 2010-11-02 Netapp, Inc. Method and system for promoting a snapshot in a distributed file system
US7853571B2 (en) 2007-09-28 2010-12-14 Symantec Corporation Techniques for file system recovery
US20090150906A1 (en) 2007-12-07 2009-06-11 Sap Ag Automatic electronic discovery of heterogeneous objects for litigation
US8028194B2 (en) 2008-07-25 2011-09-27 Inmage Systems, Inc Sequencing technique to account for a clock error in a backup system
KR100926098B1 (en) * 2008-11-18 2009-11-11 주식회사 네오플 Method and apparatus for information recovery in using snap shot database
US8069227B2 (en) 2008-12-26 2011-11-29 Inmage Systems, Inc. Configuring hosts of a secondary data storage and recovery system
US8225146B2 (en) * 2009-09-01 2012-07-17 Lsi Corporation Method for implementing continuous data protection utilizing allocate-on-write snapshots
US8433682B2 (en) * 2009-12-31 2013-04-30 Commvault Systems, Inc. Systems and methods for analyzing snapshots
WO2013138969A1 (en) 2012-03-17 2013-09-26 Beijing Haipu Wangju Technology Limited Method and system for recommending content to a user
US10346369B2 (en) * 2012-10-11 2019-07-09 Delphix Corp. Retrieving point-in-time copies of a source database for creating virtual databases
CN103914359B (en) * 2012-12-31 2017-09-26 中国移动通信集团浙江有限公司 A kind of data reconstruction method and device
US9244775B2 (en) 2013-03-14 2016-01-26 International Business Machines Corporation Reducing reading of database logs by persisting long-running transaction data
US9672237B2 (en) 2013-03-15 2017-06-06 Amazon Technologies, Inc. System-wide checkpoint avoidance for distributed database systems
US11030055B2 (en) 2013-03-15 2021-06-08 Amazon Technologies, Inc. Fast crash recovery for distributed database systems

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030158873A1 (en) * 2002-02-15 2003-08-21 International Business Machines Corporation Dynamic links to file system snapshots
US20050022213A1 (en) * 2003-07-25 2005-01-27 Hitachi, Ltd. Method and apparatus for synchronizing applications for data recovery using storage based journaling
US20070185922A1 (en) * 2006-02-07 2007-08-09 Aditya Kapoor Point-in-time database restore

Also Published As

Publication number Publication date
US9558078B2 (en) 2017-01-31
BR112017005834A2 (en) 2017-12-19
EP3213212B1 (en) 2019-04-03
JP2017533520A (en) 2017-11-09
RU2017114019A (en) 2018-10-24
US20160117228A1 (en) 2016-04-28
CN107077404A (en) 2017-08-18
EP3213212A1 (en) 2017-09-06
CN107077404B (en) 2020-08-25

Similar Documents

Publication Publication Date Title
EP3213212B1 (en) Point in time database restore from storage snapshots
US10664362B2 (en) Recovery processing for database in persistent system
KR102579190B1 (en) Backup and restore in distributed databases using consistent database snapshots
US11016944B2 (en) Transferring objects between different storage devices based on timestamps
EP3685268B1 (en) File system point-in-time restore using recycle bin and version history
CN110447021B (en) Method, apparatus and system for maintaining consistency of metadata and data between data centers
US10565071B2 (en) Smart data replication recoverer
WO2016180160A1 (en) Data snapshot recovery method and apparatus
US10635632B2 (en) Snapshot archive management
US20190163372A1 (en) Performing backup operations using replicas
AU2018324425A1 (en) Restoring a database using a fully hydrated backup
US20160103850A1 (en) Synchronizing Updates Across Cluster Filesystems
CN107003890B (en) Efficiently providing virtual machine reference points
WO2020207010A1 (en) Data backup method and device, and computer-readable storage medium
WO2022048495A1 (en) Data backup method and apparatus, data recovery method and apparatus, and electronic device
US9454591B2 (en) Synchronization of sequential access storage components with backup catalog
EP3796174B1 (en) Restoring a database using a fully hydrated backup
US20230096910A1 (en) Methods and systems for differential based backups
US20180032555A1 (en) Object database system including an object-specific historical attribute-change information system
US11093348B2 (en) Method, device and computer program product for recovering metadata
US8543544B2 (en) Checkpoint based progressive backup
EP3454231B1 (en) Remotely mounted file system with stubs
US10255237B2 (en) Isolation level support in distributed database system
US10860540B1 (en) Method and system for synchronizing backup and cloning schedules
US11650882B1 (en) Method and system for performing rename operations during differential based backups in storage devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15794386

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017005834

Country of ref document: BR

REEP Request for entry into the european phase

Ref document number: 2015794386

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015794386

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017114019

Country of ref document: RU

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017523303

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112017005834

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170322