Abstract: An illustrative efficient failover process and system in virtualized environment to reduce costs and resources associated with maintaining live stand-by failover scheduling and maintenance system is described herein. The illustrative embodiment uses incremental backup data to maintain a failover or passive virtualized computing platforms comprising of one or more virtual machines that are configured to and ready to be scaled up and initiated to take over the tasks and operations of a lost storage manager. Each virtualized failover or passive node is initially configured to use minimal computing resources to maintain a live backup of the active storage manager. During a failover, a passive virtual node will initiate the failover process. In an embodiment, the failover process comprises restoring a secondary copy of the lost storage manager, initiating a scale up process to increase computing resources, and continuing scheduled tasks and operations of the lost storage manager.

Abstract: An illustrative air-gapped data storage site for storing secure copies at the air-gapped storage site. Using specialized air-gapped media agents installed within the air-gapped storage pool site, the illustrative system, at an unpredictable time, establishes a one-way tunnel from secondary storage site to air-gapped site to receive backup copies of the data stored at primary site. In another embodiment, during disaster recovery, backup copies stored within the air-gapped site are replicated to a non-air gapped site (e.g., secondary storage pools) as “tertiary copies.” Those copies are then restored to the primary site in original application data formats for quick recovery. As restoration of data is complete, the tertiary copies are promoted to “secondary copies” to receive incremental backups.

Abstract: A data storage management system is enhanced to accommodate, and moreover to optimize, the storing and retention of deduplicated secondary copies at write-once read-many (WORM) enabled storage platforms. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy (e.g., deduplication copy, backup) operations; and pruning changes. The storage manager is generally responsible for managing the creation, tracking, and deletion of secondary copies, with and without deduplication. Media agents that store secondary copies to and prune them from the WORM-enabled storage platforms also are enhanced for communicating and interoperating with both bucket-level and object-level WORM-enabled storage platforms to implement the features disclosed herein.

Abstract: As the volume of data under management expands rapidly, so do the costs associated with storing and that data on secondary storage devices. The illustrative approach provides an improvement to the information management system by delaying certain tasks that meet a set of criteria until a specified threshold is met. The system receives a request to be performed on a set of data stored on secondary devices. Power management module determines whether the task satisfies a set of criteria for delayed execution, queues the task, and when a specified threshold of the queued tasks is met powers up the necessary components to execute the tasks.

Abstract: An information management system implements a media agent that communicates with a network area storage (NAS) device to receive secondary copy data that has been backed-up by the NAS. The secondary copy data may include primary data managed or maintained by the NAS. The secondary copy data may be in a proprietary format or other data format specific to the NAS. The NAS may prepare metadata or other information about the secondary copy data that informs the media agent as to the contents of the secondary copy data. The media agent may segment the secondary copy data into one or more backup chunks for storing in a secondary storage device. In addition, each of the backup chunks may be associated with backup chunk metadata, where the backup chunk metadata includes information that describes certain information stored by a corresponding backup chunk.

Abstract: As the volume of data under management expands rapidly, so do the costs associated with storing and that data on secondary storage devices. The illustrative approach provides an improvement to the information management system by delaying certain tasks that meet a set of criteria until a specified threshold is met. The system receives a request to be performed on a set of data stored on secondary devices. Power management module determines whether the task satisfies a set of criteria for delayed execution, queues the task, and when a specified threshold of the queued tasks is met powers up the necessary components to execute the tasks.