Abstract: A system for identifying and deleting records of hosts includes a local data manager. The local data manager identifies a discovery event associated with the host and a record type of record types, obtains, in response to identifying, all previously discovered records on the host associated with the record type from a host record repository, obtains discovered records associated with the record type and associated with the host, after obtaining all discovered records and previously discovered records, selects a previously discovered record of the previously discovered records, makes a determination that the previously discovered record does not match any discovered records of the discovered records and is not tagged with a soft delete tag or a hard delete tag, and in response to the determination, tags the previously discovered record with a soft delete tag, and notifies a data manager of modifications to the previously discovered records.

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 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 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 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 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 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 system for identifying and deleting records of hosts includes a local data manager. The local data manager identifies a discovery event associated with the host and a record type of record types, obtains, in response to identifying, all previously discovered records on the host associated with the record type, obtains discovered records associated with the record type and associated with the host, after obtaining all previously discovered records and discovered records: selects a first discovered record of the discovered records, makes a first determination that first discovered record is not included in the previously discovered records, in response to the first determination: updates a host record repository to include the first discovered record, and notifies a data manager of modified records.

Abstract: A system for identifying and deleting records of hosts includes a local data manager. The local data manager identifies a discovery event associated with the host and a record type of record types, obtains, in response to identifying, all previously discovered records on the host associated with the record type from a host record repository, obtains discovered records associated with the record type and associated with the host, after obtaining all discovered records and previously discovered records, selects a previously discovered record of the previously discovered records, makes a determination that the previously discovered record does not match any discovered records of the discovered records and is not tagged with a soft delete tag or a hard delete tag, and in response to the determination, tags the previously discovered record with a soft delete tag, and notifies a data manager of modifications to the previously discovered records.

Abstract: A production host includes a persistent storage and a backup manager. The persistent storage stores virtual machine data and a service group list associated with an application service group. The backup manager obtains a backup generation request for the application service group that includes virtual machines, and each of the virtual machines uses a copy of the virtual machine data; in response to obtaining the backup generation request: identifies a first virtual machine the virtual machines that is prioritized for generating a backup for the application service group based on the service group list; attempts to generate the backup using the first virtual machine and the copy of the virtual machine data; and stores the backup in backup storage.

Abstract: A backup storage includes a persistent storage and a backup manager. The persistent storage stores backups of entities and a global application data map. The backup manager obtains a restoration request for restoration of an application hosted by an entity of the entities; makes a determination to accelerate the restoration based, at least in part, on the application; in response to the determination: identifies a virtual disk level backup of the entity that is associated with the application using the global application data map; obtains the virtual disk level backup from the backups of the entities; and restores the application using the virtual disk level backup.

Abstract: A method for providing an application service to clients includes identifying a failure of the application service that causes the application service to be suspended; in response to identifying the failure: instantiating an instance of an application for providing the application service in a production host; identifying at least one virtual disk level backup that is: associated with the application and is a portion of deduplicated backups; extracting the at least one virtual disk level backup from deduplicated backups to obtain a copy of the at least one virtual disk level backup; identifying application data associated with the application within the copy of the at least one virtual disk level backup; transitioning an application service session for a client of the clients to the instance of the application; and resuming the application service for the client using the instance of the application and the application data.

Abstract: A backup storage includes persistent storage and a backup manager. The persistent storage stores backups of entities and an entity list that lists the entities. The backup manager obtains a restoration availability request from a user; filters the entity list based on an identity of the user to obtain an available entity list; identifies, based on user input obtain based on the available entity list, an entity of the entities; and restores the entity using the backups.

Abstract: A method and system for efficiently handling backup discovery operations. Specifically, the disclosed method and system entail enhancing breadcrumbs—e.g., persistent files that store status and other metadata information respective to performed asset backup operations—to further include unique transaction identifiers. These transaction identifiers may serve as markers for distinguishing which subset of breadcrumbs (rather than all breadcrumbs) to forward to a central management system during asset backup discovery operations. The disclosed method and system also implement batch processing architecture to regulate resource consumption on both the client and manager sides.

Abstract: A method and system for efficiently handling backup discovery operations. Specifically, the disclosed method and system entail enhancing breadcrumbs—e.g., persistent files that store status and other metadata information respective to performed asset backup operations—to further include unique transaction identifiers. These transaction identifiers may serve as markers for distinguishing which subset of breadcrumbs (rather than all breadcrumbs) to forward to a central management system during asset backup discovery operations. The disclosed method and system also implement batch processing architecture to regulate resource consumption on both the client and manager sides.

Abstract: A method for managing backups that includes generating a full backup of a database and, after generating the full backup, generating N incremental backups of the database and generating a first differential backup of the database after the N incremental backups have been generated, wherein the first differential backup is generated relative to the full backup.

Abstract: A backup storage includes a persistent storage and a backup manager. The persistent storage stores backups of entities and a global application data map. The backup manager obtains a restoration request for restoration of an application hosted by an entity of the entities; makes a determination to accelerate the restoration based, at least in part, on the application; in response to the determination: identifies a virtual disk level backup of the entity that is associated with the application using the global application data map; obtains the virtual disk level backup from the backups of the entities; and restores the application using the virtual disk level backup.

Abstract: A method for providing an application service to clients includes identifying a failure of the application service that causes the application service to be suspended; in response to identifying the failure: instantiating an instance of an application for providing the application service in a production host; identifying at least one virtual disk level backup that is: associated with the application and is a portion of deduplicated backups; extracting the at least one virtual disk level backup from deduplicated backups to obtain a copy of the at least one virtual disk level backup; identifying application data associated with the application within the copy of the at least one virtual disk level backup; transitioning an application service session for a client of the clients to the instance of the application; and resuming the application service for the client using the instance of the application and the application data.

Abstract: A production host includes a persistent storage and a backup manager. The persistent storage stores virtual machine data and a service group list associated with an application service group. The backup manager obtains a backup generation request for the application service group that includes virtual machines, and each of the virtual machines uses a copy of the virtual machine data; in response to obtaining the backup generation request: identifies a first virtual machine the virtual machines that is prioritized for generating a backup for the application service group based on the service group list; attempts to generate the backup using the first virtual machine and the copy of the virtual machine data; and stores the backup in backup storage.

Abstract: A backup storage includes persistent storage and a backup manager. The persistent storage stores backups of entities and an entity list that lists the entities. The backup manager obtains a restoration availability request from a user; filters the entity list based on an identity of the user to obtain an available entity list; identifies, based on user input obtain based on the available entity list, an entity of the entities; and restores the entity using the backups.