Abstract: Systems and methods for protecting and identifying virtual machines that have the same name in a multi-tenant distributed environment are provided. When backing up a virtual machine, a unique identifier of the virtual machine is incorporated into the name of the virtual machine's save set. This allows a backup administrator to distinguish between virtual machines that have the same name. This improves the ability to perform restore operations by enabling virtual machines that have the same name to be distinguished.

Abstract: Techniques to protect against data loss are disclosed. In various embodiments, an amount of data that has changed since a last backup of at least a defined subset of a save set is determined. The determined amount of changed data is compared to a corresponding threshold. A backup is performed based at least part on a determination that the determined amount of changed data equals or exceeds the threshold.

Abstract: A method and system for enabling data backups for virtual machines reliant on raw data mapping (RDM) disks to store their state and/or data. Traditional virtual machine backup methodologies pivot on the generation and storage of virtual machine snapshots as copies of a virtual machine disk file, which store the state and/or data of a virtual machine at various given points in time. However, these traditional virtual machine backup methodologies, at least at present, do not support the generation and storage of virtual machine snapshots for virtual machines that particularly access and consolidate information on RDM disks. Accordingly, the method and system disclosed herein facilitate the backup of state and/or data pertaining to virtual machines reliant on RDM disks.

Abstract: Techniques to protect against data loss are disclosed. In various embodiments, an amount of data that has changed since a last backup of at least a defined subset of a save set is determined. The determined amount of changed data is compared to a corresponding threshold. A backup is performed based at least part on a determination that the determined amount of changed data equals or exceeds the threshold.

Abstract: Techniques to protect against data loss are disclosed. In various embodiments, an amount of data that has changed since a last backup of at least a defined subset of a save set is determined. The determined amount of changed data is compared to a corresponding threshold. A backup is performed based at least part on a determination that the determined amount of changed data equals or exceeds the threshold.

Abstract: Synchronizing storage devices outside of disabled write windows is described. A system receives, via a backup/restore application interface, a list of identifiers corresponding to source storage devices to be backed up. The system enables a target storage device to synchronize with a source storage device. The system sends, via the backup/restore application interface, a request to disable any write commands to the source storage devices corresponding to the list of identifiers. The system creates a snapshot of the source storage device. The system sends, via the backup/restore application interface, a request to enable any write commands to the source storage devices corresponding to the list of identifiers.

Abstract: Embodiments are directed to a method of backing up virtual machines coupled to a backup server in a large-scale data storage system, by installing a single instance of a backup management program on the backup server; pushing, by the backup management program, a backup agent to each virtual machine; detecting, through the backup agent, all applications running on a respective virtual machine; taking a snapshot of each application after freezing the applications and prior to thawing the applications, by the backup agent; and saving the snapshot of the each applications on a storage medium. The pushing step comprises creating a shared folder and exposing the shared folder to all the virtual machines for remote invocation by the backup program.

Abstract: A method and system for enabling data backups for virtual machines reliant on raw data mapping (RDM) disks to store their state and/or data. Traditional virtual machine backup methodologies pivot on the generation and storage of virtual machine snapshots as copies of a virtual machine disk file, which store the state and/or data of a virtual machine at various given points in time. However, these traditional virtual machine backup methodologies, at least at present, do not support the generation and storage of virtual machine snapshots for virtual machines that particularly access and consolidate information on RDM disks. Accordingly, the method and system disclosed herein facilitate the backup of state and/or data pertaining to virtual machines reliant on RDM disks.

Abstract: Systems and methods for protecting and identifying virtual machines that have the same name in a multi-tenant distributed environment are provided. When backing up a virtual machine, a unique identifier of the virtual machine is incorporated into the name of the virtual machine's save set. This allows a backup administrator to distinguish between virtual machines that have the same name. This improves the ability to perform restore operations by enabling virtual machines that have the same name to be distinguished.

Abstract: Object layout discovery outside of backup windows is described. A system receives, from a backup/restore application, a request to discover an object layout for a data object by parsing the data object. The system determines whether the object layout is stored in layout storage. The system sends, to the backup/restore application, the object layout stored in the layout storage in response to a determination that the object layout is stored in the layout storage.

Abstract: Techniques to protect against data loss are disclosed. In various embodiments, an amount of data that has changed since a last backup of at least a defined subset of a save set is determined. The determined amount of changed data is compared to a corresponding threshold. A backup is performed based at least part on a determination that the determined amount of changed data equals or exceeds the threshold.

Abstract: Techniques to protect against data loss are disclosed. In various embodiments, an amount of data that has changed since a last backup of at least a defined subset of a save set is determined. The determined amount of changed data is compared to a corresponding threshold. A backup is performed based at least part on a determination that the determined amount of changed data equals or exceeds the threshold.

Abstract: Handling aborts of backup operations is described. A system receives an abort request message corresponding to a backup operation associated with a source storage device. The system determines whether a snapshot associated with the backup operation is created of the source storage device. The system synchronizes the source storage device with a target storage device in response to a determination that the snapshot associated with the backup operation is created of the source storage device. The system sends an abort completion message to a backup/restore application interface associated with the backup operation.