Abstract: Embodiments described herein relate to a method for managing file based backups (FBBs). The method may include obtaining a FBB mount request for a FBB mount of a FBB from an application, wherein the application is executing in a production host environment and the FBB is stored on backup storage; in response to the FBB mount request: enabling access to a portion of the FBB by the application; notifying a cyber sense device that the access is enabled; providing, to the cyber sense device, a storage location of the portion of the FBB for which access was enabled; receiving, from the cyber sense device, a security event notification; and performing, in response to the security event notification, a security action set.

Abstract: Embodiments described herein relate to a method for managing file based backups (FBBs). The method may include obtaining a FBB mount request for a FBB mount of a FBB from an application, wherein the application is executing in a production host environment and the FBB is stored on backup storage; in response to the FBB mount request: capturing an entity context associated with the application; authenticating the entity context; obtaining, when the authenticating is successful, access control information corresponding to the FBB from the backup storage; determining a subset of the FBB for which the access control information indicates the entity context has permission to access; and enabling access to a portion of the FBB by the application.

Abstract: Described is a system for predictive storage policy selection for a cloud-based storage based on backup monitoring. The system may reduce storage costs incurred by a subscriber of a backup service that leverages a cloud-based storage. The system may monitor backup operations and collect backup statistics associated with the resource requirements of performing a backup to a cloud-based storage. To collect such information, the system may execute a specialized monitoring process that works in conjunction with a backup application and/or server. The collected information may be stored as part of a metadata database associated with the object storage. Accordingly, the system may retrieve the information from the metadata database to predict storage costs associated with performing future backup operations. Based on the predicted storage costs, the system may automatically select an appropriate storage policy.

Abstract: Techniques described herein relate to a method for managing jobs. Such techniques may include: generating a job completion entry that specifies that execution of a first job was completed within an estimated period of time for the first job, generating a second job completion entry that specifies that execution of a second job was not completed within a second estimated period of time for the second job, updating the job resource mapping model based on the first job completion entry and the second job completion entry to obtain a new updated job resource mapping model.

Abstract: In general, embodiments relate to a managing a Redundant Array of Independent Disks (RAID) group. The embodiments include determining a minimum and maximum set of spare disks to allocate to the RAID group, wherein the RAID group comprises a plurality of active members, allocating the minimum number of spare members to the RAID group, allocating an additional spare member to the RAID group, setting a mode of the additional spare member to storage mode, enabling, after the setting, the RAID controller to store data in the plurality of active members and in the additional spare member, wherein the plurality of active members, the minimum number of spare members, and the additional spare member comprise persistent storage.

Abstract: In general, in one aspect, the invention relates to a method for managing updates, the method includes identifying a sub-tree based on a call graph, generating an update sequence for the sub-tree using the call graph, selecting a first component of the sub-tree based on the update sequence, wherein the first component is a hardware resource, applying an update to the first component to obtain a first updated component, selecting, after applying the update to the first component, a second component of the sub-tree based on the update sequence, and performing an update on the second component.

Abstract: Described is a system (and method) for leveraging data previously transferred to a cloud-based object storage as part of a failed backup when performing a subsequent backup operation. The system may leverage the native configuration of an object storage that may retain certain data even when a backup operation is classified as a failed operation. To provide such capabilities, the system may store specialized metadata that tracks which backups have failed and metadata indicating which backup data has not been committed. Accordingly, upon a subsequent backup operation, the system may expediently refer to the stored metadata to identify retained backup data that may be reused for the subsequent backup. As a result, the system may improve the efficiency of a backup procedure by reducing the amount of data required to be transferred from the backup source.

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 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: A method and system for auto live-mounting database golden copies. Specifically, the disclosed method and system entail reactively auto live-mounting golden copy databases on hosts or proxy hosts based on the operational state of one or more database hosts and/or one or more assets (or databases) residing on the database host(s). Should a database host prove to be unresponsive, through periodic monitoring, databases residing on the database host may be brought back online on a proxy database host using stored golden copies respective of the aforementioned databases. Alternatively, should a given database on any database host exhibit an operational abnormality (e.g., an error, failure, etc.), the given database may be brought back online on the database host or a proxy database host using a stored golden copy respective of the given database. Accordingly, through the disclosed method and system, database outages may be minimized.

Abstract: A method and system for live-mounting database backups. Specifically, disclosed method and system entail recovering database data—in entirety or at any granular level—without needing to provision storage resources for point-in-time database copies (i.e., backup database data), or without needing to wait for large amounts of data, representative of the point-in-time database copies, to traverse a network from backup storage to a target device. Substantively, through live-mounting, the physical point-in-time database data, as well as the associated structural metadata, may be retained on backup storage while a pointer-based snapshot, mapping to the physical point-in-time database data and structural metadata, may be generated thereon. Thereafter, a file system—mapping to the pointer-based snapshot on the backup storage—may be mounted on the target device, which exposes an interface through which the backup database data may be accessed and/or manipulated using a distributed file system protocol.

Abstract: A method and system for backup processes that includes identifying a target volume and identifying a number of available threads to back up the target volume. The elements in the target volume are distributed among the available threads based on a currently pending size of data in the threads. The elements are stored from each thread into a backup container, and merged from each of the backup containers into a backup volume.

Abstract: In general, the invention relates to a method for performing backup operations. The method includes generating a backup on backup storage system, locking the backup for a retention span, generating a backup archive log image using archive log files for the backup, and locking the backup archive log image for a second retention span.

Abstract: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

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; identifies a portion of the backup that includes an allocation scheme; extracts system metadata from the backup using the allocation scheme; generates an index for the backup using the system metadata; and stores the backup and the index in backup storage.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a backup agent, a backup request for a FBB, in response to the backup request, generating a FBB, generating a FBB metadata file corresponding to the FBB, wherein the FBB metadata file comprises a set of attribute regions, performing, using the set of attribute regions, a deduplication on the FBB metadata file to obtain a deduplicated FBB metadata file, and storing the deduplicated FBB metadata file in a backup storage system.

Abstract: In general, in one aspect, the invention relates to a method for managing performances of services, the method comprising: generating subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one a plurality of services, wherein the subsystem groups are generated using per-service subsystem requirements; and performing at least one of the plurality of services using a subsystem group of the subsystem groups.

Abstract: A method for managing information handling system updates includes identifying topological groups within a managed domain of information handling system devices and identifying one or more homogeneous subgroups, each of which corresponds to a single device type, within each of the identified topological groups. Device updates may then be performed for the managed domain based on the homogeneous subgroups. All instances of a particular device type within the managed domain are updated by performing subgroup-aware update operations that include transmitting a single update image for the particular device type to each topological group that includes a homogeneous subgroup corresponding to the particular device type. The single update image is then distributed to each instance of the particular device type within the topologic group.

Abstract: A method for managing updates of a data manager includes: obtaining a service call graph where the service call graph includes services grouped into service sub-trees and specifies a service hierarchy between the services; identifying the service sub-trees of the service call graph; identifying, using the service hierarchy, independent services among the services of the service call graph; generating, based on identifying the service sub-trees and the independent services, an update sequence for the services; predicting, using the update sequence and the services, an update window for the service sub-trees; and initiating an update of the services using the prediction of the update window.

Abstract: Techniques described herein relate to a method for deploying workflows with data management services. The method may include identifying a service update event; identifying a service sub-tree based on a service call graph; generating an update sequence for the service sub-tree; predicting an update window for the service sub-tree using a final estimated updated completion time for the service, wherein the final estimated updated completion time is based on a risk profile; selecting a first service of the service sub-tree based on the update sequence, wherein the first service includes a first standby service instance and a first active service instance; generating a backup of a first portion of a services shared data volume repository associated with the first service; and applying an update to the first standby service instance to obtain a first updated active service instance.