Not what you're looking for? Return to the ReadyNAS Backup FAQ
ReadyDR has several configurable options to choose during ReadyDR job creation.
On completion send
Regarding this specific job, you can indicate when to receive alerts. By default, this is set to alert when there are errors only. Alternatively, you can also be alerted about the job's status changing (status and errors).
Bandwidth Limits
Bandwidth Limits help ensure that ReadyDR does not over-saturate the network, affecting performance of other clients using the network (especially when transmitting to another ReadyNAS over the internet).
The default value is Unlimited, meaning that there is no limit set. Enter a value in kilobytes to set a limit.
When performing a local to local ReadyDR job on a lower-end ReadyNAS device, you may need to enable bandwidth limits if you experience slow performance while ReadyDR jobs is running.
Compression
Transport compression is applied to the ReadyDR job using an lz4 algorithm.
Compression has three options:
- Disabled: disables compression.
- Better: provides a higher compression ratio, but results in more CPU usage. Should be used on smaller network pipes.
- Faster: provides faster transfer, but results in a low compression ratio.
Compression is disabled on a local to local job.
Encrypted Transport
ReadyDR can transport data between ReadyNAS devices using encrypted protocols, if desired. Your data is not encrypted once it reaches the destination.
By default, Encrypted Transport is disabled.
Encrypted Transport is unavailable on local to local jobs.
Wake On Lan before backup
Enter the MAC address in colon notation of the remote ReadyNAS. The source NAS will send a magic Wake-On-LAN packet to the remote ReadyNAS to wake it up.
The ReadyDR job will wait however many minutes are notated in the Time to wait(minutes) field for the remote NAS to wake up. Increase or decrease the time to wait to match your remote ReadyNAS's startup time (this varies by model, configuration). Even if the ReadyNAS is awake, the ReadyDR job will wait this mentioned time.
Your remote ReadyNAS waking up is dependent on enabling the Wake On LAN feature, located under System > Power in the Admin Page.
Export seed for this job
Seeding exports all currently existing snapshots from a share/LUN to a file, then requires importing the seed file to the destination ReadyNAS, avoiding an initial large network data transfer.
When Export seed for this job is checked, the ReadyDR job will be disabled after creation to allow for importing the seed.
You can export the seed to a USB or eSATA device, or leave the seed file in a share for later use.
When you're ready to import the seed from the source ReadyNAS, navigate to the Admin Page of the remote unit, click the Backup tab, click the gear icon on the destination job, then click Import.
After seeding, resume the job by clicking the gear icon on the source ReadyNAS and select Enable. From this point on, ReadyDR will start backing up incremental changes from the most recent snapshot to the oldest snapshot until the ReadyDR share matches the source share's snapshot layout.
Schedule
Snapshots
ReadyDR is a snapshot-based backup solution. The Add ReadyDR Job wizard will allow you to configure a smart snapshot schedule only (hourly, daily, weekly) on the source share. To use a custom snapshot schedule with ReadyDR, reconfigure the snapshots from the Shares tab. If the source share is already configured for a custom snapshot schedule, ReadyDR will allow that custom snapshot schedule to be used.
Backup
There are two types of backup schedules, Instant and Periodic.
- Instant backups send a snapshot to the destination immediately after taken, based on your configured source share's Snapshot schedule. Each transfer only consists of one snapshot.
- Periodic backups sends snapshots taken between the last time the ReadyDR job has run. A transfer could consist of many snapshots.
During a periodic backup, if a snapshot is not taken between the last time a scheduled ReadyDR job executed, ReadyDR will run but won't have any snapshots to send. In some scenarios (like periods of high IO or load), snapshots can take up to five minutes to finalize while the Backup Schedule tries to execute at the top of the hour. Plan ahead by setting custom executions to start well after a snapshot can take.