Source: http://www.rnasguide.com/2010/09/23/rsync-backup-to-usb-disk/
Rsync is arguably my favourite protocol for backups. Whilst it is slow for full backups. It’s a great protocol for incremental backups. It compares files on the source and destination and only makes incremental changes to files. So if you have a 1GB file and add 1MB only 1MB needs to be backed up. The time taken to do the necessary calculations can make Rsync appear deceptively slower than it really is. There are some great guides for backing up a ReadyNAS to another ReadyNAS using Rsync e.g. Using Rsync for NAS-to-NAS Backups and Setting up Rsync over SSH but you can also use Rsync when backing up to a USB disk attached to the ReadyNAS!
Here’s what you need to do:
First do a full USB backup normally using Frontview backup.
Then:
1. Under Services > Standard File Protocols turn Rsync on.
2. Go to Volumes > USB Storage (if not found here the settings for the USB drive will be under Shares > Share Listing) and turn on Rsync for the USB drive and set the permissions.
3. Go to Backup > Backup Listing, and open a backup job’s properties to edit it.
4. Change the backup job properties to use Rsync. I can’t remember whether 127.0.0.1 (localhost) works. If it doesn’t work you can try the static IP address of the NAS.
5. Specify the path. This will be the name of the USB HDD e.g. USB_HDD_1 or perhaps USB_HDD_1/foldername
6. Press Test Connection to make sure you have the backup job settings correct.
7. If you want the backup to be an exact mirror of the source i.e. wipe the USB HDD (or folder inside that if specified), then make sure that the “Remove deleted files…” option is checked.
8. Check the rest of the settings and make appropriate changes (if any) then run the backup job.
Responses to “Rsync backup to USB disk”
Jason Harrison
August 25th, 2011 at 6:37 am
If you want to copy the entire ReadyNas, including the TimeMachine share you need to set the destination USB drive to be accessed by Rsync. An Rsync server can only access exported modules, which doesn’t include C: or the TimeMachine share.
Here are the steps to backup your entire ReadyNas (rather than just one share) to an attached USB drive:
1. Under Services > Standard File Protocols turn Rsync on.
2. Go to Volumes > USB Storage (if not found here the settings for the USB drive will be under Shares > Share Listing) and turn on Rsync for the USB drive and set the permissions. You may also want to set the Rsync login and password.
3. Go to Backup > Backup Listing, and open a backup job’s properties to edit it. Or add a Backup Job.
4. Set the Backup Source settings. Select: “Volume: C” from the menu. Leave blank the Host, Path, Login, and Password fields.
5. Set the Backup Destination settings.
Select “Remote: Rsync Server”
Set Host to localhost
Path is the Rsync exported module of the attached USB drive. Something like USB_HDD_2. It will be listed in the menu of possible destination types/locations as “Share: USB_HDD_2″. Just copy that share name into the Path field.
Login and Password as you set in Step 2.
6. Press Test Connection to make sure you have the backup job settings correct.
7. If you want the backup to be an exact mirror of the source i.e. wipe the USB HDD (or folder inside that if specified), then make sure that the “Remove deleted files on target” option is checked.
8. Check the rest of the settings and make appropriate changes (if any) then run the backup job.
It is possible that the Test Connection button will report that the connection works, however the backup will fail if the Path on the Rsync server (the Rsync exported module name) is not specified or correct. Test the backup and check the logs to make sure you have everything working.
Accessing the Boot Menu
Use the boot menu to restart or troubleshoot your ReadyNAS unit. Your unit has the following boot modes:
Ultra 2 / Ultra 2 Plus / Pro 2
To access the boot menu:
Boot Mode Status Indicator
Normal Power LED is lit.
Factory default Disk 1 LED is lit.
OS reinstall Disk 2 LED is lit.
Tech support USB and backup status LED is lit.
Skip volume check Power LED and disk 1 LED are lit.
Memory test Power LED and disk 2 LED are lit.
Disk test Power LED and USB and backup status LED are lit.
Press and release Reset button to confirm your boot menu selection.
The system boots in the selected boot mode.
Ultra 4 / Ultra 4 Plus / Pro 4
To access the boot menu:
The system boots in the selected boot mode.
Ultra 6 / Ultra 6 Plus / Pro 6
To access the boot menu:
The system boots in the selected boot mode.
Pro Pioneer / Business Edition
To access the boot menu:
The system boots in the selected boot mode.
NVX / NVX Pioneer Edition
To access the boot menu:
The system boots in the selected boot mode.
Duo / NV / NV+ / X6/600
To perform an OS Re-install or Factory Default, this is managed via the Reset button on the back of the chassis.
To perform other options such as Skip Volume Check, Tech Support Mode, and Memory Test, this is managed via the Power button.
| Button to Hold | Time to Hold | LED flashes | Boot Menu Mode |
|---|---|---|---|
| Power | 5 seconds | 1 | Skip Volume Check |
| Power | 10 seconds | 2 | TFTP Boot |
| Power | 15 seconds | 3 | Tech Support Mode |
| Power | 20 seconds | 4 | USB Boot |
| Power | 25 seconds | 5 | Memory Test |
| Reset | 5 seconds | 1 | OS Re-install |
| Reset | 30 seconds | 2 | Factory Default |
Direct connection to NAS
How to Direct Connect to your ReadyNAS
By sphardy, on September 17th, 2010
(Post ShortCut: http://sphardy.com/web/directconnect)
When encountering a problem with a ReadyNAS device, it is often useful during the process of diagnosing that problem to eliminate the network to which the ReadyNAS is connected to determine it the issue is truly with the ReadyNAS, or due to the network itself.
Any ReadyNAS device can be connected directly to a client via a standard ethernet cable – there is no requirement for a cross-over cable as the ReadyNAS ethernet ports are autosensing. Therefore, to make the direct connection work, it is simply a matter of ensuring the client is configured with an appropriate IP address and subnet mask.
For ReadyNAS devices with Static IP addresses
In the case where the ReadyNAS device has already been configured with a static IP address, a direct connection can be established by setting the client to have an IP address on the same subnet, and a subnet mask of 255.255.255.0. For example:
If the ReadyNAS device has a static address of 192.168.0.100, configure the client to have an address 192.168.0.xxx – where xxx can be any integer between 1 and 250 (except, in this case, for 100 which is the IP address of the ReadyNAS) Google “changing IPv4 settings” for your client if you are unfamiliar with doing this.
Once done, directly connect the client to the ReadyNAS device with a standard cable and it should be immediately available to the client
For ReadyNAS devices with Dynamically Assigned IP addresses
If the ReadyNAS device is setup to obtain its IP address from a DHCP server, then additional steps are required to direct connect to it.
In the absence of a DHCP server, once booted the ReadyNAS device will default to the IP address 192.168.168.168 at which point the connection should be established. While it should not be necessary to reboot the ReadyNAS to ensure it resets its IP address to the default once directly connected to a client, this is suggested as a precaution.
Accessing the ReadyNAS Device
Once the connection is configured and made, Frontview should be immediately available at https:<nas_ip_address>/admin – in the above examples at either https://192.168.0.100/admin or https://192.168.168.168/admin.
If for any reason Frontview cannot be accessed, it is recommended to install & run RAIDar to verify that the ReadyNAS device has properly booted and is available, and also that the IP address is as expected. The following is an example of a successful boot, with the ‘LEDs’ to the left indicating a successful boot and the actual IP address(es) highlighted in the center:
If, after verifying the NAS has booted and the IP addresses being used are correct, it is still not possible to direct connect, first try a new ethernet cable. While it is rare for cables to simply ‘break’ there may be issues due to a slightly damaged connector or a broken wire within the cable.
If the connection still fails, then it would be advisable to contact Netgear Technical Support