Abstract: A retention-based consistent hash ring process defines each file name in the system to include its expiration date (or time) as a prefix or suffix that is stored and indexed as metadata. The process uses a virtual node to represent adjacent expiration days to create virtual nodes based on individual days of the week. Each physical node contains the same number of labeled virtual nodes, and the consistent hash ring process is used to move files with the same expiration day to different physical nodes by looking for next labeled virtual nodes on the hash ring. This provides a way to locate the virtual node storage location by specifying a file's expiration date as part of the key used in the hash ring process, and distributes files that may otherwise be assigned to the same physical node through a backup policy.

Abstract: A method and system of providing estimates or recommendations for software lifecycle management tasks by obtaining and storing local timing and result data for a current run of an application task on a local client, and gathering global timing and result data in a server computer for a plurality of clients including the local client. The local client combines its local timing and result data with the global timing and result data to generate an estimated time completion and success probability for a next run of the application task. The local client uses a rule definition file to substitute function variables for text strings and recommendation text with the appropriate values from the combined timing and result data and outputs the final time estimate UI string and recommendation through a user interface for display to a user.

Abstract: Embodiments are described for a method and system of applying data protection software mechanisms to network equipment devices to auto-discover the networking equipment, save changes from memory (TCAM) to local storage, backup changes to protection storage, provide auditing and tracking history of changes, and provide the ability to deploy test/development copies of changes using software defined networking techniques.

Abstract: Embodiments are described for a method and system of applying data protection software mechanisms to network devices to auto-discover the networking equipment, save changes from memory (TCAM) to local storage, backup changes to protection storage, provide auditing and tracking history of changes, and provide the ability to deploy test/development copies of changes using software defined networking techniques. A coordinator protects network devices organized into a plurality of partitions by creating a backup of each network device, pushing backup policies to individual data protection units for the network devices within each partition to provide a consistent-state backup of the network devices, and backing up the configuration changes of the network devices to a protection storage device.

Abstract: Embodiments for optimizing data storage instances in a cloud environment in which metadata is stored and accessed separately from content data in multiple different instances of data storage units. A metadata and content data storage instance optimization process determines the status of different instances of virtual storage resources for both metadata and content data. Full instances are powered down when they are not needed, empty instances are deleted, and data of partially full instances is moved to other appropriate instances to create empty instances that can be deleted. The data storage instance optimization process is provided as part of a data protection search process that provides an execution environment and user interface to the optimization process.

Abstract: Described is a system that provides for granular and customized upgrades of sub-systems deployed within a third-part system. The system generates an upgrade manager service for implementation of a first sub-system upgrade package from within a third-party system that hosts the first sub-system. The system generates the first sub-system upgrade package according to a compatibility with a first sub-system version currently deployed in the third-party system to update the first sub-system with a feature(s) available in an upgraded version of the first sub-system. The system sends the upgrade manager service to the third-party system. The system receives a first request for the first sub-system upgrade package from the upgrade manager service running in the third-party system. The system sends the first sub-system upgrade package for implementation at the first sub-system by the upgrade manager service running in the third-party system.

Abstract: Embodiments for a method performing data migration such as backups and restores in a network by identifying characteristics of data in a data saveset to separate the data into defined types based on respective characteristics, assigning a data label to each defined type, defining migration rules for each data label, discovering assigned labels during a migration operation; and applying respective migration rules to labeled data in the data saveset. The migration rules can dictate storage location, access rights, replication periods, retention periods, and similar parameters.

Abstract: Embodiments for a method of storing documents using a document data protection process. Documents are first compressed and stored in a container along with selected metadata. An Document Record is created for each document. A Container Record is created for each newly created container, and a Backup Record is created for each container for each backup. Once the required records are created, the process facilitates the execution of backup operations, such as full or incremental backups of the stored documents. Data tiering is supported so that low cost object storage in the public cloud is used instead of expensive processing methods like deduplication. A user interface receives a user setting dictating a storage media storing the container based on a relative availability of the storage media versus cost of storage.

Abstract: Embodiments for a method of storing e-mail messages using a cloud native e-mail data protection process. E-mail messages are first compressed and stored in a container along with selected metadata. An Email Record is created for each e-mail message. A Container Record is created for each newly created container, and a Backup Record is created for each container for each backup. Once the required records are created, the process facilitates the execution of backup operations, such as full or incremental backups of the stored e-mail messages. Data tiering is supported so that low cost object storage in the public cloud is used instead of expensive processing methods, such as deduplication backups.

Abstract: Embodiments for a method performing data migration such as backups and restores in a network by identifying characteristics of data in a data saveset to separate the data into defined types based on respective characteristics, assigning a data label to each defined type by receiving user selection or automatically merging or selecting a priority label, from among many labels associated with a file, defining migration rules for each data label, discovering assigned labels during a migration operation; and applying respective migration rules to labeled data in the data saveset. The migration rules can dictate storage location, access rights, replication periods, retention periods, and similar parameters.

Abstract: One example method includes receiving a group of files, two or more of the files being of different respective file types, creating a backup saveset that includes the group of files, classifying each of the files in the backup saveset based in part on the respective file types of the files, assigning a respective storage media type to each of the classified files in the backup saveset, and transmitting the backup saveset to a storage site.

Abstract: One example method includes receiving, from an entity, a proposed entry for a ledger, where the ledger is shared and accessible by multiple users and includes a whitelist and a blacklist, determining, or assigning, a credibility score and rate limiter value for the entity, comparing the credibility score and rate limiter value with respective credibility score and rate limiter value thresholds, determining that the credibility score and rate limiter value meet or exceed the respective credibility score and rate limiter value thresholds, and submitting the proposed entry to the ledger.

Abstract: One example method includes receiving from a node, in an HSAN that includes multiple nodes, an ADD_DATA request to add an entry to a distributed ledger of the HSAN, the request comprising a user ID that identifies the node, a hash of a data segment, and a storage location of the data segment at the node, performing a challenge-and-response process with the node to verify that the node has a copy of the data that was the subject of the entry, making a determination that a replication factor X has not been met, and adding the entry to the distributed ledger upon successful conclusion of the challenge-and-response process.