NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Volume backup via rsync: exclusions format
Firmware 6.5.0. There are several existing threads on setting up backups using the rsync protocol, and a little bit of discussion about how to specify exclusions. Since I just got my first ReadyNAS have spent the afternoon figuring out how to configure a backup the way I wanted it, I wanted to share what I figured out. You can figure most of this out from a careful study of rsync, but it's a little difficult when you don't know the exact form of the rsync command line that results from input to the graphical configuration. My specific use case was a desire to do a backup of the only (default) volume to a USB drive, while omitting snapshots and some specific shares. System prep: Plug the drive in. Find it in System->Overview, click the gear next to it, and format it. (Warning: This deletes all data on the drive.) Select the file system you want to use. I used ext4, assuming that a native Linux OS would be faster. I assume this would work with a Windows-compatible file system, also, which would make it easier to access the backup from a Windows system. Mine was a used drive with old data on it that I didn't care about. Make sure that rsync is turned on in System->Settings. In Shares, find the drive, which will be somewhere under the server's "media" folder. Mine was named USB_HDD_1. Make a note of this for later. Choose Settings from its context menu. Under Network Access->RSYNC, turn this protocol on, make sure that the default access is read/write, and disable password protection. If you care about security, you can add "localhost" to the list of hosts allowed to access. (I assume this makes it inaccessible via rsync to other systems on the network, but have not yet verified this.) You may also turn off other protocols. Create a backup with these characteristics: Source: Type: Local Location: /data (Use whatever the name of your volume is; the default volume for a new system is "data".) Destination: Type: Remote Host: localhost Protocol: remote: Rsync Server (Obviously it's not really remote. SSH is unnecessary since data is not leaving the server.) Share: USB_HDD_1 (Use whatever you found as the name of the drive.) (Leave other fields empty.) After creating the backup, edit its settings. For the Source you should see Type as "volume" and Name as "volume: data" (or whatever your volume name is). Everything else is blank. Under Destination, you should see Type as "remote", Name as "remote: RSync Server", Host as "localhost", and Path as something like "USB_HDD_1" based on what you picked earlier. Under Advanced, disable compression (there's probably no point to it since the data is not leaving the server). You can now add exclusions here. The exclusions are matched against file path names during the backup. They use forward-slashes as directory separators, Unix-style, of course. If a directory is excluded, everything under it is also excluded. (Rsync is more flexible than that, but such power is not accesible through the Web interface.) Here are some basic rules on how to write them: An asterisk matches any sequence of characters, except directory separators (forward slashes). For example, an exclusion like "*.jpg "causes all files ending in ".jpg" to be excluded, wherever they are in the tree. Two asterisks match any sequence of characters, including directory separators. An exclusion that ends with a slash matches only directories, not files. So an exclusion "snapshot/" will skip any directory that is named "snapshot", no matter where it appears in the tree. (That would be a way to exclude visible snapshots, if you have shares on which you made snapshots accessible.) An exclusion that starts with a slash has to match from the beginning of a path name. The path names against which the patterns are matched start with the volume name. So in my case, to exclude a share, I use for example "/data/Pictures/". If you were backing up a particular share or directory, you would start the exclusion with the directory's name (not its whole path), for example "/Pictures/2011/Awful/" if your backup source was the Pictures share, or "/2011/Awful/" if your source was the 2011 directory on the Pictures share. For a volume backup of volume "data", you may want to define these exclusions: /data/._share/ (Excludes snapshots.) /data/*/snapshot/ (Excludes snapshots on volumes configured to make them accessible to users.) /data/.timemachine/ (I don't have any Apple computers, but I assume this is where Time Machine stores their backups. You may or may not want this.) /data/.vault/ (I haven't used ReadyVault; I assume it stores something here.) /data/.apps/ (Maybe apps store data here? Anyone know?) Anyway, I hope someone else finds this useful! None of the existing discussions that I found discussed how to "root" ReadyNAS's rsync backup exclusions, which was a key piece of missing information for me.Time Machine Constantly Failing After A Few Seconds - 6.9.4 (Hotfix 1) - MacOS High Sierra (10.13.6)
Recently, after several months of sucessful Time Machine backups, I received a Mac system error that there was something wrong with my Time Machine backup, and the system would need to create a new one. I clicked on OK, and the system did what it had to do. Since then however, I have been unable to get the first (new) backup to be successful to the ReadyNas 214. I have been able to make Time Machine backups to an external 2TB drive, without any issues. When backing up to the RN disk , the backup goes through the Preparing backup... stage, then copies less than 1 GB of 523 GB (the most recent test got to about 300MB, and the one before, 74MB, and the one before that, about 118 MB), only to begin the Stopping...process without any other error. On the RN itself, I have: removed any Private TIme Machines, rebooted, and added them again. removed the Public Time Machine, rebooted, and added them again. rebooted the machine for the sake of rebooting. confirmed there is ample space for the drive, both in relation to available space on the HD and in relation to the required space for the first backup. On my Mac, I have: removed any Private TIme Machines, rebooted, and added them again. removed the Public Time Machine, rebooted, and added them again. rebooted the machine for the sake of rebooting. In the HD, I have confirmed that the SparseBundle files are deleted for the drives I was removing, and created when a drive is created on the RN (image attached). As already written, I have been able to successfully backup to an external drive without any issues. Thanks for any insight you can provide. 6.9.4 (Hotfix 1) - MacOS High Sierra (10.13.6)Sync to Dropbox
Hi, I'm using ReadyNAS 312 (6.9.3) and have set "Upload local storage changes only" to backup my NAS (70GB, 30.000 files) to Dropbox. But not all files are copied. Some folders are empty in cloud but not in NAS. I have reseted the sync (off/on -> reconfigure) but it doesn't help. What could be the cause? Is there some log regarding sync to Dropbox? Thanks, Tommy
Readynas 312 fw update failed
Hi, I've been using RN312 since few years on Raid 1 (4tb each drive), All good till date but today I got new hard drive to replace the existing ones which were also working perfectly. So I removed the Disk 1 and added a new 4tb drive as Disk 1. to sync it with the Disk 2. The drives were resyncing but in between I got some power issue that stopped the nas. I removed the new drive and booted the NAS with Disk 2 only but it was not showing any data and showing message "Remove inactive volumes to use the disk. Disk #1. Well I shut down the NAS and added back the new Disk 1 drive intact and after rebootitng the NAS I got the screen below, although the old drive (Disk 1) which I removed is having no issues and data is intact in my knowledge but now should I wait for the NAS to fix the drives (New Disk 1 & old Disk 2) itself or should I start planning to extract data from the old Disk 1 drive? ThanksReadyDR Unknown Error 255 on ReadyNAS 422
I recently noticed our ReadyNAS unit was not backing up to our offsite ReadyNAS. We are getting an unknown error 255. Both units were working fine for months. I tried updating both units to the most recent firmware 6.9.4, we had 6.9.0 prior to that. In the history is shows that it connected and with average durations from 2-8 hours some as high as 10 or 20 hours which was normal before when it did complete the backup. I have attached a copy of the ReadyDR logs. We do use a DDNS service on the offsite unit. I have verified this is still working correctly.Mac Restore from Time Machine from ReadyNAS fail.
Hi all I have recently changed the HDD of a Mac of mine and put a new SSD. After the OS installation, El Capitan, it asked as usual if I wanted to restore all the files from a Time Machine Backup. The problem is when it started searching in the network, the Mac couldn't find the time machine backup located in the readynas, which was in the same network and active. It has been the only moment that I needed my readynas and it failed... I tried to put manually the server address, afp://...etc.etc., that I have found on the properties of the backup folder in the ready nas, but it couldn't access it too, as if it wasn't visible. Luckily I have managed to do it another way using the old HDD, but what about a real failing of the whole HD happened? Can you suggest me the proper how-to in case it should happen in the future? Thanks a lot. Giovanni
