Abstract: Described is a system (and method) for providing multiple types of granular delete operations for a cloud-based object storage. The system may include a server that acts as an intermediary between a client device and an object storage that stores client data. The server may allow a client to perform a hard delete (or permanent) delete and a soft delete. The server may perform a specialized processing to synthetically create the soft delete feature using a permanent object delete operation provided by the object storage. The specialized processing may include manipulating retention periods associated with objects depending on whether the object is subject to a hard delete or a soft delete. As a result, the server may provide the ability for clients to perform a soft delete at an object level using existing storage level APIs that do not directly support such a feature.

Abstract: Described is a system for synchronizing expiration times for incremental backup data stored on a cloud-based object storage. More particularly, the system may provide a layer of intelligence when updating the expiration times associated with backup data to ensure that a full recovery of the client data to a point-in-time of any incremental backup may be performed. To provide such a capability, the system may maintain specialized metadata identifying expiration times for objects and a list of objects required to perform a full recovery to a point-in-time for each of the performed backups (e.g. full or incremental). The system may access this metadata to identify which objects stored by a previous backup are still referenced by a subsequent backup. Based on the identified objects, the system may synchronize object expiration times to ensure objects are not prematurely deleted from the object storage.

Abstract: In general, embodiments relates to a method for managing a technical support session, comprising: obtaining technical support question from a technical support person (TSP) that is conducting the technical support session; determining that the technical support question is a duplicate of a prior technical support question; in response to the determination, obtaining a quality score for the technical support question; and displaying the quality score to the TSP in a user interface on a technical support system that the TSP is using the conduct the technical support session.

Abstract: A method for copying source data from a source server to a destination server, that includes initiating, by a source copy manager, a copy operation of the source data, where during the copy operation, the method further includes obtaining resource statistics, setting a data chunk size based on the resource statistics, copying a data chunk to a read queue, where the data chunk includes a portion of the source data, and where the data chunk has the data chunk size, and sending, from the read queue, the data chunk to a network device, and ending the copy operation.

Abstract: A method and system for implementing a topological view and insights of organization information technology (IT) environments based on bare-metal recovery and/or system-state recovery data and metadata. Often, one or many IT environment(s), affiliated with an organization, include various network resources, as well active directory service(s) for organizing, locating, and managing said network resources. Active directory service(s) may further gather and provide information pertinent to modeling a topological view of said network resources throughout the organization. Leveraging said information gleaned from any active directory service(s), as well as backup operation metadata generated during or following backup operations targeting workloads and their respective data, which support bare-metal and/or system-state recoveries, embodiments disclosed herein propose the construction of an organization metadata tree.

Abstract: A method for modifying a communication network includes: making a first determination, using monitored data, that scaling is required; in response to the first determination, executing an emulation using a modified network slice and the monitored data to generate an emulated response time, in which the monitored data comprises at least a request, a response to the request, and a corresponding response time for the request, in which the monitored data is analyzed to generate the modified network slice; making, based on the emulated response time, a second determination to implement the modified network slice; and initiating modification of the communication network using the modified network slice.

Abstract: A method and system for maintaining live database data across hybrid storage. Specifically, the disclosed method and system entail accessing live backup database data in part residing on local storage and in part residing on remote storage. That is, on occasion, available local storage capacity may fall short of the required free storage space to accommodate the full restoration or recovery of a given database. Accordingly, to overcome this shortfall, the disclosed method and system detect and cycle the recovery of frequently accessed asset (or database) data files, of the given database, from remote storage onto local storage.

Abstract: Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for creating and executing migration workflows to replicate or migrate data (collectively referred to herein as ‘migration’) from one device or set of devices to another device or set of devices (e.g., from one computing environment to another). The method of migration involves obtaining relationship information with regards to the applications that will be migrated from one device to another device or set of devices, and classifying the applications based on their relationships such as HAS-A and IS-A. Based on these classifications, one or more embodiments of the invention generate a relationship matrix in order to assign priority to the migration of each individual application. The applications are then migrated based on the matrix and assigned priorities.

Abstract: One or more embodiments of the invention performs an incremental backup by crawling only those folders which have changed. By comparing a folder's attributes with those in a backup's meta-data, an intelligent file system crawler can determine if the underlying files and sub-folders of the folder have undergone a change. If they have, then the one or more embodiments of the invention proceeds to crawl the underlying sub-folders. If the folder's attributes have not changed, then the intelligent file system crawler of one or more embodiments of the invention proceeds to the next folder and does not crawl the underlying sub-folders. By doing this, one or more embodiments of the invention can crawl the entire file system quicker, since those folders that have not undergone a change since the last backup was performed, do not have their sub-folders crawled.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, wherein the workload includes a group of two or more connected jobs, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining how many actors should be included in a swarm of actors necessary to perform all of the connected jobs, spawning the swarm of actors, and load balancing the connected jobs across the swarm of actors.

Abstract: A method and system for implementing a topological view and insights of organization information technology (IT) environments based on bare-metal recovery and/or system-state recovery data and metadata. Often, one or many IT environment(s), affiliated with an organization, include various network resources, as well active directory service(s) for organizing, locating, and managing said network resources. Active directory service(s) may further gather and provide information pertinent to modeling a topological view of said network resources throughout the organization. Leveraging said information gleaned from any active directory service(s), as well as backup operation metadata generated during or following backup operations targeting workloads and their respective data, which support bare-metal and/or system-state recoveries, embodiments disclosed herein propose the construction of an organization metadata tree.

Abstract: A method and system for shared workload anomaly detection across multiple hosts based on bare-metal recovery and/or system-state recovery data and metadata. Since at least said bare-metal recovery and/or system-state recovery metadata has information about each workload operating on one or many host(s), comparing said metadata across any set of hosts could provide the pattern of data being generated there-across. Further, other metadata generated by any shared workload instance(s), operating on a set of hosts, should be consistent across the set of hosts. Should a shared workload instance on one or more hosts generate metadata not sync with metadata generated from a baseline shared workload instance, such discrepancies could be a sign of unwanted anomalies that may warrant further analyses, alerts, etc.

Abstract: A method and system for workload anomaly detection for standalone hosts based on bare-metal recovery and/or state-system recovery data and metadata. In isolated circumstances, workloads tend to operate as expected, however, their behavior and/or functionality may become unpredictable when said workloads are exposed to other factors outside of isolation. Further, most of these other factors, as well as their influence on workload behavior and/or functionality tend to go unnoticed by administrators. Data and/or metadata, pertinent to bare-metal recovery and/or system-state recovery operations, may capture host-relevant information, including which workload(s) is/are installed on a host, which file-system objects maintained thereon belong to which installed workload, and what is the nature and storage location of each file-system object.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining whether or not any additional actors are needed to perform the workload, determining a number of reserve actors, when it is determined that one or more additional actors are needed to perform the workload, spawning the additional actors, and spawning the reserve actors, and load balancing the workload across a group that includes both the one or more actors and the additional actors that have been spawned, and the group does not include the reserve actors. The method also includes temporarily deploying one of the reserve actors to service a high priority workload.

Abstract: A method for managing data backup includes: making a determination that an asset source is a first type of asset source, in which a source client device comprises the asset source; generating, based on the determination, a data transfer path for a plurality of snapshots associated with the asset source between the source client device and a data protection system; initiating a backup for user data associated with the asset source to a target client device; obtaining the plurality of snapshots to the data protection system using the data transfer path, in which the user data is backed up in the target client device while at least a portion of the plurality of snapshots is obtained by the data protection system; and deleting the plurality of snapshots from the source client device, upon receipt of confirmation that the plurality of snapshots is successfully stored in the data protection system.

Abstract: A method for copying source data from a source server to a destination server, that includes initiating, by a source copy manager, a copy operation of the source data, where during the copy operation, the method further includes obtaining resource statistics, setting a data chunk size based on the resource statistics, copying a data chunk to a read queue, where the data chunk includes a portion of the source data, and where the data chunk has the data chunk size, and sending, from the read queue, the data chunk to a network device, and ending the copy operation.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining how many actors are needed to perform the workload, when a number of actors needed to perform the workload is determined, spawning the actors and assigning the actors to a pool, throttling the pool, and based on the throttling, load balancing the workload across the actors in the pool.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining whether or not any additional actors are needed to perform the workload, when it is determined that one or more additional actors are needed to perform the workload, spawning the additional actors, and load balance the workload across a group that includes both the one or more actors and the additional actors that have been spawned.

Abstract: In accordance with one or more embodiments of the invention, when restoring data from a backup that is at least partially stored on the cloud, the meta-data and data forming the backup are not in sync with the local meta-data. When restoring the data, once the backup data and backup data is copied to the desired location on the production host, the backup data and backup meta-data need to be linked back up. Once the backup data and backup meta-data is copied to the target production host, the backup meta-data is linked with the backup data and then the restoration is indicated as having been completed. By performing the linkage during the restoration, prior to the restore being indicated as being complete, delays in production workloads and productivity can be avoided.

Abstract: A method for managing a data protection module includes: obtaining client metadata of a client environment data protection module (CEDPM); analyzing the client metadata to extract relevant data; inferring at least a period of time a first user of the CEDPM spent to initiate performing a task, a number of steps taken by the first user to initiate performing the task, and a number of attempts made by the first user to initiate performing the task; obtaining at least an ease of use score, an automation efficiency score, and a success score for a product feature; obtaining a maturity rating for the product feature based on the scores; determining that the maturity rating for the product feature is less than a predetermined maturity rating; and sending a recommendation to a second user of a vendor environment (VE) data protection module to manage the maturity rating for the product feature.