Abstract: A vulnerability tagging process helps prioritize backups of datasets in a network by monitoring events that affect containers in the network. The monitored events are processed by an AI-based event analyzer to characterize each event in terms of a potential for destruction or damage to the data by each event. A vulnerability measure is calculated as the product of the number of occurrences of each event based on the severity associated with each event. Once the events are analyzed and the vulnerability scores are calculated, the scores are tagged on each workload. The vulnerability tags can then be utilized by the backup server to modify protection policies and/or prioritize backup schedules for the container workloads.

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: Methods and systems for restoring data are described. According to some embodiments, the method, in response to receiving a first restore request, initiates a second restore request to a hybrid data buffer to route blocks of backup data to the hybrid data buffer. The method further invokes an interrupt service routine (ISR) that is initialized with reserved addresses. When the blocks of backup data are transmitted to the hybrid data buffer, the method further tags, by the ISR, the blocks of backup data to a specified location, where the specified location is one of the reserved addresses.

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: Embodiments are described for performing an uninterrupted backup in a storage system responsive to an abort event. A backup agent receives a plurality of file objects to be backed up on a target device during a first backup session. The backup agent initiates a parent interrupt service routine (ISR), which generates a plurality of child ISRs. Each of the plurality of child ISRs monitors a backup state of a corresponding file object. The parent ISR generates a virtual file object queue (VFOQ) to store a current backup state of each of the plurality of file objects. When an abort occurs, the current backup state of each of the plurality of file objects is saved in a respective child ISR of that file object. During a subsequent backup session, backup of the plurality of file objects commences based on the current backup state of each of the plurality of file objects.

Abstract: Methods and systems for file level prioritization during a data restore operation are disclosed. According to some embodiments, in response to a restore request to restore one or more files and for each file, the method includes retrieving file information and a critical value associated with the file, and calculating a Euclidean distance of the file to a consecutive file based on the critical value. The method further includes sorting the file(s) based on the calculated Euclidean distance of each file. The method further includes restoring the sorted file(s) at a target site.

Abstract: Methods and systems for block-level data prioritization during a backup operation are disclosed. According to some embodiments, the method includes extracting a backup data criticality from header information of one or more data blocks. The method further includes based on the extracted backup data criticality, assigning a weighted value corresponding to the backup data criticality. The method further includes for each data block, calculating a Euclidean distance of the data block to a consecutive data block using the weighted value.

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 for providing data integrity services to an application host that hosts an application that uses application data includes storage for storing threshold values for creating an application backup and a processor programmed to monitor: a rate of change associated with the application data, and an input-output rate of the application data; make a determination, based on the threshold values, the rate of change, and the input-output rate, that an unscheduled backup for the application is to be generated; obtain a micro-backup for the application in response to the determination; and obtain a restoration ready backup for the application using the micro-backup and at least one previously generated 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: A backup management system for providing data integrity services to an application host that hosts an application having application data includes storage for storing a restore point catalog and a processor programmed to obtain a micro-backup of the application, wherein the micro-backup reflects changes made to the application data over a period of time from when a last scheduled backup was generated and a number of changes to the application data exceeded a predetermined number, wherein generation of the micro-backup was not scheduled; obtain a timestamp that delineates an end of the period of time; obtain header data of the last scheduled backup generated for the application host; and obtain an application backup for the application using the micro-backup, the timestamp, and the header data, wherein the application backup is usable to restore the application to a state associated with the end of the period of time.

Abstract: A backup management system for providing data integrity services to an application host that hosts an application that uses application data includes storage for storing threshold values for creating an application backup and a processor programmed to monitor: a rate of change associated with the application data, and an input-output rate of the application data; make a determination, based on the threshold values, the rate of change, and the input-output rate, that an unscheduled backup for the application is to be generated; obtain a micro-backup for the application in response to the determination; and obtain a restoration ready backup for the application using the micro-backup and at least one previously generated 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: Methods, apparatus, and processor-readable storage media for implementing a message management framework using machine learning techniques are provided herein. An example computer-implemented method includes processing a message comprising identifying at least one message type of the message; determining, based at least in part on the at least one identified message type, one or more message failures by applying one or more machine learning-based rules to at least a portion of the message; determining one or more remedial actions by processing, using one or more machine learning techniques, the at least one identified message type, the one or more determined message failures, and multiple attributes of the message; and performing one or more automated actions based at least in part on the one or more determined remedial actions.

Abstract: The present invention discloses a system for effective media tag management and method thereof. The system (100) comprises a client interface module (101) which is integrated with an external website client. The client interface module (101) provides the website client with provisions to implement media tags on items of interest showcased on the website client. The media tags gather user information and send the information to the client interface module (101) which then transmits the collected user data to a base server (102). The base server (102) is responsible for making the collected user data available to external agencies and users of the system (100). The base server (102) additionally comprises provisions for providing users information about the condition of their data and where it is being sent.

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.