NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mountain Lion Compatibility
Is there any early word on Mountain Lion compatibility for the ReadyNAS models?
I've read this entire thread, along with the other TM specific ones, and I'm still trying to figure out whether the ReadyNAS is ML-compatible or not. So I figured I would give it a shot myself. Before I continue, let me just say that the ReadyNAS is just a backup box to me. All I care about is TM, ReadyDLNA, and rsync (which is not from the Macs). TM worked for me on the combination of 4.1.8 and Lion/Snow Leopard. I have a Sparc NV and two Macs - one is a laptop connecting via wireless and the other communicates to the ReadyNAS via a gigE switch. I figured this was a pretty good combo for testing, so I updated both of the Macs to ML (I have not upgraded to 10.8.1 yet). I upgraded the ReadyNAS to 4.1.9 and factory defaulted it because that's how I roll. ReadyDLNA and rsync worked fine, so let's specifically talk about TM. Maybe I should have posted this is the TM sub-forum but this seems to be the ML thread that's getting the most attention. Anyway, I specifically did not upgrade to the 4.1.10 T3 beta because I don't share out the backup or media shares with CIFS or AFP. I do know that AFP is used for TM, but that share is specifically designed for that purpose and I suspected that it does not have the ownership issues that are fixed by the beta. So this is what I found...
First of all, my laptop on wireless was immediately able to find the ReadyNAS as a TM destination. However, I couldn't actually select it as a backup destination without getting the errors described in this link -> http://www.trollop.org/2012/07/12/os-x-10-8-mountain-lion-time-machine-netatalk/. I was able to fix this, as other folks suggested, by checking the box that advertises AFP with Bonjour. I never had to do that with TM on SL or Lion. But after that I was able to get a full backup of the laptop, along with several incremental ones, and was able to go into the backups and restore some test files. So far, so good.
But the wired machine on the switch couldn't even see the ReadyNAS as a backup destination. That was actually the one I tried first because I thought it would be easier. Even after the laptop was working, no wired success. But then I remembered that the laptop just uses the built-in firewall (which is set to block everything except essential services - Bonjour is considered by Apple to be essential) and that I use a custom IPFW script for the wired machine because I use it as a server. I went back to the wired machine and stopped IPFW, and then I could see the ReadyNAS. I didn't go through the motions to set it all the way up but I'm confident it would work. I know most people aren't firewalling ports the old-school way like me - the only reason I mention it is because my custom setup permits inbound Bonjour, so it must take more than just Bonjour to make TM work. I think that's an ML change because TM on Lion worked fine with my firewall settings. Maybe after you discover/set up the backup destination Bonjour can take it from there, whether you mounted it manually or not. But I want to make sure this works properly without having to mess around with it. I've never had the issues that some have had with sparsebundle corruption, and I'm hoping to keep it that way. I saw some SSDP packets in the mix, and I tried permitting both Bonjour and SSDP but that didn't seem to help. I'll update this post if I get a chance to do some more packet captures.
So here's what I recommend for success with TM on Mountain Lion and a Sparc ReadyNAS: upgrade the ReadyNAS to 4.1.9 or better as needed, advertise AFP with Bonjour, and make sure your network gear in the middle is not interfering with the connectivity required to discover the ReadyNAS and mount the TM share. I would always recommend directly connecting the ReadyNAS to the Mac to temporarily take the network out of the equation. One other thing, I know this post is way too long but I did come across the tmdiagnose command, which looks like it's made for gathering TM issues for a support case with Apple. But perhaps someone here might get some use out of it. Do a man tmdiagnose for more details.
First of all, my laptop on wireless was immediately able to find the ReadyNAS as a TM destination. However, I couldn't actually select it as a backup destination without getting the errors described in this link -> http://www.trollop.org/2012/07/12/os-x-10-8-mountain-lion-time-machine-netatalk/. I was able to fix this, as other folks suggested, by checking the box that advertises AFP with Bonjour. I never had to do that with TM on SL or Lion. But after that I was able to get a full backup of the laptop, along with several incremental ones, and was able to go into the backups and restore some test files. So far, so good.
But the wired machine on the switch couldn't even see the ReadyNAS as a backup destination. That was actually the one I tried first because I thought it would be easier. Even after the laptop was working, no wired success. But then I remembered that the laptop just uses the built-in firewall (which is set to block everything except essential services - Bonjour is considered by Apple to be essential) and that I use a custom IPFW script for the wired machine because I use it as a server. I went back to the wired machine and stopped IPFW, and then I could see the ReadyNAS. I didn't go through the motions to set it all the way up but I'm confident it would work. I know most people aren't firewalling ports the old-school way like me - the only reason I mention it is because my custom setup permits inbound Bonjour, so it must take more than just Bonjour to make TM work. I think that's an ML change because TM on Lion worked fine with my firewall settings. Maybe after you discover/set up the backup destination Bonjour can take it from there, whether you mounted it manually or not. But I want to make sure this works properly without having to mess around with it. I've never had the issues that some have had with sparsebundle corruption, and I'm hoping to keep it that way. I saw some SSDP packets in the mix, and I tried permitting both Bonjour and SSDP but that didn't seem to help. I'll update this post if I get a chance to do some more packet captures.
So here's what I recommend for success with TM on Mountain Lion and a Sparc ReadyNAS: upgrade the ReadyNAS to 4.1.9 or better as needed, advertise AFP with Bonjour, and make sure your network gear in the middle is not interfering with the connectivity required to discover the ReadyNAS and mount the TM share. I would always recommend directly connecting the ReadyNAS to the Mac to temporarily take the network out of the equation. One other thing, I know this post is way too long but I did come across the tmdiagnose command, which looks like it's made for gathering TM issues for a support case with Apple. But perhaps someone here might get some use out of it. Do a man tmdiagnose for more details.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
