Abstract: Dynamically creates a cloned target volume by cloning a production volume without breaking a Flashcopy chain for continuing an ingestion of a Flashcopy backup target volume.

Abstract: Methods, computing systems and computer program products implement embodiments of the present invention that include configuring a first storage system to mirror first storage regions to corresponding second storage regions in a second storage system via a first data connection, and to mirror the first storage regions to corresponding third storage regions in a third storage system via a second data connection. Upon the second storage system receiving, subsequent to detecting a failure of the first storage system, a host I/O request to retrieve data from a given second storage region and determining that the respective timestamp of the corresponding third storage region on the third storage system is more recent than the respective timestamp of the given second storage region on the second storage system, the second storage system retrieves, via a third data connection, the data from the corresponding third storage region on the third storage system.

Abstract: Dynamically allocates a new target volume and a Flashcopy map (fcmap) for ingest upon one of a mount operation and a clone operation breaking a FlashCopy chain for creating a stable FlashCopy Map (fcmaps) for ingest while a Flashcopy backup is mounted.

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: Methods, computing systems and computer program products implement embodiments of the present invention that include configuring distributed storage system resources for a distributed storage system. Examples of the storage system resources include a plurality of network segments, one or more network devices coupled to the network, and multiple nodes coupled to the network, the nodes including both frontend and backend nodes. Upon receiving, by a given frontend node in the distributed storage system, an input/output (I/O) request, one or more of the distributed storage system resources required to process the I/O request are identified, and a respective load that the I/O request will generate on each of the identified distributed storage system resources is calculated. The distributed storage system processes the I/O request upon detecting that the respective loads are less than respective available capacities of the identified distributed storage system resources.

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.

Abstract: In a hash-based multi-tenancy in a deduplication system, incorporating, as if part of input data, a tenant identification (ID) into a hash value calculation using a single hash based index table for separating data segments in a multi-tenant deduplication system.

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: 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: 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: 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: Dynamically allocates a new target volume and a Flashcopy map (fcmap) for ingest upon one of a mount operation and a clone operation breaking a FlashCopy chain for creating a stable FlashCopy Map (fcmaps) for ingest while a Flashcopy backup is mounted.

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 creates a cloned target volume by cloning a production volume without breaking a Flashcopy chain for continuing an ingestion of a FlashCopy backup target volume.

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.

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: 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: 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: 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 method and circuit for recovering a clock signal in a receiving station, wherein the receiving station receives packets carrying timing information” (TI) from a transmitting station over a packet switched network, the TI relating to a reference timing source located over the network. The method comprises the steps of: calculating over time, in the receiving station, a “TI Delay” variable based on a relative time difference between a timestamp assigned to a sample of a clock signal generated in the receiving station and the TI; upon detecting a Delay Deviation in the TI Delay, accumulating the Delay Deviation in an “Accumulated Deviation” variable; subtracting the Accumulated Deviation from the TI Delay; adjusting the frequency of the clock signal based on the TI Delay; and upon detecting that the Accumulated Deviation absolute value is smaller than a Zeroing Threshold, zeroing the Accumulated Deviation before subtracting it from the TI Delay.