Managed Data Remote Replication with DD Boost and NetWorker
DD Boost allows backup applications to manage and simplify file replication between multiple Data Domain systems, and using NetWorker as an example, the article details the step‑by‑step replication workflow, optional low‑bandwidth and encryption features, and how remote restores are performed.
DD Boost enables backup applications to manage file replication between two or more Data Domain systems that have DD Boost configured, simplifying Data Domain replication and tracking both local and remote backups.
Using NetWorker as an example, the managed file replication process works as follows:
NetWorker storage node initiates a backup task and sends data to the local Data Domain system.
The local Data Domain notifies NetWorker that the backup is complete.
Backup information is recorded in NetWorker's media database.
NetWorker storage node issues a clone (replication) task to a remote Data Domain system.
Data is copied from the local Data Domain to the remote Data Domain.
The remote Data Domain notifies the local Data Domain that replication is complete, and the local system then notifies NetWorker.
Clone information is recorded in NetWorker's media database.
Because the NetWorker media database contains information about the replicated data on the remote Data Domain, data can be restored directly from the remote system.
Two optional features can be enabled for Data Domain replication:
Low‑bandwidth optimization: When WAN bandwidth is limited, additional compression is applied to achieve replication; it must be enabled on both source and target Data Domain systems.
Encryption of managed file replication data: Provides encryption for data during replication; also requires enabling on both source and target systems.
Architects' Tech Alliance
Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.