Abstract: Provided are techniques for providing and managing data protection by using incremental forever for storage to cloud object stores. An incremental offload is performed by using one or more extents to identify blocks of data for a version of a virtual machine in operational recovery storage to be offloaded to a cloud object store, wherein each of the one or more extents identifies locations of the blocks of data. The blocks of data are converted to objects in an incremental forever data format. The objects are offloaded to the cloud object store. The details of the offloading of the objects are stored in a local database in the operational recovery storage. The local database is copied from the operational recovery storage to the cloud object store as a database copy.

Abstract: Provided are techniques for providing and managing data protection by using incremental forever for storage to cloud object stores. An incremental offload is performed by using one or more extents to identify blocks of data for a version of a virtual machine in operational recovery storage to be offloaded to a cloud object store, wherein each of the one or more extents identifies locations of the blocks of data. The blocks of data are converted to objects in an incremental forever data format. The objects are offloaded to the cloud object store. The details of the offloading of the objects are stored in a local database in the operational recovery storage. The local database is copied from the operational recovery storage to the cloud object store as a database copy.

Abstract: An apparatus, method and computer program product are disclosed. The apparatus includes a strategy module that determines restore information, writes the restore information into a restore information file, and writes the restore information file to a master volume containing target data; a snapshot module that creates a snapshot backup of the master volume; and a restoration module that restores the target data and restore information file, and restores application consistency of the target data. The method includes determining restore information, writing restore information to a file, writing the file to a volume containing data, backing up data by a snapshot backup of the volume, restoring data and the file, and restoring application consistency of the data. The computer program product comprises a computer readable storage medium that stores code to perform determining a backup strategy, backing up data, and restoring data.

Abstract: A method for executing complex data protection operations is disclosed. In one embodiment, such a method includes generating multiple complex data protection operations, where each complex data protection operation includes multiple data protection functions pre-arranged in a specified order and on a specified schedule. The method further presents the multiple complex data protection operations to a user in the form of a menu. This menu includes multiple menu options, where each menu option is associated with one of the complex data protection operations. The method further enables the user to select a menu option, and executes the complex data protection operation associated with the menu option selected by the user. A corresponding system and computer program product are also disclosed.

Abstract: An apparatus, method and computer program product are disclosed. The apparatus includes a strategy module that determines restore information, writes the restore information into a restore information file, and writes the restore information file to a master volume containing target data; a snapshot module that creates a snapshot backup of the master volume; and a restoration module that restores the target data and restore information file, and restores application consistency of the target data. The method includes determining restore information, writing restore information to a file, writing the file to a volume containing data, backing up data by a snapshot backup of the volume, restoring data and the file, and restoring application consistency of the data. The computer program product comprises a computer readable storage medium that stores code to perform determining a backup strategy, backing up data, and restoring data.

Abstract: For efficient Flashcopy backup and a mount, clone, or restore task collision avoidance using dynamic volume allocation with reuse and from a shared resource pool, dynamically using a Flashcopy target volume for the Flashcopy backup from a global pool of Flashcopy backup target volumes shared by a plurality of device classes for avoiding a collision between the Flashcopy backup and the mount, the clone, or the restore task.

Abstract: For efficient Flashcopy backup and mount, clone, or restore collision avoidance with reuse using dynamic volume allocation, performing at least one attempt to reuse an existing FlashCopy target volume that is not currently being used for at least one of a mount task, a clone task, and a restore task at the same time for a FlashCopy backup. If the at least one attempt to reuse the existing FlashCopy target volume fails, dynamically allocate a new Flashcopy target volume for the Flashcopy backup.

Abstract: A new target volume for a new FlashCopy backup is dynamically allocated by performing at least one attempt to reuse an existing FlashCopy target volume containing older FlashCopy backups that have been previously ingested into a repository and are not currently being used as a source for at least one of a mount task, a clone task, and a restore task. If the at least one attempt to reuse the existing FlashCopy target volume fails, the new target volume is dynamically allocated from a global pool of FlashCopy backup target volumes.

Abstract: For efficient Flashcopy backup and a mount, clone, instant restore, and/or file level restore task collision avoidance using dynamic volume allocation with reuse and from a shared resource pool, performing at least one attempt to reuse an existing FlashCopy target volume in a Flashcopy chain of target volumes that is not currently being used for at least one of the mount task, the clone task, instant restore task, and/or file level restore task at the same time for a FlashCopy backup. If the at least one attempt to reuse the existing FlashCopy target volume fails, dynamically allocate a new Flashcopy target volume for the Flashcopy backup from a global pool of Flashcopy backup target volumes shared by a plurality of device classes.

Abstract: Dynamically allocates a new Flashcopy backup target volume within the single repository for executing a new Flashcopy backup to avoid a collision with one of a mount operation, a restore operation, and a clone operation when dynamically allocating the new Flashcopy target volume for the new Flashcopy backup.

Abstract: Dynamically reuse an existing Flashcopy target volume containing an older Flashcopy backup and a consistency group for one of a mount operation, a restore operation, and a clone operation.

Abstract: For efficient FlashCopy backup target volume allocation, a target volume is dynamically allocated for a new FlashCopy backup by reusing an existing FlashCopy target volume containing older FlashCopy backups that have been previously ingested into a repository and are not currently being used as a source for at least one of a mount task, a clone task, and a restore task.

Abstract: A collision is avoided between a new Flashcopy backup and an existing Flashcopy target volume containing an older Flashcopy backup being ingested during one of a mount operation, a restore operation, and a clone operation by dynamically allocating a new Flashcopy target volume for the new Flashcopy backup.

Abstract: Dynamically manages a creation and a destruction of a plurality of Flashcopy resources and the target volumes using configurable high-water marks and maximum values.

Abstract: Embodiments of the present invention provide efficient and cost-effective systems and methods for backing up and recovering a virtual machine and application data therein. Embodiments of the present invention can be used to satisfy near-zero RPOs by providing more recovery points for backups in virtual machine environments, while also providing increased granularity for recovery (i.e., single virtual disk, single file, etc.) and maintaining central management capabilities and back up efficiencies offered by virtual machine-level backups.

Abstract: Embodiments of the present invention provide efficient and cost-effective systems and methods for backing up and recovering a virtual machine and application data therein. Embodiments of the present invention can be used to satisfy near-zero RPOs by providing more recovery points for backups in virtual machine environments, while also providing increased granularity for recovery (i.e., single virtual disk, single file, etc.) and maintaining central management capabilities and back up efficiencies offered by virtual machine-level backups.

Abstract: Dynamically reuse from a global pool of allocated resources an existing Flashcopy target volume containing an older Flashcopy backup and a consistency group for one of a mount operation, a restore operation, and a clone operation when dynamically allocating a new Flashcopy target volume for the new Flashcopy backup.

Abstract: Upon an indication that a Flashcopy backup is not to be ingested, ingesting changed grains and/or a Flashcopy Map (fcmap) of the Flashcopy backup into a repository and dynamically marking the Flashcopy backup for collapse from a first repository into a second repository without breaking a flashcopy chain.

Abstract: Avoiding a collision between a new FlashCopy backup and an existing FlashCopy target volume containing an older FlashCopy backup being ingested into a repository by dynamically allocating a new FlashCopy target volume for the new FlashCopy backup.

Abstract: For efficient FlashCopy backup target volume allocation from a shared resource pool while ingesting a FlashCopy backup in a repository, for dynamically allocating a target volume for the new FlashCopy backup, a global pool of FlashCopy backup target volumes and a consistency group in the global pool of FlashCopy backup target volumes is maintained for use by a new FlashCopy backup upon encountering a collision while an existing FlashCopy target volume containing older FlashCopy backups are being ingested into the repository for dynamically allocating a target volume for the new FlashCopy backup.