Abstract: A method for performing a backup operation includes obtaining, by a backup server, a backup request, wherein the backup request specifies a virtual machine to be backed up, wherein the virtual machine is hosted by a production host, and in response to the backup request: obtaining classification data from the backup agent, initiating a backup classification on an unprocessed backup associated with the virtual machine based on the classification data to obtain a sensitivity tag, and initiating a data processing on the unprocessed backup based on the sensitivity tag.

Abstract: The method includes obtaining, by a restoration policy manager, a restoration request for a plurality of application containers, and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, assigning a restoration type to each application container in the plurality of application containers, updating a restoration type list based on the assigning, and initiating a restoration of the plurality of application containers using the restoration type list.

Abstract: A method for generating a backup schedule, that includes receiving, by a scheduling agent, an event entry specifying an event associated with a container, determining that the event entry specifies an alert event, adding the event entry to a plurality of historical event entries in a historical event repository, determining that the plurality of historical event entries indicates a repeating error state of the container, determining that an error frequency of the repeating error state is greater than an existing backup frequency of a container backup schedule, and generating a backup schedule warning indicating a recommended backup frequency.

Abstract: For restoring data, a system with uninterrupted block-based restore has a hybrid container. The hybrid container has an operational buffer and a virtual container unit. The system receives blocks of data from a target device into the hybrid container and sends the blocks of data from the hybrid container to a destination device for a restore session. The system writes information about the blocks of data into one or more virtual containers. If there is an abort of the restore session, the system freezes state of the hybrid container and the virtual container(s). For a next restore session that resumes from where the aborted restore session stopped, the system resumes receiving blocks of data from the target device into the hybrid container and sends only leftover blocks of data to the destination device in accordance with the information in the virtual container(s).

Abstract: A backup management system includes storage and a processor. The processor filters copies of storage system transactions of a service device using a block level filter to identify a portion of the storage system transactions impacting a protected data asset; obtains at least one data protection metric based on the portion of the storage system transactions; makes a determination that the at least one data protection metric indicates that the backup schedule will not provide the protected data asset with a predetermined level of data protection; in response to the determination: generates a service-device initiated backup for the protected data asset; stores the service-device initiated backup in backup storage; and remediates a backup schedule for the service device based on the service-device initiated backup.

Abstract: A backup management system includes storage and a processor. The processor filters copies of storage system transactions of a service device using a block level filter to identify a portion of the storage system transactions impacting a protected data asset; obtains at least one data protection metric based on the portion of the storage system transactions; makes a determination that the at least one data protection metric indicates that the backup schedule will not provide the protected data asset with a predetermined level of data protection; in response to the determination: generates a service-device initiated backup for the protected data asset; stores the service-device initiated backup in backup storage; and remediates a backup schedule for the service device based on the service-device initiated backup.

Abstract: One example method includes obtaining hop information of a metadata path for backup metadata, obtaining content sensitivity information indicating a relative sensitivity of backup data to an attack, based on the hop information and the content sensitivity information, selecting an encryption to be applied to the backup metadata, and applying the encryption to the backup metadata. The backup data may be encrypted with the same encryption algorithm that was used to encrypt the backup metadata.

Abstract: A method for a backup operation in accordance with one or more embodiments of the invention includes obtaining, by a vulnerability analyzer executing on a backup server, a plurality of container event entries, wherein a container event entry of the plurality of container event entries specifies a an application container identifier, a container event identifier, an event severity, and an event type, selecting the container event identifier, identifying a portion of the plurality of container event entries that specify the container event identifier, generating a mean event severity based on the portion of the plurality of container event entries, generating a first vulnerability value associated with the application container identifier, and initiating a backup policy update based on a vulnerability ranking, wherein the vulnerability ranking is based on the first vulnerability value.

Abstract: A method and system for prioritizing critical data object storage during backup operations. Specifically, the method and system disclosed herein entail reordering data objects, awaiting being written to storage and thus queued in one or more data object queues, in accordance with a nearest-critical based sequential order. The nearest-critical based sequential order may be derived through modified weight-based Euclidean distances calculated between adjacent data object pairs queued in any given data object queue. Further, the calculated modified weight-based Euclidean distances incorporate data criticality factors associated with the adjacent data object pairs. By reordering data objects in a nearest-critical based sequential order, critical data objects may be written into storage first, thereby avoiding possible critical data loss should a disaster occur during backup operations.

Abstract: A method for performing a backup operation includes obtaining, by a backup server, container information associated with a plurality of application containers, generating a container score for each application container in the plurality of application containers based on the container information, identifying a resource availability for a backup agent associated with the plurality of application containers, generating an ordering of the plurality of application containers based on the availability and the container scores, and sending a prioritization list update request to the backup agent based on the ordering.

Abstract: A method for performing backup operations includes obtaining, by a stream allocator operating in a backup storage system, a plurality of media management entries, wherein a media management entry of the plurality of media management entries specifies a data object, a relative priority, and a maximum number of streams, selecting the media management entry based on the relative priority, allocating a number of backup streams to the data object based on the maximum number of streams, and initiating a transfer of a backup of the data object from the production host to the backup storage system.

Abstract: Methods and systems for file level prioritization during a data backup operation are described. According to some embodiments, the method includes in response to a request to backup one or more files and for each file, sniffing file information of the file. The method further includes determining a backup critical level of the file based on the file information. The method further includes assigning a weighted value corresponding to the backup critical level of the file. The method further includes using the weighted value to calculate a Euclidean distance of the file to a next consecutive file.

Abstract: A method for managing data includes obtaining, by a backup agent, a migration request, wherein the migration request specifies a plurality of users, and in response to the migration request: identifying a set of source-format data sets in a backup storage system, mounting the set of source-format data sets from the backup storage system, performing data mining on the set of source-format data sets in response to the mounting to obtain a hierarchical structure, generating a cloud-based service user account for each user of the plurality of users, wherein the cloud-based service user accounts are associated with a cloud-based service, obtaining source-format data sets associated with each user of the plurality of users using the hierarchical structure, and initiating a migration of the source-format data sets to the cloud-based service.

Abstract: A method for performing a backup operation includes obtaining, by a backup server, container information associated with a plurality of application containers, generating a container score for each application container in the plurality of application containers based on the container information, identifying a resource availability for a backup agent associated with the plurality of application containers, generating an ordering of the plurality of application containers based on the availability and the container scores, and sending a prioritization list update request to the backup agent based on the ordering.

Abstract: A method for a backup operation in accordance with one or more embodiments of the invention includes obtaining, by a vulnerability analyzer executing on a backup server, a plurality of container event entries, wherein a container event entry of the plurality of container event entries specifies a an application container identifier, a container event identifier, an event severity, and an event type, selecting the container event identifier, identifying a portion of the plurality of container event entries that specify the container event identifier, generating a mean event severity based on the portion of the plurality of container event entries, generating a first vulnerability value associated with the application container identifier, and initiating a backup policy update based on a vulnerability ranking, wherein the vulnerability ranking is based on the first vulnerability value.

Abstract: A method and system for verifying compliance of data objects in backup systems that includes a local compliance engine obtaining a data profile of a data object, the data object being stored on a production host in a region. The local compliance engine identifies an ideal profile corresponding to the data profile, and the data profile is compared to the ideal profile. Mismatches are identified between the data profile and the ideal profile based on the comparison, and an alert is generated based on the identified mismatches. The alert is transmitted to a user system and a centralized compliance system.

Abstract: The method includes obtaining, by a restoration policy manager, a restoration request for a plurality of application containers, and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, assigning a restoration type to each application container in the plurality of application containers, updating a restoration type list based on the assigning, and initiating a restoration of the plurality of application containers using the restoration type list.

Abstract: A pass-through snapshot engine records lifecycle data and chronological status of files or objects, in one or more pass-through snapshots during a backup. If there is an abort, the pass-through snapshot engine freezes the pass-through snapshot(s) and terminates the backup. To restart after the abort, the pass-through snapshot engine sends one or more pass-through snapshots to the backup agent. The backup agent restarts the backup, and enforces states of lifecycle and chronology to files or objects, and discards files or objects that have already been backed up to the target device, in accordance with the one or more pass-through snapshots.

Abstract: A method and system for performing jobs that includes obtaining a current status of a job scheduler queue, obtaining policy level information comprising one or more weightages for each job in the job scheduler queue, and obtaining a current number of available streams for processing jobs in the job scheduler queue. The method and system includes calculating a distance between a first job in the job scheduler queue and the remaining jobs in the job scheduler queue using the one or more weightages to obtain a plurality of distances. The remaining jobs are reordered in the job scheduler queue based on the calculated distances. After the reordering, the first job is scheduled in the job scheduler queue and, after the scheduling of the first job, removing the first job from the job scheduler queue.

Abstract: A method for generating a backup schedule, that includes receiving, by a scheduling agent, an event entry specifying an event associated with a container, determining that the event entry specifies an alert event, adding the event entry to a plurality of historical event entries in a historical event repository, determining that the plurality of historical event entries indicates a repeating error state of the container, determining that an error frequency of the repeating error state is greater than an existing backup frequency of a container backup schedule, and generating a backup schedule warning indicating a recommended backup frequency.