Abstract: An illustrative “VM heartbeat monitoring network” of heartbeat monitor nodes monitors target VMs in a data storage management system. Accordingly, target VMs are distributed and re-distributed among illustrative worker monitor nodes according to preferences in an illustrative VM distribution logic. Worker heartbeat monitor nodes use an illustrative ping monitoring logic to transmit special-purpose heartbeat packets to respective target VMs and to track ping responses. If a target VM is ultimately confirmed failed by its worker monitor node, an illustrative master monitor node triggers an enhanced storage manager to initiate failover for the failed VM. The enhanced storage manager communicates with the heartbeat monitor nodes and also manages VM failovers and other storage management operations in the system. Special features for cloud-to-cloud failover scenarios enable a VM in a first region of a public cloud to fail over to a second region.

Abstract: According to certain aspects, a method can include creating a backup copy of data associated with a virtual machine (VM) on one or more secondary storage devices, wherein the backup copy includes corresponding secondary copies of a plurality of files associated with the VM; analyzing metadata associated with the secondary copies to determine which of the plurality files are eligible to be removed from the primary storage device; in response determining that one or more files are eligible to be removed from the primary storage device, for respective file of the one or more files: determining whether the respective file has been changed since a first time at which the backup copy of the data associated with the VM was created; in response to determining that the respective file has not changed since the first time, removing the respective file; and adding a file placeholder for the removed file.

Abstract: Software, firmware, and systems are described herein that migrate functionality of a source physical computing device to a destination physical computing device. A non-production copy of data associated with a source physical computing device is created. A configuration of the source physical computing device is determined. A configuration for a destination physical computing device is determined based at least in part on the configuration of the source physical computing device. The destination physical computing device is provided access to data and metadata associated with the source physical computing device using the non-production copy of data associated with the source physical computing device.

Abstract: According to certain aspects, a method can include, at a first time, performing an incremental backup of first data associated with a virtual machine (VM) residing on a source client computing device from the source client computing device to one or more secondary storage devices to create a backup copy of the VM, where the VM is associated with a hypervisor of a first type; receiving an instruction to restore the first data associated with the VM from the one or more secondary storage devices; retrieving the first data from the one or more secondary storage devices; and applying the first data to second data associated with a replicated VM running on the destination client computing device, where the replicated VM is a replicated version of the VM, and where the second data corresponds to data of the VM at a time before the first time.

Abstract: A data storage system protects data identified for deletion which has been created or modified between scheduled data backups. For instance, the system monitors data operations and when the data operation is a delete, the system determines whether the data identified for deletion has been protected by a backup operation. Data that has not been backed up, such as newly created data, is copied to temporary storage before deletion. When the data has been protected, the system determines whether the data has been modified after the backup operation. Data modified after the backup operation is copied to temporary storage before deletion.

Abstract: Described in detail herein is a method of copying data of one or more virtual machines being hosted by one or more non-virtual machines. The method includes receiving an indication that specifies how to perform a copy of data of one or more virtual machines hosted by one or more virtual machine hosts. The method may include determining whether the one or more virtual machines are managed by a virtual machine manager that manages or facilitates management of the virtual machines. If so, the virtual machine manager is dynamically queried to automatically determine the virtual machines that it manages or that it facilitates management of. If not, a virtual machine host is dynamically queried to automatically determine the virtual machines that it hosts. The data of each virtual machine is then copied according to the specifications of the received indication.

Abstract: A data storage system backs up or protects virtual machines. For instance, the system identifies the different virtual machines executing in the system and provides a number of factors that can be used to create a backup policy. The system further creates specific rules for virtual machine backup policies using a user interface with drop down boxes of relevant criteria and Boolean operators. A preview of included virtual machines allows the rule to be refined. Particular virtual machines can be excluded during the preview. The system further dynamically updates the list of virtual machines satisfying the rules at time of backup.

Abstract: An illustrative “VM heartbeat monitoring network” of heartbeat monitor nodes monitors target VMs in a data storage management system. Accordingly, target VMs are distributed and re-distributed among illustrative worker monitor nodes according to preferences in an illustrative VM distribution logic. Worker heartbeat monitor nodes use an illustrative ping monitoring logic to transmit special-purpose heartbeat packets to respective target VMs and to track ping responses. If a target VM is ultimately confirmed failed by its worker monitor node, an illustrative master monitor node triggers an enhanced storage manager to initiate failover for the failed VM. The enhanced storage manager communicates with the heartbeat monitor nodes and also manages VM failovers and other storage management operations in the system. Special features for cloud-to-cloud failover scenarios enable a VM in a first region of a public cloud to fail over to a second region.

Abstract: Virtualization sprawl can lead to virtual machines with no designated periodic backup. If the data associated with these unprotected virtual machines is not backed up, it cannot be restored if needed, leading to system failures. A data storage system identifies and protects the unprotected virtual machines. For instance, the system compares a list of virtual machines with a list of computing devices having a designated backup policy in the data storage system and determines which of the virtual machines are unprotected. The system further automatically categorizes the unprotected virtual machines, identifies those unprotected virtual machines that remain uncategorized, and applies a default backup policy to the uncategorized and unprotected virtual machines to provide protected virtual machines.

Abstract: Systems and methods integrate disparate backup devices with a unified interface. In certain examples, a management console manages data from various backup devices, while retaining such data in its native format. The management console can display a hierarchical view of the client devices and/or their data and can further provide utilities for processing the various data formats. A data structure including fields for storing both metadata common to the client device data and value-added metadata can be used to mine or process the data of the disparate client devices. The unified single platform and interface reduces the need for multiple data management products and/or customized data utilities for each individual client device and provides a single pane of glass view into data management operations. Integrating the various types of storage formats and media allows a user to retain existing storage infrastructures and further facilitates scaling to meet long-term management needs.

Abstract: An information management system according to certain aspects may be configured to generate a snapshot of data relating to a plurality of applications. The system may include a plurality of data agents, wherein each data agent is associated with at least one of a plurality of applications, and data generated by the plurality of applications is stored in a logical volume in primary storage. The system may also include a snapshot manager configured to detect the plurality of applications; check with the plurality of data agents whether the associated applications are in consistent states; obtain a snapshot of the logical volume in response to receiving notifications from the plurality of data agents that the associated applications are in consistent states; and generate mapping information between a particular one of the plurality of applications and a portion of the snapshot relating to the particular one of the plurality of applications.

Abstract: According to certain aspects, a method can include creating a backup copy of data associated with a virtual machine (VM) on one or more secondary storage devices, wherein the backup copy includes corresponding secondary copies of a plurality of files associated with the VM; analyzing metadata associated with the secondary copies to determine which of the plurality files are eligible to be removed from the primary storage device; in response determining that one or more files are eligible to be removed from the primary storage device, for respective file of the one or more files: determining whether the respective file has been changed since a first time at which the backup copy of the data associated with the VM was created; in response to determining that the respective file has not changed since the first time, removing the respective file; and adding a file placeholder for the removed file.

Abstract: According to certain aspects, a system includes a client device that includes a virtual machine (VM) executed by a hypervisor, a driver located within the hypervisor, and a data agent. The VM may include a virtual hard disk file and a change block bitmap file. According to some embodiments the driver intercepts write operations generated by the VM to store data in a sector, determines an identity of the sector based on the intercepted write operation, determines an entry in the change block bitmap file that corresponds with the first sector, and modifies the entry in the change block bitmap file to indicate that data in that sector has changed. The data agent may generate an incremental backup of the VM based on the change block bitmap file in response to an instruction from a storage manager, where the incremental backup includes the data in the sector where data was modified.

Abstract: The disclosed systems and methods enable a virtual machine, including any applications executing thereon, to quickly start executing and servicing users based on pre-staged data blocks supplied from a backup copy in secondary storage. Substantially concurrently with the ongoing execution of the virtual machine, a virtual-machine-file-relocation operation may move data blocks originating in the backup copy to a primary storage destination that becomes the virtual machine's primary data store after the relocation operation completes. An enhanced data agent, operating in conjunction with an enhanced media agent in a storage management system, coordinates restoring of the virtual machine and the launch of the relocation operation. The enhanced media agent may pre-stage certain backed up data blocks which may be needed to launch the virtual machine, based on predictive analysis pertaining to the virtual machine's operational profile.

Abstract: A system and method for using a snapshot as a data source is described. In some cases, the system stores a snapshot and an associated data structure or index to storage media to create a secondary copy of a volume of data. In some cases, the associated index includes application specific data about a file system or other application that created the data to identify the location of the data. The associated index may include three entries, and may be used to facilitate the recovery of data via the snapshot.

Abstract: Embodiments disclosed herein include systems and processes for replicating one or more user computing systems of an information management system at an external resource system to create a backup or fallback of the user computing systems. Replicating the user computing systems may include replicating data as well as the applications, operating systems and configuration of the user computing systems. This replicated or fallback user computing system may be implemented on a virtual machine at the external resource system. Thus, if a user computing system becomes inaccessible, a new user computing system can be generated based on the backup copy of the user computing system at the external resource system. Further, in some embodiments, the copy of the user computing system may be interacted with at the external resource system. Thus, certain embodiments disclosed herein can be used to transition an information management system to an external resource system.

Abstract: According to certain aspects, a system includes a client device that includes a virtual machine (VM) executed by a hypervisor, a driver located within the hypervisor, and a data agent. The VM may include a virtual hard disk file and a change block bitmap file. The driver may intercept a first write operation generated by the VM to store data in a first sector, determine an identity of the first sector based on the intercepted write operation, determine an entry in the change block bitmap file that corresponds with the first sector, and modify the entry in the change block bitmap file to indicate that data in the first sector has changed. The data agent may generate an incremental backup of the VM based on the change block bitmap file in response to an instruction from a storage manager, where the incremental backup includes the data in the first sector.

Abstract: Systems and methods enable a virtual machine, including applications executing thereon, to quickly start executing and servicing users based on pre-staged data blocks supplied from a backup copy in secondary storage. Substantially concurrently with the ongoing execution of the virtual machine, a virtual-machine-file-relocation operation moves data blocks from backup to a primary storage destination that becomes the virtual machine's primary data store after relocation completes. An enhanced data agent, operating in conjunction with an enhanced media agent in a storage management system, coordinates restoring the virtual machine and launching the relocation operation. The enhanced media agent pre-stages certain backed up data blocks based on predictive analysis pertaining to the virtual machine's operational profile. The enhanced media agent also pre-stages backed up data blocks for the relocation operation, based on the operation's relocation scheme.

Abstract: Virtual machine (VM) proliferation may be reduced by determining the availability of existing VMs to perform a task. Tasks may be assigned to existing VMs instead of creating a new VM to perform the task. Furthermore, a coordinator may determine a grouping of VMs or VM hosts based on one or more factors associated with the VMs or the VM hosts, such as VM type or geographical location of the VM hosts. The coordinator may also assign one or more Virtual Server Agents (VSAs) to facilitate managing the group of VM hosts. In some embodiments, the coordinators may facilitate load balancing of VSAs during operation, such as during a backup operation, a restore operation, or any other operation between a primary storage system and a secondary storage system.

Abstract: An illustrative “VM heartbeat monitoring network” of heartbeat monitor nodes monitors target VMs in a data storage management system. Accordingly, target VMs are distributed and re-distributed among illustrative worker monitor nodes according to preferences in an illustrative VM distribution logic. Worker heartbeat monitor nodes use an illustrative ping monitoring logic to transmit special-purpose heartbeat packets to respective target VMs and to track ping responses. If a target VM is ultimately confirmed failed by its worker monitor node, an illustrative master monitor node triggers an enhanced storage manager to initiate failover for the failed VM. The enhanced storage manager communicates with the heartbeat monitor nodes and also manages VM failovers and other storage management operations in the system. Special features for cloud-to-cloud failover scenarios enable a VM in a first region of a public cloud to fail over to a second region.