An illustrative data storage management system enables a Tenant to retain control over criteria for protecting the Tenant's data, and hides details of the Service Provider's infrastructure. The Service Provider may have many data centers, each one represented within the system by a Resource Pool with attributes that reflect the infrastructure resources of the corresponding data center. A system analysis, which is triggered by the Tenant's choices for data protection, keys in on a suitable Resource Pool. The system analysis identifies suitable system resources within the Resource Pool and associates them to the data source. Subsequent data protection jobs invoke proper system components based on the associations created by the system analysis. In some embodiments, the system will invoke infrastructure resources created on demand when a data protection job is initiated rather than being pre-existing resources.

A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

A method and system for backup processes that includes identifying a target volume and identifying a number of available threads to back up the target volume. The elements in the target volume are distributed among the available threads based on a currently pending size of data in the threads. The elements are stored from each thread into a backup container, and merged from each of the backup containers into a backup volume.

Multiple data paths may be available to a data management system for transferring data between a primary storage device and a secondary storage device. The data management system may be able to gain operational advantages by performing load balancing across the multiple data paths. The system may use application layer characteristics of the data for transferring from a primary storage to a backup storage during data backup operation, and correspondingly from a secondary or backup storage system to a primary storage system during restoration.

Various systems and methods are provided in which a replication process is initiated between a primary site and a recovery site, each having plurality of gateway appliances. Replication loads are evaluated for each given gateway appliance of the plurality of gateway appliances. If a determination is made that at least one gateway appliance of the plurality of gateway appliances is not overloaded, the plurality of gateway appliances are sorted based on replication loads respectively associated with each gateway appliance, and a determination is made as to whether a relative difference in replication loads between a gateway appliance having a highest replication load and a gateway appliance having a lowest replication load exceeds a difference threshold to determine whether the replication workloads between the gateway appliances should be rebalanced.

The present invention provides systems and methods for data storage. A hierarchical storage management architecture is presented to facilitate data management. The disclosed system provides methods for evaluating the state of stored data relative to enterprise needs by using weighted parameters that may be user defined. Also disclosed are systems and methods evaluating costing and risk management associated with stored data.

A method of forming a vertical transistor includes forming a fin structure on a substrate, forming a gate structure on the fin structure, and forming a bottom source/drain (S/D) region on the fin structure, such that an air gap is formed between the bottom S/D region and the gate structure.

Some examples described herein relate to data restoration. In an example, checkpoints may be defined for converting backup data stored in each of Logical Unit Numbers (LUNs) of a storage system into respective virtual data disk files. Backup data stored in each of the LUNs of the storage system may be converted into respective virtual data disk files at the defined checkpoints. The virtual data disk files with user configuration information of the storage system may be packaged into a Virtual Storage Appliance (VSA), which may include a base operating system (OS) image of the VSA. The VSA may be transferred to an external entity.

One example method includes gathering respective performance data concerning each asset in a group of assets, clustering the performance data so as to define a first cluster and a second cluster, and data assets in the first cluster are assigned a HIGH RISK label and data assets in the second cluster are assigned a LOW RISK label, assigning a respective risk score to each of the assets, and the risk score includes a quantified risk level for the asset to which the risk score has been assigned, ranking the assets with the HIGH RISK label according to their respective risk scores, and backing up a ranked asset based on an IO volume associated with that ranked asset.

Multiple data paths may be available to a data management system for transferring data between a primary storage device and a secondary storage device. The data management system may be able to gain operational advantages by performing load balancing across the multiple data paths. The system may use application layer characteristics of the data for transferring from a primary storage to a backup storage during data backup operation, and correspondingly from a secondary or backup storage system to a primary storage system during restoration.