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 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 system for providing data protection services for user data generated by an application, includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for user data based on a protection policy, in response to identifying the backup generation event, obtain user data associated with the backup generation event from the application, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, and generate a user data backup using the user data and the user metadata, in which the user data backup comprises calendar events of the calendar and portions of the user metadata associated with the calendar events.

Abstract: Techniques described herein relate to a method for generating backups of assets. The method may include identifying, by a backup agent, a backup generation event associated with an asset; in response to identifying the backup generation event: obtaining change information associated with the asset, and the change information includes at least one change list; generating an asset backup using the at least one change list, in which the asset backup includes asset backup data, asset backup metadata, and historical metadata; and storing the asset backup in a backup storage.

Abstract: 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.

Abstract: Techniques described herein relate to a method for performing data protection services for data stored in a shared storage. The method may include identifying, by a primary data node, a protection policy event initiating performance of data protection services for data stored in the shared storage used by the primary data node and secondary data nodes; in response to identifying the protection policy event: obtaining primary data node monitoring information associated with the primary data node; obtaining secondary data node monitoring information associated with the secondary data nodes; assigning at least one resource limit to the primary data node and the secondary data nodes based on the primary data node monitoring information and the secondary data node monitoring information; and initiating performance of the data protection services by the primary data node and the secondary data nodes based on the assigned at least one resource limit.

Abstract: A system for providing data protection services for user data generated by an application includes persistent storage that includes an archive storage and a backup storage. The system also includes a manager. The manager is programmed to generate data chunks using user data, generate backup object metadata associated with the data chunks; obtain previously generated backup object metadata associated with the user data using an archive value, make a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata, and, in response to the first determination: store the at least one data chunk in the archive storage as a portion of a user data backup, and store remaining data chunks of the data chunks in the backup storage as the remaining portion of the user data backup.

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.

Abstract: A system for providing data protection services for user data associated with calendar groups generated by an application includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for the user data associated with a calendar group based on a protection policy, obtain user data associated with the backup generation event from the application in response to identifying the backup generation event, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, generate calendar group information associated with the calendar using the user data and the user metadata, generate a user data backup using the user data, the calendar group information, and the user metadata, in which the user data backup comprises backup data and backup metadata.

Abstract: A method that is performed for backing up data. The method includes obtaining a backup request; and in response to the backup request: obtaining an asset and an asset entry from a file system metadata repository associated with the backup request; identifying asset components of the asset using the asset entry; assigning asset components to backup threads to be backed up as pseudo-assets based on the asset entry; executing the backup threads to generate pseudo-asset backups; storing the pseudo-asset backups on backup storages; and updating asset backup metadata based on the pseudo-asset backups.

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: Techniques to back up data are disclosed. In various embodiments, a function pointer associated with a system call by an application is modified to point to a custom write function. A request to write application data is received at the custom write function. The application data is written to a backup destination based at least in part on a determination that the request is associated with invocation of a backup method of the application.

Abstract: A system for providing data protection services for user data generated by an application includes persistent storage that includes an archive storage and a backup storage. The system also includes a manager. The manager is programmed to generate data chunks using user data, generate backup object metadata associated with the data chunks; obtain previously generated backup object metadata associated with the user data using an archive value, make a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata, and, in response to the first determination: store the at least one data chunk in the archive storage as a portion of a user data backup, and store remaining data chunks of the data chunks in the backup storage as the remaining portion of the user data backup.

Abstract: A method that is performed for backing up data. The method includes obtaining an incremental backup request; and in response to the incremental backup request: obtaining an asset and an asset entry associated with the incremental backup request; dividing the asset into pseudo-assets based on the asset entry; storing the pseudo-assets across backup storages to generate incremental pseudo-asset backups; initiating the merging of the incremental pseudo-asset backups to generate an incremental asset backup; and initiating the merging of the incremental asset backup with a previously generated full asset backup associated with the incremental backup request to generate a first synthetic full asset backup.

Abstract: In some embodiments, described is a system (and method) for providing an efficient preview capability for emails backed up to a cloud-based object storage. The email preview may be provided as part of an interface allowing a user to select individual emails to restore from the object storage. The system may extract specialized preview information as part of a backup procedure. The preview information may include metadata and email content. For example, the preview information may include various email details such as sender, receiver, subject line, time sent/received, filenames of any attachments, etc. The preview information may also include email content such as particular sentences from the email body containing keywords. The system may also store extracted preview information in a specialized manner such that the preview information may be retrieved without having to access the actual backup data.

Abstract: Described is a system (and method) for managing specialized metadata that may be used to manage and search incremental backup data stored on a cloud-based object storage. The system may create and store such metadata as part of a specialized metadata database that includes a data catalog and a backup catalog. The system may leverage the metadata database to initiate operations to efficiently manage incremental backup data stored on the object storage. For example, the metadata may be relied upon to efficiently reconstruct (e.g. synthetically) the client data to a point-in-time of any incremental backup. In addition, the metadata may include properties of the backed-up data, which are maintained separately from the backup data stored as objects. Accordingly, these properties may be searched to identify and locate backup data without having to retrieve the stored objects.

Abstract: A system for providing data protection services for user data associated with calendar groups generated by an application includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for the user data associated with a calendar group based on a protection policy, obtain user data associated with the backup generation event from the application in response to identifying the backup generation event, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, generate calendar group information associated with the calendar using the user data and the user metadata, generate a user data backup using the user data, the calendar group information, and the user metadata, in which the user data backup comprises backup data and backup metadata.

Abstract: Described is a system for synchronizing expiration times for incremental backup data stored on a cloud-based object storage. More particularly, the system may provide a layer of intelligence when updating the expiration times associated with backup data to ensure that a full recovery of the client data to a point-in-time of any incremental backup may be performed. To provide such a capability, the system may maintain specialized metadata identifying expiration times for objects and a list of objects required to perform a full recovery to a point-in-time for each of the performed backups (e.g. full or incremental). The system may access this metadata to identify which objects stored by a previous backup are still referenced by a subsequent backup. Based on the identified objects, the system may synchronize object expiration times to ensure objects are not prematurely deleted from the object storage.

Abstract: A system for providing data protection services for user data generated by an application, includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for user data based on a protection policy, in response to identifying the backup generation event, obtain user data associated with the backup generation event from the application, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, and generate a user data backup using the user data and the user metadata, in which the user data backup comprises calendar events of the calendar and portions of the user metadata associated with the calendar events.

Abstract: A method and system for the efficient backup and recovery of electronic mail objects. Particularly, the disclosed method and system propose the elimination of redundant electronic mail object content while pursuing backup operations thereof, thus promoting faster and more efficient successive backups. Furthermore, the disclosed method and system propose a framework through which the restoration of electronic mail objects may be decoupled from engagement with any electronic mail client.