One of the key features of RAIDiator 2 is the ability to use the new incremental backup capability in conjunction with snapshots. If you're not familiar with snapshots, it's a read-only image of your original share frozen at the specified time you took the snapshot. You can be making more changes to your original share, but your snapshot still looks like your share at that given time. This is important especially when you backup data.
Backup scenario
For this example, we have two ReadyNAS, one used for normal day-to-day file serving, and one delegated as a backup. We'll call the two hosts "Primary" and "Secondary". Our example will backup snapshots from Primary to Secondary on a daily basis, however we want the ability to restore from up to a week's worth of changes. For simplicity, let's use the share [work] on a Primary that will be your backup source and the backup target will be on Secondary in the share [backup].
Schedule snapshot
You can do this by first scheduling snapshot to take effect every day, let's say at 2am in the morning. Go to the Share/Snapshot tab and set up snapshot once daily at 02:00, and click Apply. This sets up your snapshot schedule.
Create backup jobs
Now go to the Backup tab, and we'll create 7 jobs (job1-job7), all backups occuring from share [work-snap] from Primary, i.e. //Primary/work-snap. Note that we append "-snap" to the share name because we will be backing up the snapshot.
For destination, select the [backup] share on the ReadyNAS and enter a path. For path, specify Sun for job1, Mon for job2, ..., Sat for job7.
For schedule start time, enter 02:05. This allows the snapshot to be in place right before the backup job starts. Select Sun for job1, Mon for job2, etc. so that this backup job only occurs on that specified day.
For backup option, specify First time for "Schedule full backup". This way after the first backup, all backups will be performed as incremental and thus will be much quicker.
Additional comments
As with an backup job, you should first run it manually to make sure connection, access, file permissions, and capacity utilization all work as expected before deploying the backup schedule.
