Patent application number | Description | Published |
20080243954 | GENERATING AND INDICATING INCREMENTAL BACKUP COPIES FROM VIRTUAL COPIES OF A DATA SET - Provided are a method, system, and program for generating and indicating incremental backup copies from virtual copies of a data set. A virtual copy operation is initiated to create a virtual copy of a data set, wherein the virtual copy represents the data set at a point-in-time copy, and wherein the virtual copy is completed without transferring the data set to a backup location. An incremental backup operation is initiated with respect to an identified virtual copy, wherein the incremental backup operation copies changes to the data set that occur since a most recent creation of an incremental backup set. | 10-02-2008 |
20090187908 | OPTIMIZED METHODOLOGY FOR DISPOSITIONING MISSED SCHEDULED TASKS - The present invention provides for a method and system for the disposition of tasks which failed to run during their originally scheduled time. The determination of whether to run missed or delayed tasks is based on calculated ratios rather than on fixed window sizes. A Lateness Ratio is calculated to determine if the time elapsed between the missed task and the scheduled run time is small enough to still allow a late task to run. A Closeness Ratio is calculated to determine if the next available run time for the missed task is close enough to the next scheduled execution of the task that the missed task will be run in place of the upcoming scheduled task. Each ratio is compared to a user defined ratio limit, so if the calculated ratio does not exceed the limit, then the missed task is executed at the first available opportunity. | 07-23-2009 |
20100223233 | MANAGEMENT OF REDUNDANT OBJECT IN STORAGE SYSTEMS - Provided are a method, system, and article of manufacture wherein one client node is selected from a plurality of client nodes. A determination is made that an object corresponding to a client node has to be stored. A determination is made as to whether the object has already been stored in the server node by the one selected client node. The object is stored at the server node, in response to determining that the object has not already been stored in the server node by the one selected client node. | 09-02-2010 |
20110113015 | MANAGEMENT OF REDUNDANT OBJECTS IN STORAGE SYSTEMS - Provided are a method, system, and article of manufacture wherein one client node is selected from a plurality of client nodes. A determination is made that an object corresponding to a client node has to be stored. A determination is made as to whether the object has already been stored in the server node by the one selected client node. The object is stored at the server node, in response to determining that the object has not already been stored in the server node by the one selected client node. | 05-12-2011 |
20150046402 | DATA BACKUP ACROSS PHYSICAL AND VIRTUALIZED STORAGE VOLUMES - Machines, systems and methods for backing up data, the method comprising retrieving identifying information about target data storage volumes from which target data is to be backed up; communicating the identifying information to a proxy application installed on a backup computing system utilized to backup the target data stored on the target data storage volumes, wherein the proxy application uses the identifying information to place the target data storage volumes in a first state in which write operations may not be performed to the target data storage volumes, wherein the proxy application causes snapshots to be taken of the target data storage volumes of a first type and a second type, in response to determining that the target data storage volumes are placed in the first state. | 02-12-2015 |
20150286424 | MARKING A FLASHCOPY BACKUP FOR COLLAPSE WITHOUT BREAKING A FLASHCOPY CHAIN - 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. | 10-08-2015 |
20150286425 | EFFICIENT FLASHCOPY BACKUP TARGET VOLUME ALLOCATION - 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. | 10-08-2015 |
20150286426 | EFFICIENT USE OF FLASHCOPY RESOURCES AND TARGET VOLUMES FOR DYNAMIC TARGET VOLUME ALLOCATION - 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. | 10-08-2015 |
20150286428 | COLLISION AVOIDANCE USING DYNAMIC TARGET VOLUME ALLOCATION FROM A SHARED RESOURCE POOL - 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. | 10-08-2015 |
20150286429 | EFFICIENT FLASHCOPY BACKUP AND MOUNT, CLONE, OR RESTORE COLLISION AVOIDANCE USING DYNAMIC VOLUME ALLOCATION WITH REUSE - 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. | 10-08-2015 |
20150286430 | EFFICIENT FLASHCOPY BACKUP AND MOUNT, CLONE, OR RESTORE COLLISION AVOIDANCE USING DYNAMIC VOLUME ALLOCATION FROM A SHARED RESOURCE POOL - 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. | 10-08-2015 |
20150286431 | EFFICIENT FLASHCOPY BACKUP AND MOUNT, CLONE, OR RESTORE COLLISION AVOIDANCE USING DYNAMIC VOLUME ALLOCATION WITH REUSE AND FROM A SHARED RESOURCE POOL - 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. | 10-08-2015 |
20150286432 | EFFICIENT FLASHCOPY BACKUP TARGET VOLUME ALLOCATION FROM A SHARED RESOURCE POOL - 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. | 10-08-2015 |
20150286433 | EFFICIENT FLASHCOPY BACKUP TARGET VOLUME ALLOCATION FROM A SHARED RESOURCE POOL WHILE INGESTING A FLASHCOPY BACKUP IN A REPOSITORY - 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. | 10-08-2015 |
20150286434 | COLLISION AVOIDANCE USING DYNAMIC TARGET VOLUME ALLOCATION IN A SINGLE REPOSITORY - 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. | 10-08-2015 |
20150286540 | COLLISION AVOIDANCE USING DYNAMIC TARGET VOLUME ALLOCATION - 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. | 10-08-2015 |
20150286541 | COLLISION AVOIDANCE USING DYNAMIC VOLUME ALLOCATION WITH REUSE - 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. | 10-08-2015 |
20150286542 | EFFICIENT FLASHCOPY BACKUP TARGET VOLUME ALLOCATION WITH REUSE AND A SHARED RESOURCE POOL - 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. | 10-08-2015 |