Open terminal:
Code:defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
Sorry if this one has been covered.
I did this, relaunched time machine and BLAM. My AEBSn share was there.
I tried it and it still wouldn't see my readynas drives.
I ended up doing the workaround (I had an external drive available) and copied over the two files to my NAS. Time Machine immediately lit up the NAS drive. I have a backup going now (over wireless G)... This should take a while![]()
Nothings that simple, surely...? Not that I'm complaining however![]()
Which protocols did you turn on for the share? (i have two readynas's but haven't tried it yet)
You guys said backing up works, but does Time Machine itself work? (When you invoke Time Machine, can you actually use it to go back in time?) Because in my case, it backs up, but when I call up Time Machine, there's nothing before the present. In other words, the only way to retrieve old files is to go into the file structure and fetch them yourself. No fancy Time Machine interface.
See my thread (that no one replied to) here.
You guys said backing up works, but does Time Machine itself work? (When you invoke Time Machine, can you actually use it to go back in time?) Because in my case, it backs up, but when I call up Time Machine, there's nothing before the present. In other words, the only way to retrieve old files is to go into the file structure and fetch them yourself. No fancy Time Machine interface.
See my thread (that no one replied to) here.
Maybe you need to invoke the command in the OP in order for the Time Machine app to recognize it? I'm not sure if mine works, because it is still backing up.
Might have something to do with the copying large files issue that just popped up on page 1.
Dropping that network connection could be a bummer! LOL
Yeah, well, you can accidently unplug the USB cable too. **** happens.
But the thing is, I noticed that with the drive connected to the Mac directly, Time Machine saves the backups directly to the drive. But over the network, Time Machine saves to a .sparsebundle file. Maybe that's why?
When Time Machine did it's first BIG backup, it didn't eject the .sparsebundle image. Which could be dangerous. But when it did the second backup, it did eject the .sparsebundle image. Maybe that's the bug Apple is worried about?
It does that because most network file sharing protocols don't support some of the filesystem things that a normal hard drive would. So, it makes an image and formats that so that it can do such things correctly.
Plus, it doesn't steal the entire hard disk!
Also, I don't think the bug that is in the news will affect this, because that has to do with MOVING files across volumes, rather than copying. By default, Mac OS will COPY files if they are being placed on another volume.
Then I have absolutely no clue why Apple disabled this. It's been working great for me so far. Makes me wonder if Apple is planning to release a Apple TV - Mac mini - AirPort Express super-ultra-hybrid thingie and plans to tout Time Machine hosting as a feature.
For a feature like Time Machine, "worked for me" isn't good enough to allow shipping. "Works so well that nobody will lose their data, ever, and sue us" is much harder to achieve.
Well, well. Whaddaya know. My sparsebundle file somehow got corrupt and unusable.
Guess I'll do without Time Machine for now.