Abstract: A method is provided for backing up and restoring a web applications platform. The method includes backing up web applications platform databases to a backup system. A search index of the web application platform is backed up. An application programming interface (API) is queried to discover internet information services (IIS) virtual directories associated with the web applications platform. Discovered IIS virtual directories associated with the web applications platform are backed up to the backup system. IIS configuration data, IIS metabase data and registry data for the web applications platform are then backed up to the backup system. A similar process enables the restoration of this data to allow for disaster recovery for the web applications platform.

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 embodiment, a sender process on a node of a node cluster communicates a live object to a receiver process. The sender process determines a shared binary file and a shared file location. The sender process serializes the live object to be communicated to a receiver process, into a binary data stream and writes the binary data stream into the predetermined shared binary file. The receiver process receives a shared binary filename and the shared location associated with the shared binary file. The receiver process de-serializes the binary data stream and reconstructs the live object. The communication is independent of the type of proxy, i.e., virtual or physical, and operating systems of the proxies, such as Windows, Mac OS, or Linux. The live objects may be VM configurations and VHD information metadata.

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: Embodiments are directed to a large-scale data backup system and method. A backup process accesses a defined policy defining how the virtual machines are to be grouped into a plurality of groups, and groups the plurality of virtual machines into the plurality of groups according to the defined policy with each group containing a number of virtual machines that can be backed up in a single backup operation without causing a system error. It then takes a snapshot backup of each group of the plurality of groups in a respective data rollover operation, and saves the snapshot backup of each group to a storage media. The policy may be a user-defined policy or a dynamic system-defined policy, and may be based on characteristics such as total number of virtual machines, system characteristics, and backup system constraints.

Abstract: In one embodiment, for each of the nodes forming a cluster that share a cluster shared volume (CSV), a remote connection is established with an operating system (OS) management interface of an operating system of the node to query and to obtain OS configuration information concerning a VMM hosting one or more virtual machine (VMs) within the node. A remote connection is established with a VMM interface of the VMM of the node to query and to obtain VM information concerning each of the VMs hosted by the VMM in the node. An analysis is performed on the OS configuration information and the VM information in view of a set of management rules. A report is generated based on the analysis, the report including information indicating which of the management rules has been violated.

Abstract: A backup of an application stored in a container on a backup media server is accessed. The container is formatted as a virtual hard disk and in a read-only mode. A differencing virtual hard disk is created at a recovery server. The differencing disk is pointed to the container. A size of the differencing disk is increased. The differencing disk is mounted onto the recovery server. Writes are allowed to be made to the differencing disk mounted at the recovery server while the virtual hard disk formatted container remains in the read-only mode on the backup media server.

Abstract: Systems, methods, and computer-readable media can present improved data backup of data servers, including Microsoft Exchange servers. Embodiments can provide backup of a data server using a backup application, where the backup application can send a request to the data server for data to backup and receive a first set of backup data from the data server. The backup application can also send a request to the data server for backup data criteria and receive backup data criteria from the data server. The backup application may apply the backup data criteria to the first set of data to create a second set of backup data that is new, non-duplicated data sending the second set of backup data to a storage device, thus saving storage space, backup time, and network bandwidth.

Abstract: Techniques for virtual proxy based backup of virtual machines in a cluster environment are disclosed. In some embodiments, each of a subset of virtual machines hosted by physical nodes in a cluster environment is configured as a virtual proxy dedicated to backup operations. During backup, data rollover of each virtual machine in the cluster environment that is subjected to backup is performed using a virtual proxy.

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: Techniques for virtual proxy based backup of virtual machines in a cluster environment are disclosed. In some embodiments, each of a subset of virtual machines hosted by physical nodes in a cluster environment is configured as a virtual proxy dedicated to backup operations. During backup, data rollover of each virtual machine in the cluster environment that is subjected to backup is performed using a virtual proxy.

Abstract: A differencing virtual hard disk is created at a recovery server. The differencing disk is pointed to a virtual machine that has been backed up to a backup media server. A configuration file associated with the backed up virtual machine is restored to the recovery server while the backed up virtual machine remains on the backup media server. A planned virtual machine is created from the configuration file. Virtual hard disk settings of the planned virtual machine are modified to point to the differencing disk at the recovery server. Parameters of the planned virtual machine are modified based on a path of the configuration file as restored on the recovery server. The planned virtual machine is realized.

Abstract: A method for backing up and restoring search service applications (SSAs) is provided that backs up an SSA topology extensible markup language (XML) file to a backup system. The method then backs up an SSA search topology XML file to the backup system and backs up SSA databases to the backup system. An application programming interface (API) is queried to discover internet information services (IIS) virtual directories associated with the SSA. Discovered IIS virtual directories associated with the SSA are backed up to the backup system IIS configuration data, IIS metabase data and registry data for the SSA are also backed up to the backup system. A similar process is utilized to restore this data to enable the recovery of an SSA.

Abstract: A backup agent issues to a virtual machine management service (VMMS) a request to export a virtual machine (VM). The VMMS generates a configuration file associated with the export that cannot be accessed by the backup agent because the file is encrypted. A full backup of the exported VM is performed. A first backup check point corresponding to the full backup is created. After the full backup, a second backup check point is created. The agent issues to the VMMS a request to export changes to the VM between the first and second backup check points. An incremental backup of the exported changes is performed and a backup components document is created. A synthetic full backup based on the incremental and full backups is created and restoration of the VM from the synthetic full backup is based on the information in the backup components document.

Abstract: Identifying virtual machines and errors for snapshots is described. A system receives, from a volume snapshot service, an error message and a corresponding component identifier associated with a backup operation. The system requests a corresponding snapshot status from each component participating in the backup operation. The system receives a corresponding snapshot status from each component participating in the backup operation. The system requests an error identifier from a component corresponding to a snapshot failure status. The system receives the error identifier from the component corresponding to the snapshot failure status. The system identifies a virtual machine based on the component identifier. The system outputs, via a user interface, a report identifying the virtual machine and the error identifier.

Abstract: Techniques for virtual proxy based backup of virtual machines in a cluster environment are disclosed. In some embodiments, each of a subset of virtual machines hosted by physical nodes in a cluster environment is configured as a virtual proxy dedicated to backup operations. During backup, data rollover of each virtual machine in the cluster environment that is subjected to backup is performed using a virtual proxy.

Abstract: Techniques for virtual proxy based backup of virtual machines in a cluster environment are disclosed. In some embodiments, each of a subset of virtual machines hosted by physical nodes in a cluster environment is configured as a virtual proxy dedicated to backup operations. During backup, data rollover of each virtual machine in the cluster environment that is subjected to backup is performed using a virtual proxy.