Abstract: Embodiments for migrating hash values for backup data blocks in a network of data protection targets (DPTs) and a common data protection target implementing a Gold image library management system in which backups of Gold images used as templates for physical machines and virtual machines are stored on the CDPT. The CDPT and each DPT stores backup data split into chunks that are uniquely identified by a respective hash of its contents, and maintains data structures comprising the hash, chunk size, chunk data, and a list of DPT and CDPT identifiers. The hashes are partitioned into a set of buckets in the CDPT. A Bloom filter is generated for each bucket of hashes, and stored in each DPT so that each DPT stores Bloom filters for all CDPTs in the network. Each DPT checks its list of hashes against the Bloom filters in each of the DPTs to determine whether to keep or free chunks of data.

Abstract: Automatically updating operating system and application programs in a large-scale network using Gold image data. An asset update process receives validation by a user for use of an updated program comprising new Gold image data. The process automatically updates the previous version of the updated version with the updated program to generate new user content data, without requiring further user intervention by using a defined tag linking the new Gold image data with previous Gold image data for the older version of the program. The Gold image data is stored in a central data protection target storage separate from data protection target storage for the user content data.

Abstract: Embodiments provide for a primary storage array having multiple storage tiers. The multiple storage tiers include one or more performance tiers and at least one deduplicated storage tier storing deduplicated data. One embodiment provides for a data storage system including the storage array and an I/O engine to manage I/O requests for the storage array. The data storage system additionally includes a virtual execution environment to execute a virtual backup engine, the virtual backup engine to generate backup data for the one or more storage tiers of primary storage and deduplicate the backup data and a resource manager to manage a resource allocation to the virtual backup engine based on a hint received from the virtual backup engine, the hint associated with a backup operation that has a characterization selected from a set including computationally intensive and I/O intensive.

Abstract: Reducing backup data by providing a data protection target for storing content data from clients running operating system and applications, and a common data protection target (CDPT) separate from the data protection target for storing Gold image data for the operating system and applications. During backup, user content data is copied from the client to the data protection target, and Gold image data is copied to the CDPT. It is also referenced in the DP target to prevent redundant storage. During backup, the CDPT is queried to determine if the Gold image exists, and if so, the DP target does not store the Gold image data in the DP target, but uses the reference to indicate the location of the Gold image data corresponding to the backed up content data. During a restore, the restore stream is built from the DP target and CDPT to combine user content data and Gold image data.

Abstract: Reducing backup data by providing a data protection target for storing content data from clients running operating system and applications, and a common data protection target (CDPT) separate from the data protection target for storing Gold image data for the operating system and applications. Gold image data is stored by a user in a defined location or tagged with a defined tag. The stored or tagged Gold image data is identified by the backup software and copied to the CDPT. The identified Gold image data is cataloged. During backup, the CDPT is queried to determine if the Gold image exists, and if so, the DP target does not store the Gold image data in the DP target, but uses the reference to indicate the location of the Gold image data corresponding to the backed up content data. During a restore, the restore stream is built from the DP target and CDPT to combine user content data and Gold image data.

Abstract: Embodiments for migrating hash values for backup data blocks in a network of data protection targets (DPTs) and a common data protection target implementing a Gold image library management system in which backups of Gold images used as templates for physical machines and virtual machines are stored on the CDPT. The CDPT and each DPT stores backup data split into chunks that are uniquely identified by a respective hash of its contents, and maintains data structures comprising the hash, chunk size, chunk data, and a list of DPT and CDPT identifiers. The hashes are partitioned into a set of buckets in the CDPT. A Bloom filter is generated for each bucket of hashes, and stored in each DPT so that each DPT stores Bloom filters for all CDPTs in the network. Each DPT checks its list of hashes against the Bloom filters in each of the DPTs to determine whether to keep or free chunks of data.

Abstract: Reducing backup data by providing a data protection target for storing content data from clients running operating system and applications, and a common data protection target (CDPT) separate from the data protection target for storing Gold image data for the operating system and applications. During backup, user content data is copied from the client to the data protection target, and Gold image data is copied to the CDPT. It is also referenced in the DP target to prevent redundant storage. During backup, the CDPT is queried to determine if the Gold image exists, and if so, the DP target does not store the Gold image data in the DP target, but uses the reference to indicate the location of the Gold image data corresponding to the backed up content data. During a restore, the restore stream is built from the DP target and CDPT to combine user content data and Gold image data.

Abstract: Facilitating efficient copy reuse of point-in-time (PIT) backup data in a data storage system by providing a data protection target (DPT) for storing user the PIT backup data, and a common data protection target (CDPT) accessible to but separate from the data protection target for storing Gold image data comprising structural data for operating system and application programs as defined by a manufacturer and different from the backed user content data. A Gold image copy reuse coordinator component or process receives a selection of a Gold image to be combined with a specified PIT backup dataset, and combines the specified PIT backup dataset with the selected Gold image to form a synthetic copy of the specified PIT backup dataset stored in the DPT. The synthetic copy can then be exposed to a system through a file share protocol for reuse by a user.

Abstract: Automatically updating operating system and application programs in a large-scale network using Gold image data. An asset update process receives validation by a user for use of an updated program comprising new Gold image data. The process automatically updates the previous version of the updated version with the updated program to generate new user content data, without requiring further user intervention by using a defined tag linking the new Gold image data with previous Gold image data for the older version of the program. The Gold image data is stored in a central data protection target storage separate from data protection target storage for the user content data.

Abstract: Reducing backup data by providing a data protection target for storing content data from clients running operating system and applications, and a common data protection target (CDPT) separate from the data protection target for storing Gold image data for the operating system and applications. Gold image data is stored by a user in a defined location or tagged with a defined tag. The stored or tagged Gold image data is identified by the backup software and copied to the CDPT. The identified Gold image data is cataloged. During backup, the CDPT is queried to determine if the Gold image exists, and if so, the DP target does not store the Gold image data in the DP target, but uses the reference to indicate the location of the Gold image data corresponding to the backed up content data. During a restore, the restore stream is built from the DP target and CDPT to combine user content data and Gold image data.

Abstract: In a storage system in which a storage array accesses cloud storage via a cloud gateway, the cloud gateway provides signals to control data rate between the storage array and the cloud. The signals may include commands to reduce or stop all volume streams or a select subset of volume streams. Data rate may be controlled on the basis of available buffering capacity of the cloud gateway and available bandwidth between the cloud gateway and cloud storage. The signals may be SCSI VU commands, where the cloud gateway is a SCSI initiator and the storage array is a SCSI target.

Abstract: In a data processing system having multiple production hosts, each with a backup agent, interfaced to a storage array and to a backup server, an array I/O priority engine on the storage array establishes and enforces I/O priorities for I/O backup and production communications with the array to ensure that backup does not consume a disproportionate CPU processing and array bandwidth load or disrupt more critical production processing.

Abstract: Embodiments are described for a multi-node file system, such as a clustered or distributed file system, with a file system buffer cache and an additional host-side tier non-volatile storage cache such as 3DXP storage. Cache coherency can be maintained by one of three models: (i) host-side tier management, (ii) file system management, or (iii) storage array management. performing a storage tier-specific file system action in a file system that comprises a namespace that spans multiple tiers of storage.

Abstract: Systems and methods for scheduling multiple flows in a computing system or for allocating resources to the flows in the computing system. Each flow may be associated with a target priority and a target performance. A current priority can be determined for each flow and resources are allocated based on the highest current priority. Over time, the current priorities change and each flow will receive resources as the flows are scheduled for execution. No flow is starved of resources.

Abstract: In a data processing system having multiple production hosts, each with a backup agent, interfaced to a storage array and to a backup server, an array I/O priority engine on the storage array establishes and enforces I/O priorities for I/O backup and production communications with the array to ensure that backup does not consume a disproportionate CPU processing and array bandwidth load or disrupt more critical production processing.

Abstract: A storage system may include an interface configured to connect with a mainframe computing system. The interface converts the protocol used by the mainframe computing system to another protocol. Once the data, which may be present in a backup data stream, from the mainframe computing system is converted, the storage system may direct or transmit the backup data stream for further processing such as deduplication and/or compression. The de-duplicated and/or compressed backup data stream is then stored to storage of the storage system.

Abstract: In a data processing system having multiple production hosts, each with a backup agent, interfaced to a storage array and to a backup server, an array I/O priority engine on the storage array establishes and enforces I/O priorities for I/O backup and production communications with the array to ensure that backup does not consume a disproportionate CPU processing and array bandwidth load or disrupt more critical production processing.

Abstract: Embodiments provide for a primary storage array having multiple storage tiers. The multiple storage tiers include one or more performance tiers and at least one deduplicated storage tier storing deduplicated data. One embodiment provides for a data storage system including management logic to manage the deduplicated storage tier. The management logic can receive a request to store deduplicated data and respond to the request to store the deduplicated data based on workload statistics associated with the data. In one embodiment the response to the request includes storing at least a portion of the deduplicated data to a first storage device in the second set of storage devices and the workload statistics include input/output (I/O) statistics associated with the unit of deduplicated data. In other embodiments the response includes reallocating drives between storage tiers and/or providing migration hints with respect to data on the deduplicated storage tier.

Abstract: Embodiments provide for a primary storage array having multiple storage tiers. The multiple storage tiers include one or more performance tiers and at least one deduplicated storage tier storing deduplicated data. One embodiment provides for a data storage system including a first storage tier including a first set of storage devices; a second storage tier including a second set of storage devices, the second storage tier including deduplicated data; and a quality of service (QoS) manager to manage data migration between the first storage tier and the second storage tier, the QoS manager to maintain deduplication statistics for the deduplicated data, wherein the QoS manager, based on the deduplication statistics, is to partially migrate a data extent between the first storage tier and the second storage tier, the data extent including data stored at a range of storage addresses.

Abstract: A backup engine of a first storage system receives a request to perform a backup session from the first storage system to a second storage system based on a backup service level objective (SLO) that has been configured for the backup session. In response to the request, it is determined that a first backup resource allocated for the backup session by the first storage system cannot satisfy the SLO based on statistics of prior backup sessions in view of characteristics of the backup session to be performed. A dynamic resource allocation (DRA) module is to dynamically perform a first DRA to modify the first backup resource to satisfy the SLO. The backup engine then initiates the backup session by transmitting backup data from the first storage system to the second storage system using the modified first backup resource.