10.6: Destination /Volumes/DroboCapsule does not support TM Lock Stealing

[Cedric]

Hi,

I successfully upgraded to Snow Leopard last night. My first TM backup
took a long time - at least the first part of it - but I've seen a lot
of people reporting that even with TimeCapsule so I don't think it has
anything to do with Backmyfruitup.

Subsequent backups are running ok and are fast but I keep getting the
following warnings:

02/09/2009 09:12:53 com.apple.backupd[1101] Warning: Destination /
Volumes/DroboCapsule does not support TM Lock Stealing
02/09/2009 09:12:53 com.apple.backupd[1101] Warning: Destination /
Volumes/DroboCapsule does not support Server Reply Cache

Any idea? TM Lock Stealing is important and a good reason to use AFP/
Backmyfruitup instead of SMB mounts according to Jon's recent post. I
don't think I've seen these warnings before the 10.6 upgrade.

Full log below.
Thanks.

Cedric


02/09/2009 09:12:51 com.apple.backupd[1101] Starting standard backup
02/09/2009 09:12:51 com.apple.backupd[1101] Attempting to mount
network destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
02/09/2009 09:12:53 com.apple.backupd[1101] Mounted network
destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
02/09/2009 09:12:53 com.apple.backupd[1101] Warning: Destination /
Volumes/DroboCapsule does not support TM Lock Stealing
02/09/2009 09:12:53 com.apple.backupd[1101] Warning: Destination /
Volumes/DroboCapsule does not support Server Reply Cache
02/09/2009 09:13:02 com.apple.backupd[1101] Disk image /Volumes/
DroboCapsule/MacBook_001f5be7e5f4.sparsebundle mounted at: /Volumes/
Backup of MacBook
02/09/2009 09:13:03 com.apple.backupd[1101] Backing up to: /Volumes/
Backup of MacBook/Backups.backupdb
02/09/2009 09:13:23 com.apple.backupd[1101] No pre-backup thinning
needed: 171.5 MB requested (including padding), 286.65 GB available
02/09/2009 09:13:52 com.apple.backupd[1101] Copied 1343 files (9.7 MB)
from volume Macintosh HD.
02/09/2009 09:13:52 com.apple.backupd[1101] Starting post-backup
thinning
02/09/2009 09:13:52 com.apple.backupd[1101] No post-back up thinning
needed: no expired backups exist
02/09/2009 09:13:52 com.apple.backupd[1101] Backup completed
successfully.
02/09/2009 09:13:53 com.apple.backupd[1101] Ejected Time Machine disk
image.
02/09/2009 09:13:53 com.apple.backupd[1101] Ejected Time Machine
network volume.

[Jon Stevens]

My first backup took awhile because it was 10+gigs of data. Of course it is going to take a while, you just upgraded your system and a lot of files changed. =)

Yup, I'm following the netatalk development closely. Apple has *finally* documented [1] what it takes to make an AFP server support timemachine backups and those changes are being coded up in netatalk.

Those warnings are just that, warnings. They don't prevent your backup from succeeding. I'm not worried about it right now because as far as I can tell, the default behavior is that if those commands aren't sent, then to assume the data is invalid and start over again. These new features will be added to netatalk and when there is a new release, I'll upgrade backmyfruitup to use it.

[1] http://developer.apple.com/mac/library/documentation/NetworkingInternetWeb/Conceptual/TimeMachineNetworkInterfaceSpecification/TimeMachineRequirements/TimeMachineRequirements.html#//apple_ref/doc/uid/TP40008951-CH100-SW1

jon

My blog: http://lookfirst.com/