Methods and systems for automatically upgrading or synchronizing a remote data management agent running on a remote host machine (e.g., a hardware server) to a particular version that is in-sync with a corresponding version used by a cluster of data storage nodes controlling the remote data management agent are described. The remote agent may be initially installed on the remote host and subsequent updates to the remote agent may be performed using the remote agent itself without requiring intervention by the remote host. The remote agent may comprise a backup agent and a bootstrap agent that are each exposed in different network ports or associated with different port numbers or networking addresses. The backup agent may perform data backup related tasks for backing up files stored on the remote host and the bootstrap agent may perform upgrade related tasks for upgrading the backup agent.

Embodiments are described for storing array snapshots of a file system in networked attached storage (NAS) device. A system and process determine an organization of the file system comprising directories and files in a defined hierarchy, and a size of each file and a number of files in each directory. One or more slicer processes slice the file system into a number of slices, wherein each slice contains at least one of: a defined number of files or files having a defined total size. Backup agents are deployed as proxies to back up the slices to the NAS device, and the slices are backed up as array snapshots in the NAS device.

A method, electronic device, and a computer readable medium for managing backup data that includes determining an expiration time of backup data in a data set to be backed up in a source storage device, and determines a priority of the backup data to be migrated in a migration operation to be performed based on the expiration time. The method may also include migrating backup data with the same priority in the data set to be backed up to a target storage device to reduce a write amplification factor of a storage device, and prolong the service life of the storage device.

A database replication using heterogenous encoding is provided. Aspects include obtaining a database and analyzing a data pattern of data in the database. Aspects also include identifying a plurality of candidate encoding formats and evaluating a computing cost for encoding the database for each of the plurality of candidate encoding formats. Aspects further include selecting an encoding format from the plurality of candidate encoding formats based at least in part on the computing cost and storing a backup copy of the database using the encoding format.

Systems and methods for efficient and secure management of encrypted “snapshots” for a remote provider substrate extension (“PSE”) of a cloud provider network substrate are provided. The PSE may request and obtain a snapshot from the cloud provider network substrate, restore a volume from the snapshot, make changes to data in the restored volume, and/or initiate the creation and storage of a new snapshot that includes incremental updates to the original snapshot to reflect the changes made to data in the volume. An encrypted snapshot stored within the cloud provider network substrate may be decrypted using a cloud provider key designed for internal use only, and then re-encrypted using a PSE-specific key before providing the snapshot to the PSE, thereby avoiding the sharing of the cloud provider internal use only key outside the cloud provider network substrate.

In some examples, a networked computing system comprises a backup node cluster of a backup service in communication with a host database node cluster of a host, a host database at least initially undiscovered by the backup node cluster, one or more processors coupled with memory storing instructions that, when executed, perform operations comprising at least installing a backup agent on at least one node of the host database node cluster, registering the host at the backup service, based on the host registration, triggering a host database discovery process to discover the undiscovered database automatically, the discovery process including a discovery call, in response to the discovery call, receiving metadata relating to the discovered database, and communicating with the discovered database.

Virtualization sprawl can lead to virtual machines with no designated periodic backup. If the data associated with these unprotected virtual machines is not backed up, it cannot be restored if needed, leading to system failures. A data storage system identifies and protects the unprotected virtual machines. For instance, the system compares a list of virtual machines with a list of computing devices having a designated backup policy in the data storage system and determines which of the virtual machines are unprotected. The system further automatically categorizes the unprotected virtual machines, identifies those unprotected virtual machines that remain uncategorized, and applies a default backup policy to the uncategorized and unprotected virtual machines to provide protected virtual machines.

The hybrid method (100) for storing digital information comprises: a configuration step (105), which comprises: a step (120) to define at least two information storage devices, at least one of the devices being local and not dedicated to storage, a step (125) to create a computer abstraction presenting common addressing characteristics between at least two storage devices, each abstraction being addressable by a central control device, iteratively, a dynamic step (110) to adjust local storage capacity, comprising: one step (130) of allocation, by at least one local device not dedicated to storage, of storage capacity and a step (135) of communication, to the central control device, of an allocated storage capacity and an execution step (115), which comprises: a step (140) to trigger a digital information backup, a step (145) of fragmenting digital information into at least one information segment, a step (150) of selecting, by the central control device and for each segment, a storage device according to the abstractions created and a step (155) of recording, on the selected storage device, the associated information segment.

Disclosed herein are system, method, and computer program product embodiments for multi-cluster distribution. In some embodiments, a server on a primary computing cluster receives an update to an object stored on the primary computing cluster and to be implemented by a secondary computing cluster. Furthermore, the server receives a request to distribute the object to the secondary computing cluster. The server further retrieves the object based on an object identifier or an identifier of the secondary computing cluster. Moreover, the server identifies the secondary computing cluster based on the object identifier or the identifier of the secondary computing cluster. The server then distributes the object to the secondary computing cluster via a persistent connection.

Methods and systems for generating backups are disclosed. To generate a backup, a snapshot may be generated. A snapshot may be a point in time representation of data, in contrast to live data which may be updated over time. To reduce the impact of snapshot generation, a method, system, and device for generating and maintaining a snapshot that utilizes fewer writes is disclosed. To reduce the writes, the snapshots may be generated by preferentially referring to already stored copies of data for the snapshot rather than storing an additional copy of data for the snapshot. The snapshots may be maintained by storing copies of data for the snapshot only when live data diverges from the snapshot.