Abstract: A method for managing data includes obtaining, by an analytics engine and from an application, a file system analysis request for analyzing a file system, wherein the analytics engine is operating on a second environment that is external to a client environment, wherein the file system comprises an organization of file system data, wherein the file system data is generated by the application, in response to the file system analysis request: obtaining a metadata backup, wherein the metadata backup is associated with the file system, applying a machine learning model on the metadata backup to extract a portion of attributes, performing a metadata analysis using the portion of attributes to obtain a processed result, and providing the processed result to the application.

Abstract: A method and system for leveraging backup process metadata for cloud object storage selective deletions. Under cloud object storage architecture, any unstructured data may be managed and stored in the cloud as objects. Objects thus provide an elastic, scalable format through which unstructured data may be maintained for a variety of purposes, including those directed to data backup, archiving, and/or disaster recovery. Further, any unstructured data, stored within any object, may pertain to one or many file(s). Should data, from multiple files, be stored within a shared object, any post-upload activity (e.g., modifications or deletions in keeping with data regulatory compliances) targeting said data, belonging to any one file or a subset of files, may be complex and resource-expensive.

Abstract: A method for managing data includes obtaining, obtaining by a production agent, a request for a backup of a file system, in response to the backup request: generating a file system backup of the file system, generating a metadata backup associated with the file system backup, storing the backup in a storage system, obtaining, by the production agent and from an analytics engine, a data access request for the data, wherein the data is a portion of file system data associated with the file system, and wherein the analytics engine is operating on a second environment that is external to a client environment, wherein the file system is generated by an application executing on the client environment, in response to the data access request: identifying the portion of the file system data from the file system backup, and providing the identified portion to the analytics engine.

Abstract: A method for managing a full backup includes: generating a BBB of a file system, in which the BBB is a full backup of the file system and is generated using a snapshot of the file system; obtaining, using a MBB mechanism, modified file system metadata from the snapshot; obtaining second modified file system metadata from a second snapshot of the file system, in which the snapshot is generated at a first point in time and the second snapshot is generated at a second point in time; comparing the modified file system metadata and the second modified file system metadata to obtain a list of changed assets; initiating an incremental backup of the list of changed assets, in which the list of changed assets is backed up using a FBB mechanism; and generating a synthetic full backup by combining the full backup and the incremental backup.

Abstract: An example method includes detecting, using sensors, packets throughout a datacenter. The sensors can then send packet logs to various collectors which can then identify and summarize data flows in the datacenter. The collectors can then send flow logs to an analytics module which can identify the status of the datacenter and detect an attack.

Abstract: A synthetic full backup of a source volume representing a state of the volume at a current time is retrieved, the synthetic full having been generated by merging a full backup of the volume performed at an initial time with an incremental backup of the volume performed at the current time, after the initial time. A bitmap tracking changes to the volume made between the initial and current times is accessed. The bitmap is used to identify a location on the volume having changes made between the initial and current times. First data written to the location on the volume is read. Second data written to the same location on the synthetic full backup is read. First and second checksums are generated based on the first and second data, respectively. The checksums are compared and if any do not match, an indication is generated that the synthetic full is corrupt.

Abstract: A method and system for enabling incremental backup operations targeting bare-metal recovery and system-state recovery data and metadata. These aforementioned forms of recovery focus on the protection of computing system state, including operating system binaries and configuration, as well as the data, metadata, and/or configuration of software application(s) installed on said computing system(s). Further, the data and/or metadata reflected in said computing system state often remains unchanged unless operating system and/or software application component(s) or feature(s) is/are uninstalled, installed, and/or upgraded. Existing solutions protecting said data and/or metadata tend to only support full backup operations, which are time and storage space inefficient. Ideally, incremental backup operations targeting said data and/or metadata should be provided.

Abstract: Network configuration details associated with a host are collected with each bare metal recovery (BMR) backup of the host. The network configuration details are stored in backup storage with each BMR backup copy. A target host is booted into a preinstallation environment. The target host is configured into a DHCP mode to allow the target host to establish a network connection to a backup management server. Details about the host are received from a user. A listing of BMR backup copies corresponding to the host details are retrieved from the backup management server. A selection of a BMR backup copy to be restored onto the target host is received. Network configuration details corresponding to the selected BMR backup copy are downloaded from backup storage. A recovery wizard at the target host is populated with the network configuration details.

Abstract: Embodiments of the invention relate to methods and systems for efficiently sharing assets such as files and folders between a host computer system and a client computer system while minimizing the amount of work the client must perform to efficiently transfer an asset. In one or more embodiments, assets such as files and folders that are to be shared or transferred are placed in appropriate network slice queues by the hosts rather than the clients. These network slice queues allow the files and folders to be placed in slices without utilizing the resources of the clients as well as much of the available network resources. This ensures efficient use of network resources, while minimizing the amount of work the hosts and/or clients must perform in order to perform a backup.

Abstract: Aspects of the subject technology relate to a system configured to receive a set of network snapshot segments from an output stream of a stream processing service, compile the set of network snapshot segments from the set of messages into a first network snapshot and a second network snapshot, and compare the first network snapshot and the second network snapshot to identify a difference between the first network snapshot and the second network snapshot.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager and by an application, a file request for a file stored in a FBB, wherein the FBB is stored in a backup storage system, identifying, using a FBB metadata file of the FBB, a storage location of the file, initiating generation of a temporary storage device, storing a copy of the file in the temporary storage device using the storage location and the FBB, and initiating, after the storing, access to the copy of the file for the application.

Abstract: A method for performing a data backup process on a cluster includes: obtaining a backup generation request for virtual machines; in response to obtaining the backup generation request: generating a first set of backup groupings based on the backup generation request where each of the first set of backup groupings includes at least one of the virtual machines; issuing a disable migration command to a plurality of production hosts where each of the plurality of production hosts is associated with at least one of the virtual machines; identifying, after the issuing, a virtual machine of the virtual machines that is migrating; removing, based on the identifying, the virtual machine from the first set of backup groupings to obtain a second set of backup groupings where the virtual machine is placed in an excluded group after the removing; and backing up the second set of backup groupings.

Abstract: A method provides for receiving network traffic from a host having a host IP address and operating in a data center, and analyzing a malware tracker for IP addresses of hosts having been infected by a malware to yield an analysis. When the analysis indicates that the host IP address has been used to communicate with an external host infected by the malware to yield an indication, the method includes assigning a reputation score, based on the indication, to the host. The method can further include applying a conditional policy associated with using the host based on the reputation score. The reputation score can include a reduced reputation score from a previous reputation score for the host.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a backup agent, a FBB generation request for a file system at a point in time, in response to the FBB generation request: identifying a target backup storage system in which to store the FBB, identifying a target exposed application programming interface (API) associated with the target backup storage system, generating a FBB corresponding to the FBB generation request, wherein the FBB comprises a FBB metadata file, wherein the FBB is in a common data streaming format (CDSF), generating an API command based on the FBB and the target exposed API, and initiating storage of the FBB in the target backup storage system using the API command.

Abstract: A changed block tracking (CBT) driver at a production host tracks, in a bitmap, changes made to a source volume of the production host since a last backup. A command is received to perform a differential backup of the source volume. A request is issued to a copy service to take a snapshot of the source volume. The bitmap is embedded into the snapshot. The snapshot is mounted on a backup proxy, different from the production host. The backup proxy retrieves the bitmap from the snapshot and conducts the differential backup of the source volume to secondary storage, thereby backing up the changes made to the source volume since the last backup according to the bitmap.

Abstract: A synthetic full backup of a source volume is retrieved, the synthetic full having been created from merging a backup chain including an incremental backup into a full backup. The full backup corresponds to a state of the source volume at a first time. The synthetic full corresponds to a state of the source volume at a second time, after the first time. A bitmap embedded into a snapshot of the source volume taken at the second time is retrieved. The bitmap identifies data from the source volume copied to secondary storage for the incremental backup. The backup chain is regenerated by copying from the snapshot the data identified by the bitmap to a regenerated incremental backup.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager, a FBB mount request for a FBB mount of a FBB from an application, wherein the application is executing in a production host environment, in response to the FBB mount request, the FBB metadata file manager: identifies a FBB in a backup storage system, obtains a FBB metadata file corresponding to the FBB from the backup storage system, performs an attribute analysis to identify the storage location attributes in the FBB metadata file, stores a FBB virtual file system in the production host environment using the storage location attributes, and enables access to the FBB virtual file system by the application.

Abstract: A method for performing a backup includes: receiving, by a computing device, a native view request for a graphical user interface (GUI) of a local file system; intercepting, by a backup services agent executing on the computing device, the native view request before the GUI is generated; obtaining, by the backup services agent and in response to intercepting the native view request, a file system backup metadata associated with the local file system from a backup storage device and a local file system metadata associated with the local file system from a local storage of the computing device; generating a combined file system content list using the file system backup metadata and the local file system metadata; generating the GUI using the combined file system content list; and displaying, on a display of the computing device and to a user, the GUI.

Abstract: A method for backing up standalone data and clustered data on a node, that includes receiving, by a backup agent, a first backup request, making a first determination that a backup process is not active, and based on the first determination, identifying a first type of data specified in the first backup request, where the first type of data is the standalone data, locating, using a first backup policy, the standalone data in the node, begin generating standalone backup data from the standalone data, receiving, by the backup agent, a second backup request, making a second determination that the backup process is active, and based on the second determination, queuing the second backup request.

Abstract: A method for managing data includes obtaining, by a universal connector, a backup request for a backup of a set of files, in response to the backup request: performing a file system analysis on the set of files to determine an ordering of files to be accessed for the backup, generating a set of file read requests based on the ordering of files, sending a data access request based on the set of file read requests, obtaining a response from the NAS server, wherein the response comprises data associated with the set of files, and generating the backup using the data associated with the set of files.