According to various embodiments, with respect to a target set of files being managed (e.g., protected by data snapshots), each file in the target set of files is classified into one of two or more filesets (discontiguous filesets), where each of these filesets comprises one or more files that are related to each other by one or more factors, such as frequency of file change or purpose of existence (e.g., used by a software application). Once classified, files within the target set of files can be uniquely processed by a data management operation (e.g., incremental data snapshot process) according to their association to a discontiguous fileset.

Some examples relate generally to a data management platform comprising: a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; and transmitting the data associated with the aspect of the secondary data to the target.

Described is a system (and method) that provides the ability to create an endpoint to allow cloud-based components to access services directly using network infrastructure of a cloud system. To provide such an ability, access connections from components of a production system to the cloud system may be monitored to derive a storage service and a datastore based on portions of a domain name. The derived storage service and datastore are then used to determine configuration settings required to automatically create a service endpoint. The service endpoint may then be deployed within the cloud system allowing the cloud-based component to access the storage service directly. Accordingly, the system provides the ability to automatically configure and deploy service endpoints by leveraging information derived from monitoring network access connections between a production environment and a cloud environment.

A resource matching technique between a primary site and one or more secondary sites accommodates a configuration update of a virtual machine (VM) in a disaster recovery (DR) environment. The resource matching technique determines whether a proposed resource configuration update or change to a primary VM running at the primary site is permissible on a secondary VM configured for failover operation at a secondary site in the event of failure to the primary VM. The technique continuously monitors the availability of resources at each secondary site and enables negotiation between the primary and secondary sites of the proposed configuration change based on corresponding indications resource availability. The resources may include generic resources (e.g., memory, storage capacity and CPU processing capacity) and specialized resources (e.g., GPU types and/or models).

Techniques described herein relate to a method for generating backups of virtual machines. The method may include, in response to identifying a backup generation event associated with virtual machines: obtaining, by a backup agent, virtual machine metadata associated with the virtual machines; identifying groups of virtual machines based on the virtual machine metadata; provisioning resources to generate backups of the virtual machines based on the groups of virtual machines; and generating a backup of the virtual machines based on the groups of virtual machines using the provisioned resources associated with the groups of virtual machines.

An information handling system may include a first host system, comprising a first processor and a first network interface, and a second host system, comprising a second processor and a second network interface. The first network interface may be configured to accelerate migration of a designated virtual resource from the first host system to the second host system.

An elastic Internet Protocol (IP) address for hypervisor and virtual router management in a branch environment may be provided. First, an IP address may be assigned to a hypervisor associated with a virtual branch. Next, it may be determined that a virtual machine (VM) has been instantiated at the virtual branch. In response to determining that the VM has been instantiated at the virtual branch, the IP address may then be released. It may next be determined that the VM is in a failed state and then, in response to determining that the VM is in the failed state, the IP address may be reassigned to the hypervisor.

There is provided allocating cloud computing resources to process a user session by a gateway in a mobile communications network, and allocating the cloud computing resources in pairs to user sessions. Rules for the pair of allocated resources are determined such that incoming control plane traffic associated with the session is forwarded to the both cloud computing resources forming the pair.

The disclosed technology teaches recovering a first virtual machine or an instance with an Internet Protocol address, a first root volume and one or more data volumes that are corrupted. The first virtual machine is hosted by a first cloud server that hosts plurality of virtual machines. The disclosed technology includes instructing the first cloud server to launch a recovery virtual machine. The recovery virtual machine launches one or more new data volumes based upon captured file system images in one or more snapshots taken of corrupted data volumes of the first virtual machine prior to becoming corrupted. The recovery virtual machine detaches the corrupted data volumes and attaches the new data volumes launched to the first virtual machine. The Internet Protocol address of the first virtual machine remains unchanged.

The subject matter of this specification can be implemented in, among other things, a method including creating a new disk file at a reference point-in-time, wherein an original disk file is a backing file of the new disk file, copying the original disk file to a disk snapshot file, in response to the original disk file being copied to the disk snapshot file, merging the original disk file and the new disk file to form a merged file, wherein a virtual machine is to continue to perform disk operations using the merged file, and determining whether the merged file is synchronized with the original disk file and the new disk file by determining whether entries of a bitmap for the merged file match corresponding entries of a bitmap for the new disk file.