Abstract: Methods for creating a live copy of a data object from a production system for use by third party applications include receiving at least one request for a copy of production data from an application; creating a live backup copy; creating a flash copy of the live backup copy, and a flash copy bitmap; creating a modified version of the live backup copy by changing a subset of data in the live backup copy; recording the changed subset of data using the flash copy bitmap; mounting, the modified version of the live backup copy to the application; and transforming the modified version of the live backup copy back to the live backup copy when unmounting the modified version of the live backup copy of the production data from the application by applying changes associated with the flash copy bitmap to the live backup copy.

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 for creating a live copy of a data object from a production system for use by third party applications. The systems and methods include receiving at least one request for a copy of production data from an application; creating a live backup copy; creating a flash copy of the live backup copy, and a flash copy bitmap; creating a modified version of the live backup copy by changing a subset of data in the live backup copy; recording the changed subset of data using the flash copy bitmap; mounting, the modified version of the live backup copy to the application; and transforming the modified version of the live backup copy back to the live backup copy when unmounting the modified version of the live backup copy of the production data from the application by applying changes associated with the flash copy bitmap to the live backup copy.

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 for creating a live copy of a data object from a production system for use by third party applications. The systems and methods include receiving at least one request for a copy of production data from an application; creating a live backup copy; creating a flash copy of the live backup copy, and a flash copy bitmap; creating a modified version of the live backup copy by changing a subset of data in the live backup copy; recording the changed subset of data using the flash copy bitmap; mounting, the modified version of the live backup copy to the application; and transforming the modified version of the live backup copy back to the live backup copy when unmounting the modified version of the live backup copy of the production data from the application by applying changes associated with the flash copy bitmap to the live backup copy.

Abstract: Systems and methods of backing up data to a replication target such that the data is recoverable from the replication target when a source application and one or more other intermediary replication targets are unavailable. A first deduplicated data object associated with an application is received at a first intermediary copy data management system based on a first schedule. The first deduplicated data object is replicated to generate at least one of a second deduplicated data object at a second copy data management system according to a second schedule.

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 of capturing application data locally on a source data management system and performing a high performance, bandwidth optimized replication the data from the source data management system to a remote data management system either (a) in parallel with copying data from an application to the source data management system, or (b) serially by replicating the data to the remote data management system after the data is copied to the source data management system, wherein the determination to operate in parallel or serially is based on at least one of a characteristic of the data and user specified tuning parameters.

Abstract: Systems and methods of backing up data to a replication target such that the data is recoverable from the replication target when a source application and one or more other intermediary replication targets are unavailable. A first deduplicated data object associated with an application is received at a first intermediary copy data management system based on a first schedule. The first deduplicated data object is replicated to generate at least one of a second deduplicated data object at a second copy data management system according to a second schedule.

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: Techniques are disclosed for preventing a user from configuring a service level agreement from creating a data management schedule that creates a set of data backups that exceeds data resource limits available for storing the set of data backups. A first amount of pool resources associated with the backup of each of the at least one application is determined according to a received schedule. A first amount of data volumes associated with the backup of each of the at least one application is determined according to the received schedule. A resource shortage warning is transmitted when the aggregate amount of pool resources exceeds an available amount of pool resources or the aggregate amount of data volume resource exceeds an available amount of data volume resource, thereby preventing a user from configuring a service level agreement that exceeds data resource limits.

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 backing up data to a replication target such that the data is recoverable from the replication target when a source application and one or more other intermediary replication targets are unavailable. A first deduplicated data object associated with an application is received at a first intermediary copy data management system based on a first schedule. The first deduplicated data object is replicated to generate at least one of a second deduplicated data object at a second copy data management system according to a second schedule.

Abstract: Systems and methods are disclosed for copying a data object to a target storage pool using a hybrid of storage pools, in which at least one of the storage pools of the hybrid is particularly efficient at identifying data that should be used for copying the data object to the target storage pool, and at least one of the storage pools of the hybrid is particularly efficient at retrieving the data that should be sent to the target storage pool. The system comprises a performance storage pool for storing data and having relatively high performance for retrieving stored data; a deduplicating storage pool for storing deduplicated data and storing metadata about data objects in the system and which has relatively high performance for identifying and specifying differences in a data object over time; and a controller for causing the performance storage pool to retrieve differences and provide the data to the target storage pool.

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 disclosed for checking the data integrity of a data object copied between storage pools in a storage system by comparing data fingerprints of data objects, by scheduling a series of successive copy operations over time for copying a data object from a source data store to a target data store; generating a partial fingerprint of the data object at the source data store using a data fingerprinting operation that creates a fingerprint from a subset of data of the data object; sending the partial fingerprint of the data object to the target data store; sending any new data contents for the data object to the target data store; and creating a partial fingerprint of the data object at the target data store and comparing it to the partial fingerprint sent to the target data store to determine if they differ.

Abstract: Systems and methods are disclosed for a system for managing data in accordance with service level agreements (SLAs) that specify schedules on a calendar basis for performing prescribed data management functions and for reducing inter-function redundancy. This system may include a data management engine for performing data management functions, including at least a snapshot function, and at least one back-up function. The data management engine may include a service level policy engine that receives SLAs in electronic form and which controls the scheduling of the data management functions. Each electronic SLA may be associated with a corresponding application and may specify at least one service level policy, each policy specifying a source pool, a destination pool, a copy frequency, a retention period and schedule information. A collection of policies is capable of expressing a non-uniform schedule for when a given function should be performed.

Abstract: Systems and methods of capturing application data locally on a source data management system and performing a high performance, bandwidth optimized replication the data from the source data management system to a remote data management system either (a) in parallel with copying data from an application to the source data management system, or (b) serially by replicating the data to the remote data management system after the data is copied to the source data management system, wherein the determination to operate in parallel or serially is based on at least one of a characteristic of the data and user specified tuning parameters.