Abstract: In one example, a method includes receiving, at a physical proxy node, a backup request from a client outside the cluster environment, the backup request identifies a VM that is to be backed up, and including data that resides on a virtual federated database that is an element of the cluster environment and to which respective databases of each node of the cluster environment are mapped, and the backup request is received at the physical proxy node due to the position of the physical proxy node in a PSOL. Next, initiating, with an agent at the physical proxy node, a save program on the physical proxy node, and initiating, with the save program, a secondary save process on the physical proxy node that is a federated backup process and includes reading the VM identification from the backup request, and backing up the VM identified in the backup request.

Abstract: In one example, a method includes obtaining cluster and machine configuration information, sending a restore request for one or more machines, and loading a backup of a virtual machine, the backup having been created by a federated backup process involving the physical proxy node, and the virtual machine includes data that resides on a virtual federated database that is an element of a cluster environment and to which respective databases of each of a plurality of nodes of the cluster environment are mapped. Next, the virtual machine is taken offline after the backup of the virtual machine has been loaded, and after the virtual machine has been taken offline, the virtual machine is removed from the node where it resides. The backup of the virtual machine is then restored, and the restored virtual machine brought online, after which the restored virtual machine is enabled as a cluster-wide virtual machine.

Abstract: In one example, a method includes obtaining cluster and machine configuration information, sending a restore request for one or more machines, and loading a backup of a virtual machine, the backup having been created by a federated backup process involving the physical proxy node, and the virtual machine includes data that resides on a virtual federated database that is an element of a cluster environment and to which respective databases of each of a plurality of nodes of the cluster environment are mapped. Next, the virtual machine is taken offline after the backup of the virtual machine has been loaded, and after the virtual machine has been taken offline, the virtual machine is removed from the node where it resides. The backup of the virtual machine is then restored, and the restored virtual machine brought online, after which the restored virtual machine is enabled as a cluster-wide virtual machine.

Abstract: In one example, a method includes receiving, at a physical proxy node, a backup request from a client outside the cluster environment, the backup request identifies a VM that is to be backed up, and including data that resides on a virtual federated database that is an element of the cluster environment and to which respective databases of each node of the cluster environment are mapped, and the backup request is received at the physical proxy node due to the position of the physical proxy node in a PSOL. Next, initiating, with an agent at the physical proxy node, a save program on the physical proxy node, and initiating, with the save program, a secondary save process on the physical proxy node that is a federated backup process and includes reading the VM identification from the backup request, and backing up the VM identified in the backup request.

Abstract: A virtual machine backup process where a plurality of types of snapshots of the virtual machine coexist includes: obtaining a list of files comprising virtual hard disks and differencing virtual hard disks associated with the virtual machine; sorting the list of files to identify relationships and to generate a current tree in which differencing virtual hard disks point to corresponding parent virtual hard disks; comparing the current tree with a previous tree associated with the virtual machine from the last backup of the virtual machine; identifying differencing virtual hard disks in the current tree that are not present in the previous tree as incremental backup data; and backing up the incremental data. The incremental data is merged with a previous synthetic full backup of the virtual machine to generate a new synthetic full backup of the virtual machine.

Abstract: In one example, a method for data protection in a cluster environment includes identifying data in the cluster environment that is to be backed up, where the identified data includes data that resides on a shared disk of the cluster environment. Next, a physical proxy node, from which a backup of the identified data will be performed, is selected. The selected physical proxy node is in the cluster environment. A federated backup of the identified data is then performed from the physical proxy node and generates a backup. The backup is then stored for later restoration to a node of the cluster environment.

Abstract: A remote backup agent that provides data storage services to virtual machines includes a persistent storage and a processor. The persistent storage stores workflows for the virtual machines. The processor performs a first remote backup of the virtual machines based on the workflows using production agents hosted by production hosts that also host the virtual machines; obtains a workflow update; updates the workflows based on the workflow update to obtain updated workflows; and performs a second remote backup of the virtual machines based on the updated workflows using the production hosts without modifying the production agents.

Abstract: According to one embodiment, a system in response to a request to back up a virtual machine (VM) to a backup storage system, retrieves history data from the backup storage system. The history data has been previously backed up in the backup storage system during a previous backup operation of the VM. The history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at the point-in-time of the previous backup operation. The system validates the history data against a current configuration of the VM. The current configuration includes information of one or more current consistent states of the VM disk. The system determines a backup type for each of the current consistent states based on the validated history data. The system backs up each of the current consistent states based on the backup type.

Abstract: Embodiments described herein provide for a system and associated logic to enable browsing of a federated backup having a plurality of portions, each portion separately generated and indexed by a plurality of nodes. In one embodiment, the system performs a federated backup by generating a unique identifier on a primary node and providing the unique identifier to each secondary node tasked with generating the plurality of portions. The secondary nodes associate the unique identifier with each of the plurality of portions. The unique identifier can then be used by a recovery UI to generate and display a consolidated view of the plurality of portions.

Abstract: A remote backup agent that provides data storage services to virtual machines includes a persistent storage and a processor. The persistent storage stores workflows for the virtual machines. The processor performs a first remote backup of the virtual machines based on the workflows using production agents hosted by production hosts that also host the virtual machines; obtains a workflow update; updates the workflows based on the workflow update to obtain updated workflows; and performs a second remote backup of the virtual machines based on the updated workflows using the production hosts without modifying the production agents.

Abstract: According to one embodiment, a system in response to a request to back up a virtual machine (VM) to a backup storage system, retrieves history data from the backup storage system. The history data has been previously backed up in the backup storage system during a previous backup operation of the VM. The history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at the point-in-time of the previous backup operation. The system validates the history data against a current configuration of the VM. The current configuration includes information of one or more current consistent states of the VM disk. The system determines a backup type for each of the current consistent states based on the validated history data. The system backs up each of the current consistent states based on the backup type.

Abstract: An incremental backup of a database includes issuing a request to a copy service requesting a snapshot of a volume having the database, and identifying a writer of the database that should participate in creating the snapshot. From the snapshot, changes to the database since a last backup of the database and log files associated with the database that include data not yet committed to the database, are transmitted to a backup storage unit.

Abstract: A backup and recovery architecture for applications compatible with the Microsoft Windows Volume Shadow Copy Service (VSS) includes a backup client module that includes an orchestration engine, an application manager, a common requestor, and a save transports component. The client module interacts with the VSS on the client in the generation of a shadow copy. Data is backed up from the shadow copy to a backup storage server. In various specific embodiments, the application manager includes functions that are application-specific and the orchestration engine includes functions that are not application-specific. A single consolidated log may be generated by the backup client module for a backup or recover operation.

Abstract: A first cluster node receives a request for a backup of files stored in a CSV shared with a second cluster node. A first VSS writer determines a first set of files associated with the first cluster node. A second VSS writer determines a second set of files associated with the second cluster node. A WMD file associated with the backup is generated to include a first component describing the first set of files and a second component describing the second set of files. A BCD file associated with the backup is modified to store information indicating the first VSS writer to restore the first and second sets of files, such that the first and second sets of files can be restored using the first VSS writer without having to use the second VSS writer. The backup is then performed to a backup storage device.

Abstract: Backup operations for shared volumes are described. A shared volume is identified as used by a virtual machine scheduled for a backup operation by a first distributed system node. A second distributed system node is identified that has a responsibility for sending control signals to the shared volume. An association is saved of the second distributed system node to the shared volume. The responsibility for sending control signals to the shared volume is assigned to the first distributed system node. The backup operation is executed for the shared volume by the first distributed system node. The responsibility for sending control signals to the shared volume is assigned to the second distributed system node.

Abstract: Displaying configuration test results by leveraged data protection software is described. A memory location is read where a display file is stored for a software installer. A configuration checker is executed for the computer. Results are read from executing the configuration checker. The results are written to the memory location. A leveraged software creation tool is prompted to display the display file via an output device. The leveraged software creation tool lacks the capability to dynamically load the display file.

Abstract: A process for organizing data objects backed up from a content-addressed storage systems is disclosed. Content-addressed storage systems back up data objects in a flat directory, labeling them with non-intuitive user-unfriendly content addresses. Such directories can be large and difficult to browse, making selective recovery of desired data objects inefficient and laborious. When the content-addressed storage system is further archived to a secondary storage device, such as tape, navigation of archived data objects is especially tedious and difficult. An embodiment of the present invention enables easy navigation of a data object directory created by building a pseudo-file structure as content addressed data objects are archived to a secondary backup device. The file structure of the data object director is based upon timestamp metadata extracted from each data object, resulting in a navigable directory tree that is more intuitive and user-friendly.

Abstract: What is disclosed is process for backing data objects from a content addressed storage system to a tape storage device such that the data objects are written in a contiguous sequential fashion. Data objects are kept together on the storage medium, rather than fragmented. An embodiment of the present invention describes the software modules and memory buffers required to implement this process. Additionally, what is disclosed is a process that restores data objects that have been contiguously written to tape. According to one embodiment of the present invention, recovery of non-fragmented data objects is made more efficient and less prone to failure.

Abstract: A process for organizing data objects backed up from a content-addressed storage systems is disclosed. Content-addressed storage systems back up data objects in a flat directory, labeling them with non-intuitive user-unfriendly content addresses. Such directories can be large and difficult to browse, making selective recovery of desired data objects inefficient and laborious. When the content-addressed storage system is further archived to a secondary storage device, such as tape, navigation of archived data objects is especially tedious and difficult. An embodiment of the present invention enables easy navigation of a data object directory created by building a pseudo-file structure as content addressed data objects are archived to a secondary backup device. The file structure of the data object director is based upon timestamp metadata extracted from each data object, resulting in a navigable directory tree that is more intuitive and user-friendly.

Abstract: What is disclosed is process for backing data objects from a content addressed storage system to a tape storage device such that the data objects are written in a contiguous sequential fashion. Data objects are kept together on the storage medium, rather than fragmented. An embodiment of the present invention describes the software modules and memory buffers required to implement this process. Additionally, what is disclosed is a process that restores data objects that have been contiguously written to tape. According to one embodiment of the present invention, recovery of non-fragmented data objects is made more efficient and less prone to failure.