Abstract: A method for managing access to a file based backup (FBB) includes generating, at a first point-in-time, a first FBB at a first point-in-time, wherein the first FBB comprises a first set of files of an asset at the first point-in-time, generating, at a second point-in-time after the first point-in-time, a second FBB at a second point-in-time, wherein the second FBB comprises a second set of files of the asset at the second point-in-time, performing an asset analysis on the first FBB metadata file and a second FBB metadata file associated with the second FBB to generate a differencing FBB metadata file, performing an anomaly analysis on the second FBB using the differencing FBB metadata file to obtain a anomaly report, and performing a remediation of the second FBB based on the anomaly report.

Abstract: A method for managing access to a file based backup (FBB) includes generating, two backup snapshots, each at two points-in-time and each associated with a set of files, comparing the first backup snapshot and the second backup snapshot to generate a difference snapshot, wherein the difference snapshot specifies a third set of files that are different between the first set of files and the second set of files, providing a recovery notification to an application accessing the asset, wherein the recovery notification specifies recovering a file in the third set of files, obtaining a selection of the file in the third set of files from the application, and in response to the selection, performing a recovery of the file.

Abstract: Techniques described herein relate to a method for performing restorations of file system data on a host. The method may include identifying a restoration event associated with a file system of a host; obtaining backup metadata associated with a backup of the file system and obtaining current file system metadata associated with the file system; identifying non-matching files and matching files using the backup metadata and the current file system metadata; storing local copies of the matching files on the host; identifying, based on the current file system metadata and the backup metadata, matching portions, non-matching portions, and completely unique files; storing local copies of the matching portions of the non-matching files on the host to restore the matching portions of the non-matching files; and restoring the completely unique files of the non-matching files and the non-matching portions of the non-matching files from a backup storage.

Abstract: Techniques described herein relate to a method for performing restorations of file system data on a host. The method includes identifying a backup access event associated with a backup of a file system of the host obtaining backup metadata associated with the backup; generating a virtual hard disk file; generating a placeholder file system using the backup metadata and storing the placeholder file system in the virtual hard disk file; generating a hidden copy of the placeholder file system using block cloning; loading the virtual hard disk file on the host; performing backup access services using the placeholder file system and the backup metadata; making a determination that the placeholder file system and the hidden copy indicate updated data blocks have been generated during the backup access services; identifying the modified data blocks; and storing the updated blocks.

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 of a virtual machine (VM) stored on a backup storage, wherein the VM comprises a plurality of applications; 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 in a virtual hard disk file; loading the virtual hard disk file on a host associated with the VM; instantiating single application instances of the VM on the host; and performing application aware backup access services using the placeholder file structure, the backup metadata, and the single application instances of the VM, wherein the single application instances of the VM have limited access to placeholder file structure portions associated with the single application instances.

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, a shared access request for a plurality of virtual machines (VMs) to access a FBB, accessing a FBB metadata file associated with the FBB to determine file data accessible to the plurality of VMs, performing an attribute analysis on the FBB metadata file, wherein the storage location attributes are each associated with a storage location of a portion of the file data in a backup storage system, generating a shared virtual disk in the production host based on the attribute analysis, wherein the shared virtual disk maps the file data to the storage locations, generating the plurality of VMs, wherein the VMs read from and write to the shared virtual disk, and enabling access to the virtual machines by the application.

Abstract: A method for managing access to a file based backup (FBB) includes obtaining, by a FBB metadata file operating in a production host, an instant access request for data associated with an FBB, wherein the instant access request is associated with a user, wherein the FBB is associated with a plurality of users comprising the user and a second user, in response to the instant access request: access a FBB metadata file associated with the FBB to determine file data accessible to the user and determining second file data not accessible to the user, wherein the file data is associated with the user, performing an attribute analysis on the FBB metadata file to identify a storage location attributes of the file data and not the second file data, generating a FBB virtual file system, and enabling access to the FBB virtual file system by the user via an application.

Abstract: A method for managing access to a file based backup (FBB) includes obtaining an instant access request for data associated with two FBBs, wherein the first FBB is stored in a first storage device and the second FBB is stored in a second storage device, accessing a first FBB metadata file associated with the first FBB and a second FBB metadata file to determine file data accessible to the application, performing a storage analysis on the first FBB metadata file and the second FBB metadata file to identify the first storage device and the second storage device, performing a filtering of the file data using a storage device access data structure to obtain filtered data, wherein the storage device access data structure specifies that the application does not have access to the second storage device, and enabling access to a FBB virtual file system by the application.

Abstract: A method for managing access to a file based backup (FBB) includes obtaining, by a FBB metadata file manager operating in a production host, a search request for file data stored in a backup storage system, in response to the search request: generating a set of search results associated with the search request, performing a first attribute analysis for a first search result to identify first storage location attributes of the first file, performing a second attribute analysis for a second search result to identify second storage location attributes of the second file, generating a FBB virtual file system in the production host using the first storage location attributes and the second storage location attributes, displaying the set of search results, and enabling access to the FBB virtual file system by the application via the set of search results.

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 system in virtual hard disk file; loading the virtual hard disk file on a target application; performing, after the loading, prefetching of backup data using the virtual hard disk file and the backup metadata to store the backup data in a cache; and performing backup access services using the virtual hard disk file, the backup metadata, and the cache.

Abstract: Agent lifecycle management for backup and restore applications is described. A system enables selection of application hosts, each of which meets installation requirements for installing instances of application agents from a backup and restore application, then downloads, in parallel, the instances of the application agent to the corresponding selected application hosts. The system installs, in parallel, the instances of the application agent in the corresponding selected application hosts, then registers, in parallel, the instances of the application agent with the backup and restore application. The system subsequently initiates sessions which download and install, in parallel, an update in instances of the application agent in in corresponding application hosts. The system unregisters at least one of the instances of the application agent, in at least one application host, from the backup and restore application.

Abstract: A method for managing a client environment includes obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with a configuration of nodes in the client environment, in response to the notification: obtaining metadata associated with the auto-generated service request, analyzing the metadata to extract current node configuration details, comparing the current node configuration details to an node optimization model, making a determination, based on the comparing, that an optimization is required, based on the determination, performing a re-configuration on the nodes in the client environment.

Abstract: A method for managing a client environment includes obtaining a notification for an auto-generated service request, wherein the auto-generated service request is associated with an issue with the client environment, in response to the notification: obtaining metadata associated with the auto-generated service request, analyzing the metadata to extract pattern information, comparing the pattern information to a service request pattern database, making a determination, using the service request pattern database, that a recommendation is associated with the pattern information, and based on the determination, performing a remediation action associated with the recommendation.

Abstract: A method for managing data includes obtaining, by a universal connector, a backup request for an incremental backup of a set of files, in response to the backup request: sending a file extent request to a network attached storage (NAS) server, obtaining, from the NAS server, a set of file extents associated with data of the set of files, performing a block-based analysis on the set of file extents using a stored data block table to determine a subset of data blocks, sending a data access request based on the subset of data blocks, obtaining a response from the NAS server, wherein the response comprises the subset of data blocks, and initiating a backup of the set of files using the subset of data blocks.

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 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: 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: 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: 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.