NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Making Time Machine work with the ReadyNAS
The step-by-step how-to can be found here.
I recently purchased a ReadyNAS Duo for use on my home network (we have some PC laptops and a MacBook Air; everything is connected by a WRT310N wireless router).
One of my goals for the NAS was to use it for Time Machine backups of the MacBook Air. I followed the directions at http://www.readynas.com/?p=253 (which I thought were quite good, though Spotlight seems to "forget" that I've asked it not to index the Time Machine share). I think I got exactly one good backup.
After that, things became a real mess. The backup would start, but performance during the backup was extremely sluggish culminating in a never ending "pinwheel of death." This forum among others mentioned using the Console to track the progress of Time Machine backups, and this proved to be the key. After letting Time Machine run overnight and then doing a forced (hold the power button down) restart in the morning, I checked the "system.log" and found a whole lot of messages like this:
I'm a mechanical engineer, and still have only the vaguest notion of what these messages mean, but Google identified "Virex" as my virus scanner, McAfee 8.6 (I think that's the correct version number, but am not sure. if you read on you'll see why I don't know for sure anymore).
I fiddled around with the virus scanner settings, adding all the shares on the NAS to an exclude list and tried to run a Time Machine backup. No luck; I got the same sort of messages.
Fortunately, uninstalling the virus scanner completely seems to have solved the problem. I've now done a pleasantly uneventful backup.
Now I just have to find a new virus scanner.
One of my goals for the NAS was to use it for Time Machine backups of the MacBook Air. I followed the directions at http://www.readynas.com/?p=253 (which I thought were quite good, though Spotlight seems to "forget" that I've asked it not to index the Time Machine share). I think I got exactly one good backup.
After that, things became a real mess. The backup would start, but performance during the backup was extremely sluggish culminating in a never ending "pinwheel of death." This forum among others mentioned using the Console to track the progress of Time Machine backups, and this proved to be the key. After letting Time Machine run overnight and then doing a forced (hold the power button down) restart in the morning, I checked the "system.log" and found a whole lot of messages like this:
Sep 18 06:41:01 eponymous-2 kernel[0]: Virex Kext: "monitorActivity(/private/var/log/system.log) for action open file for write failed"
Sep 18 06:41:01 eponymous-2 kernel[0]: Virex Kext: "monitorActivity(/Volumes/TMeponymous/eponymous_XXXXXXXXXXXX.sparsebundle/bands/20) for action close file after modify failed"
I'm a mechanical engineer, and still have only the vaguest notion of what these messages mean, but Google identified "Virex" as my virus scanner, McAfee 8.6 (I think that's the correct version number, but am not sure. if you read on you'll see why I don't know for sure anymore).
I fiddled around with the virus scanner settings, adding all the shares on the NAS to an exclude list and tried to run a Time Machine backup. No luck; I got the same sort of messages.
Fortunately, uninstalling the virus scanner completely seems to have solved the problem. I've now done a pleasantly uneventful backup.
Now I just have to find a new virus scanner.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
