Abstract: A method for performing a backup operation, the method comprising receiving a backup operation request for an asset, partitioning a plurality of slices of the asset into a plurality of backup sessions, wherein each backup session comprises a separate portion of the plurality of slices, sending a first backup request to a proxy manager to initiate a backup session of the plurality of backup sessions, wherein initiating the backup session comprises: instantiating a container on the one compute node, wherein the backup session operates within the container, receiving a notification that one of the plurality of slices in the backup session has been processed, and sending, based on the notification, a second backup request to the proxy manager to add a new slice to the backup session, wherein the new slice is associated with a second asset.

Abstract: A method for performing a backup operation, the method comprising receiving a backup request for an asset, partitioning, based on available capacity in a proxy infrastructure, a plurality of slices of the asset into a plurality of backup sessions, wherein each backup session comprises a separate portion of the slices, wherein the plurality of slices are associated with a queue, sending a first reservation request to the proxy infrastructure, wherein the first reservation request specifies the plurality of backup sessions, making a first determination that a first portion of the plurality of backup sessions was successfully reserved and that a second portion of the plurality of backup sessions was unsuccessfully reserved, sending a request to initiate the first portion of the plurality of backup sessions on the proxy infrastructure, and sending the second portion of the plurality of backup sessions to the queue based on the first determination.

Abstract: A method for performing a backup operation, the method comprising receiving a backup operation request for an asset, identifying a queue comprising the plurality of slices, wherein each slice references a separate portion of the asset, sending a first backup request to a proxy manager to instantiate a container for each of a plurality of backup sessions, wherein each backup session corresponds to a slice of the plurality of slices, receiving, from the proxy manager, a notification that one of the number of backup sessions is complete and a corresponding container has been torn down, making a second determination that there is an additional slice on a second queue associated with a second asset, and sending, based on the second determination, a backup request to the proxy manager to instantiate a new container for the additional slice associated with the second asset.

Abstract: A method for managing virtual machines (VMs) includes obtaining, by a backup agent, a backup request for an incremental backup of a VM, in response to the backup request: obtaining a resilient change tracking (RCT) data structure associated with the VM, sorting a set of tracked changes specified in the RCT based on offset, performing a size normalization of the set of tracked changes to obtain a set of normalized blocks, storing a normalized blocks metadata table in the backup agent, wherein the normalized blocks metadata table comprises a mapping between the set of tracked changes and the set of normalized blocks, and initiating storage of the incremental backup in a backup storage system using the normalized blocks metadata table.

Abstract: A method for managing virtual machines obtaining a backup request for a full backup of a VM, in response to the backup request: performing a logical slicing of VM data associated with the virtual machine to obtain a set of logical slices, initiating generation of a backup of each logical slice in the set of logical slices to obtain a set of backup slices, storing the set of backup slices in a backup storage system, after storing the set of backup slices, obtaining a second backup request for a virtual synthetic backup of the VM, in response to the second backup request: obtaining a tracked changes file associated with the VM data after the full backup, identifying a backup slice associated with each of the tracked changes, and initiating storage of the virtual synthetic backup using the tracked changes file and the set of backup slices.

Abstract: A method for managing virtual machine (VMs) includes obtaining, by a backup agent, a backup request for a space-efficient backup of a VM, in response to the backup request: parsing a virtual disk associated with the VM to obtain data block information of VM data associated with the VM, performing, using data block information of the VM data, a used block analysis to identify a set of used blocks by the VM data, generating an updated data block information, wherein the updated data block information comprises the set of used blocks, generating the space-efficient backup of the VM using the updated data block information, and storing the space-efficient backup in a backup storage system.

Abstract: A method for managing virtual machines (VMs) includes obtaining, by a backup agent, a restoration request for a VM, in response to the restoration request: identifying a set of backup slices associated with the VM, initiating a restoration of each of the set of backup slices to a production host, wherein the set of backup slices is stored in a backup storage system operatively connected to the production host, generating, at the production host, a composite virtual disk associated with the VM, mapping VM data in the set of backup slices to the composite virtual disk, and generating the VM to read from the composite virtual disk.

Abstract: A method for managing virtual machines includes obtaining a backup request for a full backup of a VM, in response to the backup request: performing a logical slicing of VM data associated with the VM to obtain a set of logical slices, storing the set of backup slices in a backup storage system, after storing the set of backup slices, obtaining backup metadata associated with the VM from the backup storage system, performing, using the backup metadata, a slice file system analysis on each backup slice of the set of backup slices associated with the VM to obtain file system information for a portion of VM data stored in each backup slice of the set of backup slices, and generating, from each backup slice associated with the full backup, a file indexing system for each backup slice in the set of backup slices using the file system information.

Abstract: A method for managing virtual machines (VMs) obtaining, by a metadata file manager, an instant access request for instant access to a backup of a VM to execute in a production host, wherein the backup is stored in a backup storage system, in response to the instant access request: obtaining a configuration selection for the instant access of the backup, obtaining backup metadata associated with the backup, generating, at the production host, a temporary virtual disk based on the configuration selection and the backup metadata, generating, in the metadata file manager, a second virtual disk comprising logical blocks, mapping VM data stored in the backup storage system to the logical blocks in the second virtual disk, configuring the VM to read from the temporary virtual disk, and servicing a write request of the temporary virtual disk using the mapping of the VM data in the second virtual disk.

Abstract: A method for managing data migration includes: obtaining a confidence level of a predicted failure state of an internal component (IC) of a source device, in which the IC is one of a plurality of ICs in the source device; making a first determination that the confidence level exceeds a predetermined confidence level threshold; making, based on the first determination, a second determination that a high priority network slice of a network exists; mapping, based on the second determination, data stored in the IC to the high priority network slice; and migrating the data to a target device via the high priority network slice.

Abstract: A method for managing application migration includes: inferring dependencies and connectivity among applications executing on a system; generating a target infrastructure node (IN) configuration template based on the inferred dependencies and connectivity; making a determination that a configuration of a target IN does not satisfy the template, in which an application is executing on an IN, in which the application is not executing on the target IN; in response to the determination: obtaining a weight for each inferred parameter in the template, in which the inferred parameters comprises the inferred dependencies and connectivity, in which the weight for each inferred parameter is configured by a user; executing, based on the weights, a model to obtain a deviation score for a second target IN; generating, based on the deviation score, a migration recommendation specifying the second target IN; and initiating a display of the migration recommendation to the user.

Abstract: A method for providing ransomware training includes conducting a skill assessment for a user to determine a user performance level of the user; determining user attributes associated with the user, and user attributes include a user type, a user role, and a list of providers associated with the user; generating a training exercise including a simulated attack, and generating the simulated attack includes identifying a real-world ransomware attack, determining attack attributes of the real-world ransomware attack, and generating the simulated attack based on the attack attributes, the user attributes, and the user performance level; conducting the training exercise by sending the simulated attack to the user; receiving an attack response from the user, where the attack response includes the user's response to the simulated attack; and providing feedback to the user based on the attack response, the user attributes, and the user performance level.

Abstract: A method for performing an application migration operation, the method includes initiating the application migration operation to migrate an application from a source device to a target device, where the source device includes a source data migration agent and the target device includes a target data migration agent. The method also includes initiating an active scan. Further, the method includes establishing a secure data path between the source device and the target device. Moreover, the method includes making a first determination, using the active scan, that the network traffic or the source performance metrics are indicative of suspicious activity and logging information about the suspicious activity. The method also includes making a second determination that the application migration operation is complete and terminating the active scan and the secure data path based on the second determination.

Abstract: A method for enhancing data security includes receiving data. The method includes obtaining a plurality of contextual factors associated with the data. The further method includes determining an encryption level based on at least one of the contextual factors. The method further includes determining a type of encryption based on the encryption level. The method further includes encrypting the data using the type of encryption to generate encrypted data. The method further includes associating an access control level with the encrypted data to generate associated encrypted data. The method also includes determining a storage location for the associated encrypted data based on the encryption level, wherein determining the storage location is based on a data sensitivity associated with the data or a compliance rule. The method further includes sending the associated encrypted data to the storage location.

Abstract: A method for managing a data protection module (DPM) includes: obtaining an alert generated by the DPM within a predetermined period of time; obtaining metadata associated with the DPM; analyzing the metadata to extract relevant data; analyzing the alert to extract second relevant data; making, based on the second relevant data, a determination that a tolerance level associated with the alert has been exceeded; sending, based on the determination, the alert, the relevant data, and the second relevant data to a vendor environment (VE) analyzer; in response to sending the alert, the relevant data, and the second relevant data, receiving a service request (SR) generated by the VE analyzer for the DPM; and providing the SR to the client to notify a user of the client about the SR using a graphical user interface (GUI) of the client.

Abstract: Techniques described herein relate to a method for performing data protection services for limited access cloud data. The method includes identifying, by a cloud service provider (CSP) proxy, a protection policy event associated with an incremental approximation backup of an object; in response to identifying the protection policy event: obtaining previous object metadata associated with the object; obtaining object data from on-premises cloud resources associated with the object; generating slices of the object data; generating current checksums and current object metadata associated with each slice; selecting a first slice of the slices; making a first determination that a first current checksum of the current checksums and a first previous checksum associated with the first slice do not match; in response to the first determination: storing the first slice in a backup storage; and updating a first portion of the current object metadata associated with the first slice.

Abstract: Various embodiments of the invention may receive information related to a plurality of application upgrades from an application monitoring agent. Based on the received information, a device emulation will be requested, and an emulation will be performed in response to generate an application upgrade strategy that includes such things as emulated (e.g., predicted) upgrade times. The application upgrade strategy is used to produce a more refined upgrade strategy. The various embodiments refine the upgrade strategy by specifically consider the power consumption and cost for the power that is consumed.

Abstract: Embodiments of the invention relate to methods and systems for efficiently performing one or more backups of assets stored on a shared storage. In one or more embodiments, the assets are sliced into a plurality of slices and the size of the slices is determined based on a maximum recommended number of connections that can be used and either a previous backups number of connections used, or the total number of connections currently used. The recommended number of connections to use is also calculated based on system telemetry. By changing the size of the slices, one or more embodiments of the invention may ensure that the backup is performed as efficiently as possible. This may result in better utilization of system and network resources as well as a better backup and recovery performance.

Abstract: Described is a system for cloud-based processing of backup data for storage onto various types of object storage systems. A specialized cloud-based component (e.g. proxy server) may act as an intermediary when backing up data from a client system to an object storage. For example, the cloud-based component may be provided as part of backup service that operates in conjunction with a client system. Accordingly, the system may allow different clients of a backup service to efficiently and seamlessly interact with the different third-party object storage providers via a single cloud-based component. To provide such object-storage-agnostic functionality, the cloud-based component may include a function library that includes object-storage-specific functions. For example, the cloud-based component may invoke a specific set of operations that interact with a storage API provided by a particular object storage provider.

Abstract: Techniques described herein relate to a method for performing generating backups of host snapshots. The method may include identifying, by a data protection agent of a host, an asset discovery event associated with the host; in response to identifying the asset discovery event: obtaining file system metadata associated with the host from a file system metadata repository on a storage of the host; identifying existing snapshots on the host using the file system metadata; obtaining snapshot metadata associated with the snapshots using the file system metadata; providing the file system metadata to a data protection manager to generate assets; and providing the snapshot metadata to the data protection manager to generate pseudo-assets.