Abstract: Restoring a clustered database having a plurality of nodes each having database from a failed storage device by receiving a request to restore a backup image of a failed shared storage device associated with the clustered database to a time; performing a preflight check including at least one checklist process; terminating the restore when any checklist process fails; when each checklist process succeeds completing the restore by creating at least one flashcopy associated with the backup image, mapping to each of the plurality of nodes an associated portion of the at least one flashcopy, mounting the at least one flashcopy to the node as a diskgroup, and switching the clustered database to run from the diskgroup.

Abstract: Restoring a clustered database having a plurality of nodes each having database from a failed storage device by receiving a request to restore a backup image of a failed shared storage device associated with the clustered database to a time; performing a preflight check including at least one checklist process; terminating the restore when any checklist process fails; when each checklist process succeeds completing the restore by creating at least one flashcopy associated with the backup image, mapping to each of the plurality of nodes an associated portion of the at least one flashcopy, mounting the at least one flashcopy to the node as a diskgroup, and switching the clustered database to run from the diskgroup.

Abstract: Restoring a clustered database having a plurality of nodes each having database from a failed storage device by receiving a request to restore a backup image of a failed shared storage device associated with the clustered database to a time; performing a preflight check including at least one checklist process; terminating the restore when any checklist process fails; when each checklist process succeeds completing the restore by creating at least one flashcopy associated with the backup image, mapping to each of the plurality of nodes an associated portion of the at least one flashcopy, mounting the at least one flashcopy to the node as a diskgroup, and switching the clustered database to run from the diskgroup.

Abstract: Restoring a clustered database having a plurality of nodes each having database from a failed storage device by receiving a request to restore a backup image of a failed shared storage device associated with the clustered database to a time; performing a preflight check including at least one checklist process; terminating the restore when any checklist process fails; when each checklist process succeeds completing the restore by creating at least one flashcopy associated with the backup image, mapping to each of the plurality of nodes an associated portion of the at least one flashcopy, mounting the at least one flashcopy to the node as a diskgroup, and switching the clustered database to run from the diskgroup.

Abstract: Systems and methods are provided for automating a provision of applications from a source to a target by providing a virtual copy of application data, wherein the virtual copy can be adapted to a plurality of different target environments. Versions of source application data from an application database at a source production server are maintained at times associated with a schedule. Data associated with a request is received from a user to provision the source application data for a target environment at a target server, the request further comprising application specific parameters that define necessary requirements for the target environment. A virtual copy of the source application data is presented to the target server. Instructions to the target server are transmitted that define how to restore an operational server database from the virtual copy based on the application specific parameters to meet the requirements of the target environment.

Abstract: Systems and methods of utilizing multiple threads to facilitate parallel data copying to reduce an amount of time associated with backing up data. A request to copy application is received that indicates a number of available threads. A first available thread is used to select files from the application for backup. Selecting a file includes adding files to a work queue and creating backup work items associated with the work queue files. The files in the work queue are processed by a multiple threads in parallel such that an amount of time associated with backup up the application is reduced.

Abstract: Systems and methods for backing up clustered databases such that production backups associated with the clustered databases are restorable with near zero downtime. First data indicative of a backup request of a clustered database is transmitted by a first computing device to a second computing device. The first computing device maps the backup staging disks to each of a plurality of nodes. The second computing device adds the mapped staging disks to a backup staging diskgroup on a primary node. The second computing device mounts the backup staging diskgroup to each of the plurality of nodes. The second computing device executes a full backup from at least one of the plurality of nodes to the backup staging diskgroup. The second computing device transmits a catalog of backup information to a database associated with the first computing device. The first computing device creates a snapshot of the first backup staging disk.

Abstract: Systems and methods of performing backup of databases and associated logs with one schedule such that a backup of both a database and its associated log can be restored or recovered to a desired point in time. A backup request associated with a backup type is received and defined by a service level agreement. The service level agreement includes a combined schedule for backing up both data stored in the database and log data associated with a database.

Abstract: Systems and methods for checking data integrity of a data object copied between storage pools in a storage system by comparing data samples copied from data objects. A series of successive copy operations are scheduled over time for copying a data object from a source data store to a target data store. A first data sample is generated based on a sampling scheme comprising an offset and a period. A second data sample is generated using a similar sampling scheme. The blocks of data in the first data sample and the second data sample are compared to determine if they differ to thereby indicate that the data object at the target store differs from the corresponding data object at the source data store.

Abstract: Systems and methods are provided for automating a provision of applications from a source to a target by providing a virtual copy of application data, wherein the virtual copy can be adapted to a plurality of different target environments. Versions of source application data from an application database at a source production server are maintained at times associated with a schedule. Data associated with a request is received from a user to provision the source application data for a target environment at a target server, the request further comprising application specific parameters that define necessary requirements for the target environment. A virtual copy of the source application data is presented to the target server. Instructions to the target server are transmitted that define how to restore an operational server database from the virtual copy based on the application specific parameters to meet the requirements of the target environment.

Abstract: Systems and methods for backing up clustered databases such that production backups associated with the clustered databases are restorable with near zero downtime. First data indicative of a backup request of a clustered database is transmitted by a first computing device to a second computing device. The first computing device maps the backup staging disks to each of a plurality of nodes. The second computing device adds the mapped staging disks to a backup staging diskgroup on a primary node. The second computing device mounts the backup staging diskgroup to each of the plurality of nodes. The second computing device executes a full backup from at least one of the plurality of nodes to the backup staging diskgroup. The second computing device transmits a catalog of backup information to a database associated with the first computing device. The first computing device creates a snapshot of the first backup staging disk.

Abstract: Systems and methods are provided for intra-process communication in a backup framework. A custom requester is registered with a framework configured to run and coordinate one or more requesters and one or more providers, wherein the framework provides an application programmer interface for the requesters and providers. A first requester from the one or more requesters starts a backup process for a first data set associated with a first application. The first requester determines that the data storage device associated with the first data set and the first application is exported by a data management system. The first requester selects a first provider to create a backup of the first data set for the backup process, wherein the first requester and first provider are separate threads in a same process space that can communicate directly with each other using one or more intra-process communication channels.

Abstract: Systems and methods of utilizing multiple threads to facilitate parallel data copying to reduce an amount of time associated with backing up data. A request to copy application is received that indicates a number of available threads. A first available thread is used to select files from the application for backup. Selecting a file includes adding files to a work queue and creating backup work items associated with the work queue files. The files in the work queue are processed by a multiple threads in parallel such that an amount of time associated with backup up the application is reduced.

Abstract: Systems and methods of performing backup of databases and associated logs with one schedule such that a backup of both a database and its associated log can be restored or recovered to a desired point in time. A backup request associated with a backup type is received and defined by a service level agreement. The service level agreement includes a combined schedule for backing up both data stored in the database and log data associated with a database.

Abstract: Computerized methods and systems are disclosed for creating an incremental backup of application data by creating a snapshot associated with a current incremental backup of a data file using a change tracking bitmap such that a data file associated with the current incremental backup can be restored from just the snapshot associated with the current incremental backup and an initial backup without needing to access one or more previously generated incremental backups of the data file.

Abstract: Systems and methods are provided for intra-process communication in a backup framework. A custom requester is registered with a framework configured to run and coordinate one or more requesters and one or more providers, wherein the framework provides an application programmer interface for the requesters and providers. A first requester from the one or more requesters starts a backup process for a first data set associated with a first application. The first requester determines that the data storage device associated with the first data set and the first application is exported by a data management system. The first requester selects a first provider to create a backup of the first data set for the backup process, wherein the first requester and first provider are separate threads in a same process space that can communicate directly with each other using one or more intra-process communication channels.