Abstract: Embodiments for a method of backing up virtual hard disks by: parsing a list of base parent and differencing disks to identify disk parameters and child disks of immediate parent disks; creating a differencing disk chain in reverse time order of modification of the base parent disk starting from the base parent disk to a latest child differencing disk; identifying changed sectors in each child disk starting from the latest child differencing disk; creating a list detailing a respective differencing disk, sector offsets and logical data sector index for each changed sector; iteratively adding updated sectors to the list for latest changed sectors that were not previously added to the list by a later child disk by reading the changed sectors from their respective child disk; and merging, in a single step, the changed sectors read from their respective child disks into the base parent disk.

Abstract: Techniques described herein relate to a methods and systems for asset classification, which may include: identifying, in a backup domain, a first asset and a second asset; performing a first analysis of the first asset to determine a set of first asset characteristics; performing a second analysis of the second asset to determine a set of second asset characteristics; creating a first asset group based on the first analysis and the second analysis, the first asset group comprising the first asset and the second asset; and assigning a first backup policy to the first asset group.

Abstract: Systems, devices, and methods for reducing the impact of temporary unavailability of storages in a backup storage system. The system may store different types of backups depending on the availability storages. The first type of backup, which may rely on a previous backup stored in a first storage that is available for restoration purposes, may be stored on the first storage. When the first storage becomes temporarily unavailable, a second type of backup may be stored in a second storage that is available that requires a previous backup stored in the temporarily unavailable first storage for restoration purposes. The second type of backup may be chained to the previous backup stored in the temporarily unavailable storage. The second type of backup may be converted to the first type of backup when the first storage becomes available again in a computationally efficient manner.

Abstract: A method for performing a backup operation includes obtaining, by a backup agent, a backup request, and in response to the backup request: obtaining a complete application listing, wherein the complete application listing specifies a plurality of applications associated with the backup request, comparing the complete application listing to a cloud-based application listing, wherein the cloud-based application listing specifies a portion of the plurality of applications, making a first determination that the complete application listing specifies more than the portion of the plurality of applications, and in response to the first determination, initiating a hybrid workflow, wherein the hybrid workflow specifies backing up each of the plurality of applications.

Abstract: A remote agent, for providing data protection services to virtual machines, includes persistent storage and a backup manager. The persistent storage is for storing a resource allocation calendar and lifecycle policies associated with the virtual machines. The backup manager obtains a virtual machine data package from a virtual machine of the virtual machines; identifies a computational load change point based on the lifecycle policies; predicts a magnitude of a computational load during a period of time demarcated by the computational load change point using, at least in part, the virtual machine data package; updates the resource allocation calendar to obtain an updated resource allocation calendar, the updating is based on: the identified computational load change point, and the magnitude of the computational load during the period of time; and generates a backup for the virtual machine using the updated resource allocation calendar.

Abstract: A system for providing backup services for limited-access user data includes persistent storage for storing a conversation specific user data backup and a manager. The manager identifies a backup generation event for limited-access user data based on a protection policy; in response to identifying the backup generation event; obtains fragmented user data from an application that gates access to the limited-access user data; obtains organizational metadata associated with the fragmented user data from the application; makes a determination that the fragmented user data is associated with a conversation; in response to making the determination, obtains conversation metadata associated with the fragmented user data from the application; and generates the conversation specific user data backup using the organizational metadata, conversation metadata, and the fragmented user data.

Abstract: A system for providing backup services for limited-access user data includes persistent storage for storing a user data visualization enhanced user data backup and a manager. The manager identifies a backup generation event for limited-access user data based on a protection policy; in response to identifying the backup generation event, obtains fragmented user data from an application that gates access to the limited-access user data; obtains organizational metadata associated with the fragmented user data from the application; makes a determination that the fragmented user data is associated with a user data visualization; in response to making the determination, obtains user data visualization metadata associated with the fragmented user data from the application; and generates the user data enhanced user data backup using the organizational metadata, the user data visualization metadata, and the fragmented user data.

Abstract: A system including persistent storage for storing an object repository and a user data backup. The system also includes a manager that obtains fragmented user data associated with an object that is potentially duplicative of an object stored in the object repository; makes a determination that the object is duplicative based on a copy of the object stored in the object repository; in response to making the determination, adds the fragmented user data to a user data backup without adding the object to the backup; associates the fragmented user data in the user data backup with the copy of the object stored in the object repository; and stores the user data backup in the persistent storage.

Abstract: A system for providing backup services for limited-access user data includes persistent storage for storing fragmented user data and a manager. The manager identifies a backup generation event for the limited-access user data based on a protection policy; in response to identifying the backup generation event, obtains the fragmented user data from an application that gates access to the limited-access user data; identifies, based on the fragmented user data, organizational metadata for generating a user data backup; obtains the identified organizational metadata from the application; and generates the user data backup using the organizational metadata and the fragmented user data.

Abstract: A system for providing backup services for limited-access user data includes persistent storage and a manager. The manager identifies a backup generation event for the limited-access user data based on a protection policy; in response to identifying the backup generation event, performs, using an application that gates access to the limited-access user data, a change analysis of the limited-access user data to identify a portion of the limited-access user data that is potentially in a backed-up state; obtains, using the application, metadata associated with the portion indicative of whether sub-portions of the portion are in the backed-up state; identify, using the metadata, at least one of the sub-portions that is not in the backed-up state; and generates the user data backup using the at least one of the sub-portions.

Abstract: A Building Management System (BMS) includes a plurality of building subsystems and communications interface. The building subsystems include device(s) for controlling aspect(s) of the building subsystem. The communications interface receives commands from a cloud-based controller and a local client device. The commands from the cloud-based controller and local client device are structured to modify setting(s) for a device of the building subsystems. A BMS controller receives, via the communications interface from the cloud-based controller, a command for modifying a setting of a device for a first building subsystem. The BMS controller identifies a local setting of the device provided by the local client device. The BMS controller identifies a priority of the command from the cloud-based controller in relation to a priority of the local setting. The BMS controller controls the device based on the respective priorities.

Abstract: A method for a backup operation includes obtaining, by a backup agent, a backup request for an incremental backup of a file system, and in response to the backup request: selecting a reference backup from a backup storage system, obtaining a first hash value document associated with the reference backup, generating a hash value for an asset associated with the file system, making a first determination that the hash value matches a second hash value specified in the first hash value document, in response to the first determination, populating an incremental backup with a copy of data associated with the asset, initiating a transfer of the incremental backup to the backup storage system, and storing a second hash value document, wherein the second hash value document comprises the hash value and a backup identifier of the incremental backup.

Abstract: A method for managing a persistent storage system includes obtaining, by a first node in a node cluster, a write request, wherein the node cluster comprises the first node and a second node, processing the write request, storing data associated with the write request in a persistent storage system, updating a block-based change list based on the storing, making a first determination that a synchronization schedule is triggered, and in response to the first determination: initiating a block-based change list synchronization to the second node.

Abstract: A method for performing a backup operation includes obtaining, by a backup agent, a backup request for a file system, and in response to the backup request: generating a first application partition for an application associated with the file system, performing a dependency analysis on the application to identify application dependency information, populating a first application partition with a copy of the application dependency information and a copy of application data associated with the application, and initiating a storage of a backup to a backup storage system, wherein the backup comprises the first application partition.

Abstract: A backup agent for facilitating restorations of virtual machines includes a persistent storage and a backup/restoration policy updater. The persistent storage stores backup/restoration policies. The backup/restoration policy updater identifies a change of a label associated with data of a production host and, in response to identifying change in the label, identifies a virtual machine of the virtual machines associated with the data; performs a threat analysis of the identified virtual machine to determine a new security policy for the identified virtual machine; and updates a policy of the backup/restoration policies associated with the identified virtual machine based on the identified new security policy.

Abstract: A method and system are provided for matching database records. According to one embodiment, the method includes receiving a record from a first database, and selecting a sequence of characters within the record. The method also includes identifying a key associated with a second, dissimilar database by comparing the selected sequence with a number of historical records. The comparison is performed using one or more analytical processes, where at least one analytical process is a machine-learning (ML) process. The method further includes matching, using the key, the record from the first database with another record from the second database, where the other record includes the identified key.

Abstract: A method for performing a backup operation includes obtaining, by a backup agent, a backup request, and in response to the backup request: obtaining a complete application listing, wherein the complete application listing specifies a plurality of applications associated with the backup request, comparing the complete application listing to a cloud-based application listing, wherein the cloud-based application listing specifies a portion of the plurality of applications, making a first determination that the complete application listing specifies more than the portion of the plurality of applications, and in response to the first determination, initiating a hybrid workflow, wherein the hybrid workflow specifies backing up each of the plurality of applications.

Abstract: A backup manager for providing backup services includes persistent storage and a backup orchestrator. The persistent storage includes protection policies. The backup orchestrator identifies a last backup generation time for a client in response to a protection policy of the protection policies triggering a backup generation for the client; obtains system metadata for the client; identifies a portion of client data that has been modified since the last backup generation time using the system metadata; generates an incremental backup based on the identified portion of the client data; and stores the incremental backup in backup storage.

Abstract: A backup manager for providing backup services includes persistent storage and a backup orchestrator. The persistent storage includes protection policies. The backup orchestrator generates a backup for a client based on the protection policies. The backup orchestrator generates an index for the backup. The index specifies a sensitivity level of each portion of the backup. The backup orchestrator stores portions of the backup in regions of a container that correspond to the sensitivity level of the respective portion of the backup. The backup orchestrator stores the container in backup storage.

Abstract: A backup storage for providing backup services includes storage and a compliance manager. The storage includes backups. The compliance manager obtains a compliance request for data; makes a determination, in response to obtaining the compliance request, that the data is stored as part of a backup of the backups; in response to making the determination: deletes linking data that associates a portion of a compliance sensitive data portion stored in backup metadata of the backup with a portion of modified backup data of the backup to make the linking data unavailable; and removes the modified backup data using garbage collection.