User Manual

Table Of Contents
The Import Public Key window closes and the Access List window shows the filename
and fingerprint for the first ReadyNAS device.
13. Click the Close button.
Seed a ReadyDR Job
When a ReadyDR job first runs, all of the data on the share or LUN must be transferred
to the destination. For large shares or LUNs, transfering this much data over the network
can take a long time. You can eliminate this large initial network transfer by seeding the
job by transferring the data using removable media.
If you seed a ReadyDR job, it must be seeded before the job runs the first time. When
you create the job, you can select the Export seed for this job checkbox to stop the
job before it runs. You can then create the seed archive. After importing the seed archive
on the destination device, you restart the job.
You create a seed by exporting the share or LUN after you create the job. For more
information about creating a seed file, see Monitor and Change ReadyDR Jobs on page
295.
Create a ReadyDR Job
A ReadyDR backup job backs up the snapshots on a share or LUN. The destination must
be a ReadyDR share, which is created when you create the job.
Before you create a ReadyDR job between a local and remote system, you must
download the public key for the system on which you are creating the job, and import
that key to the other device. If you log in to the other system over HTTPS from the system
creating the job, the systems exchange the key for you, otherwise you must manually
exchange the keys before you create the job. For information about exchanging the
key, see Load System Access Key Before Using ReadyDR on page 290.
The initial data transfer in a ReadyDR job transfers all of the data in the share or LUN. If
this transfer occurs over a network, it might take a long time if the network is slow. During
job creation you can create a seed archive file, copy it to removable media, and import
it to the destination, and avoid the initial network transfer. For information about seeding,
see Seed a ReadyDR Job on page 292.
Note: A destination LUN is always a thin LUN, even if the source LUN is a thick LUN.
For information about thick and thin LUNs, see Thin and Thick Provisioning on page 95.
Software Manual292Backup and Recovery
ReadyNAS OS 6.10