Abstract: Techniques described herein relate to a method for performing data protection of file system data on a host. The method includes identifying a backup access event associated with a backup, wherein a first portion of the backup is stored on a first backup storage and a second portion of the backup is stored on a second backup storage; obtaining backup metadata associated with the backup from a data protection manager; generating a placeholder file structure using the backup metadata and storing the placeholder file structure in a virtual hard disk file; and performing heterogeneous backup storage backup access services using the placeholder file structure and the backup metadata to facilitate transfer of data of the first portion of the backup on the first backup storage and the transfer of data of the second portion of the backup on the second backup storage to an application associated with the backup.

Abstract: A method for managing data includes obtaining, by a universal connector, a data share request to obtain data from a set of files, in response to the data share request: performing a share scan to obtain attributes associated with each file in the set of files, performing a batching of the set of files to obtain a set of file batches using the attributes and using a batch size threshold, performing a request conversion to generate a set of converted batch requests each corresponding to one of the set of file batches, and initiating a data share of the large set of files by sending the set of converted batch requests to a network attached storage (NAS) server.

Abstract: Techniques described herein relate to a method for performing data protection of file system data on a host. The method includes identifying, by a data protection agent, a backup access event associated with a backup of a file system stored on a backup storage; in response to identifying the backup access event: obtaining backup metadata associated with the backup from a data protection manager; generating a placeholder file system using the backup metadata and storing the placeholder file in a virtual hard disk file; and performing backup access services using the placeholder file and the backup metadata to facilitate transfer of file system data of the backup to an application associated with the backup.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file operating in a production host and from an application, an instant access request for data associated with an FBB, and wherein the FBB is associated with a plurality of users comprising the user and a second user, in response to the instant access request: storing a FBB virtual file system in the production host using storage location attributes, wherein the FBB virtual file system maps the file system data to storage locations of files in the FBB, enabling access to the FBB virtual file system by the application, monitoring the use of the FBB virtual file system, based on the monitoring, making a determination that a self-destruction criterion has been reached, and based on the determination, initiating a self-destruction of the FBB virtual file system.

Abstract: A method for managing application migration includes: inferring dependencies and connectivity among applications executing on a distributed system, in which the applications are operatively connected through a network; 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 satisfies the target IN configuration template, in which an application is executing on an IN, in which the application is not executing on the target IN, in which the distributed system comprises the IN and the target IN; initiating migration, based on the determination, the application to the target IN.

Abstract: Techniques described herein relate to a method for performing pre-backup tasks. The method includes obtaining, by a proxy host, a snapshot request associated with a full backup of a file system stored in a network attached storage (NAS) from a backup manager; in response to obtaining the snapshot request: instantiating a NAS container to obtain a snapshot of the file system; providing the snapshot to the NAS container; after providing the snapshot to the NAS container: generating, using the snapshot, slices associated with the file system; sorting the slices based on average file sizes associated with each slice; grouping the slices based on the average file sizes and group criteria to generate slice groups; generating a slice list specifying the slices and the slice groups; and providing the slice list to the backup manager.

Abstract: A method for managing an application upgrade includes: making a first determination that an urgent fix is received from an application monitoring agent; 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, the urgent fix to the high priority network slice; making a third determination that a prerequisite fix is required; mapping the prerequisite fix to the high priority network slice; sending the prerequisite fix and the urgent fix to the reordering engine; reordering at least one fix available in a receiving queue of the reordering engine to prioritize the prerequisite fix and the urgent fix in the receiving queue; sending the prerequisite fix and the urgent fix to a client device upgrade manager; and initiating upgrading of a client device based on the prerequisite fix and the urgent fix.

Abstract: In general, embodiments relate to a method for proactively detecting and filtering vulnerabilities of an application upgrade, comprising: receiving an application upgrade request to upgrade an application to a version from a client device; sending information related to the application upgrade to a vulnerability validator; determining, based on the impact score information, that the version of the application has vulnerabilities and that a second version of the application does not have vulnerabilities; filtering, based on the determining, the version of the application that has vulnerabilities; generating an application upgrade strategy by only considering the second version of the application; and sending information related to the version of the application to a vendor to fix the vulnerabilities.

Abstract: Embodiments of the invention relate to methods and systems for efficiently backing up a production host. In one or more embodiments, the size of slices associated with certain preset asset types are altered. By leveraging metadata of previous backups performed on the assets/hosts, one or more embodiments of the invention are able to determine the types of assets being backed up. Based on these determinations, some asset types may be assigned to slices having a larger size, while other assets may be assigned to slices having smaller sizes as appropriate for type of asset. Thus, various embodiments may improve the utilization of system and network resources.

Abstract: A method that is performed for backing up data. The method includes obtaining an asset backup request; and in response to the asset backup request: obtaining an asset and an asset entry associated with the asset backup request; dividing the asset into pseudo-assets using the asset entry; storing the pseudo-assets across backup storages to generate pseudo-asset backups; initiating the merging of the pseudo-asset backups to generate an asset backup; and updating asset backup metadata based on the asset backup.

Abstract: A standby site is periodically synchronized to a primary site. The synchronizing includes copying blocks of a source volume at the primary site that have changed since a last synchronization to the standby site, and a bitmap specifying locations of the changed blocks. A synthetic full copy of the source volume is generated at the standby site. The synthetic full backup is validated by using the bitmap to identify locations on the synthetic full backup to verify. These locations correspond to the changed blocks. A progress of the validation is tracked. A user can specify a threshold percentage value of data that upon being validated indicates that the standby site is ready to assume production operation from the primary site. A readiness of the standby site to assume production operation is reported based on the progress of the validation and the threshold percentage value.

Abstract: In general, embodiments relate to a method for detecting vulnerabilities of an installed application, comprising: obtaining information related to an application installed to a client device; sending, by an application monitoring agent, the information related to the application installed to the client device to a vulnerability validator; determining by the vulnerability validator, based on impact score information, whether a specific version of the application installed to the client device has vulnerabilities; sending the impact score information to a client device upgrade manager; and notifying, based on the impact score information, the client device when the application installed to the client device has vulnerabilities.

Abstract: A method for managing data protection includes: obtaining metadata associated with a backup from a backup storage; performing analysis on the metadata using an analysis engine to generate an analysis result; generating a data protection strategy using the analysis result; and providing the data protection strategy to a production agent.

Abstract: One or more embodiments of the invention may improve the operation of one or more computing devices in a cluster environment. More specifically, by mapping backups of shared volumes to a cluster client instead of individual data nodes, one or more embodiments of the invention avoid duplicative backups and/or restorations of the same shared assets by the each of the data nodes. Further, if a failure occurs to the particular node the backup may have originated from, in accordance with one or more embodiments of the invention, because the method is agnostic with regards to the individual nodes the backup may have originated from, any remaining data node can discover the backup and perform a restoration or incremental backup. This will provide better protection for the clustered nodes while requiring minimal user/administrator input.

Abstract: Automatically updating agents from backup and restore applications is described. A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions did not fail to install update in any of instances of application agent in cluster of application hosts, then the system stores the updated instances of the application agents in a non-volatile storage.

Abstract: A method for efficient file-based backups and recoveries. The method includes: receiving, to initiate a backup session, a file-system backup instruction identifying a host file-system; obtaining at least one clone logical cluster number (LCN) corresponding to a file managed by the host file-system, and a region LCN corresponding to a file region of the file; based on a determination that the region LCN matches a clone LCN of the at least one clone LCN: querying a cluster-offset tracking data structure using the region LCN to identify a cluster-offset tracking entry including the region LCN and a container offset; writing, as a session metadata record stored in backup session metadata for the backup session, file metadata describing the file and including the container offset; and transmitting, to a backup target, an information tuple including a backup session identifier generated for the backup session, and the backup session metadata.

Abstract: Communications are exchanged with a copy service of a host to identify writers associated with the copy service. The identification includes a type of a writer as being a system or application writer. Writers identified as system writers are added to a list of writers that should participate in a backup operation. For writers identified as application writers, components of an application writer are iterated through to determine whether a component of the application writer has a name or logical path that includes a name of a system service. When any component has the name or logical path that includes the name of the system service, the application writer is promoted to be of type system writer by adding the application writer to the list of writers that should participate in the backup operation. Components of each writer listed in the list of writers are backed up.

Abstract: Techniques described herein relate to methods and systems for managing backup operations. The method may include receiving a request to perform a first backup operation for a first virtual machine (VM); making a first determination, using a vProxy preference map, that a first vProxy is assigned to the first VM based on a backup capability associated with the first vProxy; making a second determination that the first vProxy is not available to perform the first backup operation; making a third determination, based on the second determination and using a vProxy information database, that a second vProxy is available to perform the first backup operation based on the second vProxy being associated with the same backup capability as the first vProxy; and performing the first backup operation using the second vProxy.

Abstract: A method for managing data replication includes: identifying data being used by an application programming interface (API), in which the data is stored in a source device; tagging the data based on a usage level of the data by the API; obtaining a predicted probability of the usage level of the data; making a first determination that the data is tagged as important data and the predicted probability of the usage level of the data is low; and replicating, based on the first determination, the data from the source device to a target device.

Abstract: A method includes identifying relationships between containers on a first device, where each container includes at least one relationship that includes a HAS-A relationship or an IS-A relationship. The method also includes creating, on a second device, a first set of twin containers, where each container in the first set of twin containers corresponds to a container that includes only the HAS-A relationships. In addition, the method includes creating, on the second device and in response to creating the first set of twin containers, a second set of twin containers where each container in the second set of twin containers corresponds to a container that includes at least one IS-A relationship. Moreover, the method includes determining and performing a twin container start-up sequence for the first set and the second set of twin containers.