Netapp, Inc.

Michael David Mankovsky

Qing Zhang

Grace Zhanglei Wu

Pawel Malinowski

A system, method, and computer program product are provided for allowing access to backup data resulting from performance of one or more recovery point backup operations and one or more full backup operations. This is accomplished by associating recovery point backup operations with full backup operations and allowing access to backup data resulting from performance of the recovery point backup operations and the full backup operations. In this way, logs corresponding to the backup operations may be associated with a backup path, such that the logs may be accessed during a restore operation. Furthermore, the recovery point operations may be configured to provide a user defined granularity for data recovery. To this end, in various embodiments, backup data may be stored at a granularity defined by a user and recovered based on a user selection of a recovery point.

System, method, and computer program product for allowing access to backup data

Embodiments of the present invention provide a mechanism by which a server system executing a host application monitors utilization of overwrite reserve space on a volume storing application data. The server system executes space reservation policies to ensure that the volume cannot run out of space due to snapshot creation. In one implementation, the server system initiates deletion of backup datasets stored on the volume if certain criteria provided by a system administrator are met. If deleting backup datasets cannot not stop the volume from running out of space due to continuous snapshot creation, the server system prevents the host application from temporarily issuing I/O requests to the storage system until space is recovered. Preventing the host application from issuing I/O requests, rather than failing I/O requests by the storage system, eliminates undesirable consequences, such as loss of data and the need to perform data recovery.

Backup data management on a fractionally reserved storage system

A mechanism is provided for archiving and restoring transaction files of a database system without requiring the copying of the transaction files. A server system executes a host application that implements the database system comprising a set of database files and a set of transaction files that contains updates to the set of database files, the files being stored in a storage system. A backup engine interacts with the host application to archive a transaction file having an original filename in an original directory by creating a corresponding archive filename to the transaction file in an archive directory. The archive transaction files may be used later to perform a copy-less restore process of the database system that does not require copying of any transaction files. The copy-less restore process restores any altered original filenames by replacing, in the original directory, an altered original filename with its corresponding archive filename.

Copy-less restoring of transaction files of a database system

The present invention provides a method for generating a backup of a database file that is suitable for a hard recovery operation. A snapshot of the database file is generated and the log and/or patch files associated with the database are stored in a backup location. Additionally, the header and/or footer information of the database is stored, thereby enabling a restored snapshot of the database to be converted into a file suitable for a hard recovery operation.

Growing community of inventors

Gilroy, CA, United States of America

Michael David Mankovsky