Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.6: Set up Time Machine on networked AFP volume' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Set up Time Machine on networked AFP volume
Authored by: ssevenup on Apr 03, '10 07:21:42PM
Running 10.6.3 and my TM Volume is a Buffalo NAS which "supports TM" but probably not 10.6.3 though I need to look into firmware patches. In any case my backups appear to be working despite my not doing this change. However I'm seeing the following in the logs which I'm assuming is BAD. But all in all TM actually seems to work better with my Buffalo since 10.6.3.

Apr 3 18:21:57 vos-mac com.apple.backupd[20052]: Warning: Destination /Volumes/Machine does not support Server Reply Cache
Apr 3 18:21:57 vos-mac com.apple.backupd[20052]: Warning: Destination /Volumes/Machine does not support TM Lock Stealing

---
Mark Moorcroft
ELORET Corp. - NASA/Ames RC
Sys. Admin.


[ Reply to This | # ]
10.6: Set up Time Machine on networked AFP volume
Authored by: ssevenup on Apr 04, '10 01:33:29PM

I have since found that the latest versions of HFS+ support these added features. And they are just now being developed for netatalk (found in many NAS products). In the mean time I don't know the implication of NOT having these features but TM backups appear to continue to work. One might assume locking has to do with the ability to do multiple TM backups to a single destination. Possibly at the same time?

---
Mark Moorcroft
ELORET Corp. - NASA/Ames RC
Sys. Admin.



[ Reply to This | # ]
10.6: Set up Time Machine on networked AFP volume
Authored by: ssevenup on Apr 04, '10 01:45:46PM

And BTW my 10.6.3 TM backups to my Buffalo Linkstation Live were working fine without the plist but I have added it to the sparsebundle now anyway. It was critical in my case to have the MAC address of en0 part of the sparsebundle name. At least that was the case with 10.5.8. Perhaps because I had that naming right is why 10.6 kept on working. The name convention is actually:

computername_000000000000.sparsebundle

You will note no colons in the MAC address.

---
Mark Moorcroft
ELORET Corp. - NASA/Ames RC
Sys. Admin.


[ Reply to This | # ]