Abstract: A method, apparatus, system, and computer program product for backing up data from a virtual machine. A backup service is presented by a computer system as a storage system to the virtual machine, wherein the storage system is located outside of the virtual machine. A hypervisor for the virtual machine is instructed by the computer system to present the storage system as a virtualized storage system to the virtual machine. Data is received by the computer system from the hypervisor in which the data is stored on the virtualized storage system by a backup client performing a backup operation in the virtual machine.

Abstract: Technology for storing legal hold data in the cloud (for example, in containers), where the source of the data stored in the cloud is independent backup copy(ies) that are maintained by an enterprise subject to a legal hold order. Changing the legal hold data as it is stored in the set of backup copy(ies) in a manner will not change the legal hold data as it is stored in the cloud. Mechanism may also be provided for auditing chain of custody and authenticating parties who request legal hold data to be delivered from cloud storage.

Abstract: A method, system, and program product for controlling power associated with connectivity between devices is provided. The method includes scheduling a copy function associated with copying data from a production hardware device to a secure hardware device at a specified time period. A first hardware connection between the production hardware device and a production network associated with the production hardware device is disabled during the specified time period and a second hardware connection between the production hardware device and the secure hardware device is enabled. A subsequent copy function is enabled for copying the data from the production hardware device to the secure hardware device. The second hardware connection between the production hardware device and the secure hardware device is disabled after the copy function has completed. In response, the first hardware connection between the production hardware device and the production network is enabled.

Abstract: A method, system, and computer program product manages a storage system. Writes to sections in solid state storage devices in endurance tiers in the storage system are monitored by a computer system over a period of time. Responsive to a write rate for the writes to a section in the sections in an current endurance tier in the endurance tiers exceeding a maximum recommended write rate for the current endurance tier during the period of time, data is moved from the section in the current endurance tier to a higher endurance tier in the endurance tiers having a higher maximum recommended write rate than the maximum recommended write rate for the current endurance tier.

Abstract: Cross backup application diskless data migration is provided. Legacy data backups eligible for migration are identified in a legacy backup environment. Application specific information regarding the legacy data backups eligible for migration is received. The application specific information is filtered to indicate only legacy backup data that must be migrated representing a type of migration desired. The application specific information corresponding to the legacy backup data that must be migrated is presented as a virtual filesystem mounted within an operating system such that the application specific information is seen as live local data. A backup of the virtual filesystem mounted within the operating system is performed.

Abstract: A method, system, and computer program product manages a storage system. Writes to sections in solid state storage devices in endurance tiers in the storage system are monitored by a computer system over a period of time. Responsive to a write rate for the writes to a section in the sections in an current endurance tier in the endurance tiers exceeding a maximum recommended write rate for the current endurance tier during the period of time, data is moved from the section in the current endurance tier to a higher endurance tier in the endurance tiers having a higher maximum recommended write rate than the maximum recommended write rate for the current endurance tier.

Abstract: A content-lifecycle management system (CLMS) intercepts a request to perform an action upon a data object in a domain of a multi-domain computing environment during a certain phase of the object's lifecycle. The CLMS retrieves data and rules from a cross-domain distributed ledger that is accessible throughout the multi-domain environment. The retrieved information includes content-lifecycle management policies that control which actors can perform certain types of actions upon specific data objects during various lifecycle phases. The ledger also describes and classifies actors, dependency relationships between storage and infrastructure components of the environment, and the results of past requests.

Abstract: A method, apparatus, system, and computer program product for deduplicating data. Data is stored by a computer system in storage domains in a storage system. Deduplication is performed by the computer system within each storage domain in the storage domains using a hash table that includes entries for all of the storage domains. Cross-deduplication between the storage domains is avoided in the storage system.

Abstract: A method, apparatus, system, and computer program product for backing up data from a virtual machine. A backup service is presented by a computer system as a storage system to the virtual machine, wherein the storage system is located outside of the virtual machine. A hypervisor for the virtual machine is instructed by the computer system to present the storage system as a virtualized storage system to the virtual machine. Data is received by the computer system from the hypervisor in which the data is stored on the virtualized storage system by a backup client performing a backup operation in the virtual machine.

Abstract: Cross backup application diskless data migration is provided. Legacy data backups eligible for migration are identified in a legacy backup environment. Application specific information regarding the legacy data backups eligible for migration is received. The application specific information is filtered to indicate only legacy backup data that must be migrated representing a type of migration desired. The application specific information corresponding to the legacy backup data that must be migrated is presented as a virtual filesystem mounted within an operating system such that the application specific information is seen as live local data. A backup of the virtual filesystem mounted within the operating system is performed.

Abstract: Provided are techniques for a headless resilient backup and restore software ecosystem. At a first backup server of a plurality of backup servers, a connection request is received. At the first backup server, a second backup server is identified by: determining a backup server score for each of the plurality of backup servers based on identification factors comprising historical client latency, scheduled backup server workload, and whether the metadata is already cached on any of the plurality of backup servers and identifying the second backup server as having a lowest backup server score. The identification of the second backup server is returned.

Abstract: A content-lifecycle management system (CLMS) intercepts a request to perform an action upon a data object in a domain of a multi-domain computing environment during a certain phase of the object's lifecycle. The CLMS retrieves data and rules from a cross-domain distributed ledger that is accessible throughout the multi-domain environment. The retrieved information includes content-lifecycle management policies that control which actors can perform certain types of actions upon specific data objects during various lifecycle phases. The ledger also describes and classifies actors, dependency relationships between storage and infrastructure components of the environment, and the results of past requests.

Abstract: A method, apparatus, system, and computer program product for deduplicating data. Data is stored by a computer system in storage domains in a storage system. Deduplication is performed by the computer system within each storage domain in the storage domains using a hash table that includes entries for all of the storage domains. Cross-deduplication between the storage domains is avoided in the storage system.

Abstract: Pre-fetching and staging restore data is provided. A set of data corresponding to a client device is collected from each respective data source in a plurality of data sources. A score is determined for each set of data collected. A probability of receiving a request to restore backup data on the client device is predicted based on analysis of the set of data from each respective data source and the score for each set of data. It is determined whether the predicted probability of receiving a request to restore the backup data on the client device is greater than a threshold. In response to determining that the predicted probability of receiving a request to restore the backup data on the client device is greater than the threshold, the backup data of the client device is preemptively moved to a fastest data storage tier in a multi-tiered backup data storage system.

Abstract: Provided are techniques for a headless resilient backup and restore software ecosystem. At a first backup server of a plurality of backup servers, a connection request is received. At the first backup server, a second backup server is identified by: determining a backup server score for each of the plurality of backup servers based on identification factors comprising historical client latency, scheduled backup server workload, and whether the metadata is already cached on any of the plurality of backup servers and identifying the second backup server as having a lowest backup server score. The identification of the second backup server is returned.

Abstract: Provided are techniques for a headless resilient backup and restore software ecosystem. At a first backup server of a plurality of backup servers, a connection request is received. At the first backup server, a second backup server is identified by: determining a backup server score for each of the plurality of backup servers based on identification factors comprising historical client latency, scheduled backup server workload, and whether the metadata is already cached on any of the plurality of backup servers and identifying the second backup server as having a lowest backup server score. The identification of the second backup server is returned.

Abstract: Provided are techniques for a headless resilient backup and restore software ecosystem. At a first backup server of a plurality of backup servers, a connection request is received. At the first backup server, a second backup server is identified by: determining a backup server score for each of the plurality of backup servers based on identification factors comprising historical client latency, scheduled backup server workload, and whether the metadata is already cached on any of the plurality of backup servers and identifying the second backup server as having a lowest backup server score. The identification of the second backup server is returned.