Netgear RD5D (ReadyDATA Disk Packs) – ReadyDATA Disk Packs (SATA/NL-SAS/SAS/SSD) Software Guide

The replication status is reported at both the source and the destination systems in a 
replication relationship, and includes the age of the snapshot that is transferred and the size 
of the data that is transferred. For example, if a 50 MB snapshot was created 20 seconds 
before being transferred to a remote system as part of replication, the status that is reported 
is Target is 50

MB / 20 seconds behind source, or a similar status message. 

For more information, see the white paper Building Backup-to-Disk and Disaster Recovery 
Solutions with the ReadyDATA 5200 that is available from the ReadyDATA website at 

.

In a replication configuration, after data has been lost at the source system, or after the 
source system has been compromised, no special steps are required to recover data. If the 
configuration is one of continuous replication, the data on the destination is fully current. If the 
configuration is one of periodic replication, the data on the destination is current as of the last 
snapshot.

Once you have configured replication for each individual share and LUN on the source 
system, all data is available at the secondary location on the destination system. You only 
must provide users access to their share or LUN on the destination system.

After the source system has been repaired and brought back online, you have the option to 

configure reverse replication to replicate data from the destination system back to the source 
system. If a significant amount of data is on the original destination site, the first job after 
starting reverse replication can take a long time. You can substantially shorten this time by 
seeding the reverse replication. For information about seeding replication, see 

196.

When a share or LUN has a large amount of data and you want to replicate that data to 
another ReadyDATA, the initial replication job can take a significant amount of time because 
all of the data must be moved to the destination system. If the amount of data is large 
enough, and the connection between systems is slow, for example over a WAN, you can start 
up much more quickly by seeding the destination system with the complete, initial state of the 
source.

This speed-up can be especially valuable when you are reestablishing the original source 
during disaster recovery following the loss of the original source system.



Create the seed by exporting the source share or LUN. 

85, or 

Move the NAS with exported share or LUN to the same LAN as the destination system.

118.