So the Mac OS X 10.5.3 update broke Time Machine for me.
The update did fix Time Machine backups over the network for many people, but not for me. Lots of folks have tried various things to fix the problem (like standing on their head, reformatting, fingering prayer beads). Here’s what fixed Time Machine over AFPfor me.
I had a setup that was backing up perfectly on 10.5.2.
- MacBook connected to wifi network
- Mac Mini with external drive
- A shared folder on the Mini’s external drive (called “backups”) that was the Time Machine backup target. This folder contains the sparse bundle holds all the MacBook’s backups
- Access to the Mini’s “backups” share was through a .Mac login
- Here’s how I knew that: Browsing to Mini in Finder shows “Connected as: blahblah@mac.com” in the gray bar
- And the local usernames on the two machines were different (the same .Mac login accessed harold on the MacBook and freddy on the Mini)
After the 10.5.3 update, Time Machine said “The backup volume could not be mounted” — again and again. Console’s system log showed backupd errors 18 and sometimes 19.
Worse, I couldn’t choose “backups” as the destination for Time Machine. As it turns out, there are two problems with this setup that Leopard 10.5.3 doesn’t like — even though 10.5 through 10.5.2 were fine with it.
- 10.5.3 Time Machine now apparently can’t use a share accessed by a .mac login
- At least when they point to different local usernames. Let us know in the comments if it works for you with .mac at all
- Permissions on previous sparse bundle backups now seem to confuse Time Machine
- Again, this is likely due to the .mac credentials
I was able to fix the first of these problems and work around the second both problems, which got Time Machine backing up over the network.
I am so far unable to access previous Time Machine backups, though, so I’m still experimenting with the second.
Fixing Problem Number 1 – Connect as you you, not .mac you
- On MacBook, start System Preferences, and choose Time Machine
- “Change disk”, and select “None”
- This turns Time Machine backups off for now.
- Some folks say you need to reboot now
- On MacBook unmount any of Mini’s shares
- Over on Mini, share your backup share with both your user and Administrators; both need Read & Write access
- Back on MacBook, connect to “backups” on Mini as your username
- The .Mac user is the default, so you’ll probably need to disconnect, then connect as yourself
- On MacBook, start System Preferences, and choose Time Machine
- “Change disk”, and select “Backups (mini)”
- “Backups” should be in the list now. If not, reboot and start from step 4.
- Enter your username and password. With this, Time Machine will be able to mount your share automatically when it’s ready to back up
- Try to “Back up now” in Time Machine
If it works, congratulations, you’re done. For me, it didn’t — probably because the previous .mac login connected as different users on Mini and MacBook. Since you’re not likely to have such a bizzarro-world setup, you’re probably home free. Let us know in the comments.
Fixing Problem Number 2 – sparsebundle permissions
Because of my .mac username hijinks (the same .Mac login accessed harold on the MacBook and freddy on the Mini), I still couldn’t back up.
Console told me I was now getting backupd error 18 in system.log:
/System/Library/CoreServices/backupd: Volume at path /Volumes/Backups-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
/System/Library/CoreServices/backupd: Backup failed with error: 18
In theory, changing permissions on the sparsebundle to MacBook’s user ought to work. Only it didn’t for me.
Instead, I moved the sparsebundle on Mini to another folder. From there, MacBook’s Time Machine backed up just fine, though any backups made under 10.5.2 or earlier are lost.
Update 1 Jun: It does work, but I had to change two things to get access to the old backups.
- Give the local user read and write permissions on the sparsebundle. Use Finder on the Mini to do this, as ACLs are involved. It will take a long time.
- From Terminal on Mini, change ownership of the sparsebundle to the local user (use your username in place of “eric” and your sparsebundle name in place of “greatnorthern…”):
sudo chown -R eric greatnorthern_0017f2f16a4e.sparsebundle
After this, backups over wifi worked — though the first backup took a very very long time preparing.
The good news? 10.5.3 is much smarter about network backups. Time Machine will mount the share automatically when it’s time to back up — or when you enter Time Machine. For a laptop, Time Machine backups are now truly seamless.
If only the upgrade was painless!
6 Comments on the Original Post
I get the msg “operation not supported” when I try to change owner.
The problem as I see it is that Finder and via Time Machine mount the backup disk in different ways. If I open it in finder, it lists the permissions as belonging to the user. When Time Machine mounts the disk, it is listed as belonging to Root.
This explains the console messages I’m getting about backup daemon not having permissions:
5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd148 Backup requested by user 5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd148 Starting standard backup 5/29/08 5/29 | 11:32:10 PM /System/Library/CoreServices/backupd148 Network mountpoint /Volumes/sean not owned by backupd… remounting 5/29/08 5/29 | 11:32:12 PM /System/Library/CoreServices/backupd148 Failed to remount network volume. 5/29/08 5/29 | 11:32:17 PM /System/Library/CoreServices/backupd148 Backup failed with error: 19
..I wonder if I should connect to my Airport Disk as a user rather than with a disk password. But when I consider changing, Airport Utility gives me the warning that I won’t be able to see the data on the drive.
Thank you for the support on this site, nearly there I feel, but not quite.
S
one more thing: if I open the airport disk AND time machine opens the disk, I get TWO disks attached: backup AND backup-1
S
Hi Sean —
Two things may be worth trying —
1. What happens if you give “Administrators” read & write access to the share and the sparsebundle?
2. Alternately, it may be worthwhile connecting to the airport disk as a user — but my guess is you’d have to change the share to give read & write access to that user. And you’d probably have to make the sparsebundle owned by that user, too.
This is what I did to get backups to my desktop Mini working.
But I don’t have an airport myself, so I can’t help you experiment there.
Does the airport’s warning message give you any hints?
Eric,
from what I’ve read on the mac forum
http://discussions.apple.com/thread.jspa?messageID=7291724
… it’s not as simple as changing the permissions on the sparsebundle.
I think the only way to be the same owner as the share is to log on as a user: I didn’t want to have my airport disk set up this way, and also there’s a scary message when I consider changing, that I won’t be able to read data already on the drive.
I think the problem occurs because TM accesses the disk in a new way. If the volume “Backup” is already mounted, it mounts “Backup-1” but then fails to be able to read and write to it. And if, say, iTunes tries to do the same, it hasn’t got write privileges either. The only workaround I have at the moment is to keep mounting and unmounting the disk manually!
Many thanks for the reply Eric. Hoping you/Apple come up with a solution!
Sean
Tried the fix posted here – still not working properly.
I’ve just downloaded airport utiliity 5.3.2 – still not fixed.
How to reproduce:
restart mac: click on time machine, ‘back up now’. Time machine will fail (can’t mount disk). If I open the airdisk (connect to the folder, as guest, so it shows the ‘eject’ icon), it will also fail.
If I open then eject the airdisk, it works. But this is a bit of a ‘pullahvah’ as we say in the UK.
Sean
I’m trying this with an airport extreme, no TC and get
6/20/08 1:02:36 AM kernel AFP_VFS afpfs_mount: /Volumes/TMDrive, pid 8649 6/20/08 1:02:50 AM kernel AFP_VFS afpfs_unmount: /Volumes/TMDrive, flags 0, pid 8671 6/20/08 1:03:15 AM /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder151 SharePointBrowser::handleOpenCallBack returned 80 6/20/08 1:03:35 AM kernel AFP_VFS afpfs_mount: /Volumes/TMDrive, pid 8649 6/20/08 1:03:37 AM kernel AFP_VFS afpfs_unmount: /Volumes/TMDrive, flags 0, pid 8676 6/20/08 1:03:37 AM /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder151 SharePointBrowser::handleOpenCallBack returned -5002 6/20/08 1:03:53 AM kernel AFP_VFS afpfs_mount: /Volumes/TMDrive, pid 8649 6/20/08 1:04:00 AM /System/Library/PrivateFrameworks/Admin.framework/Resources/writeconfig8653 Warning: accessing obsolete X509Anchors. 6/20/08 1:04:19 AM /System/Library/CoreServices/backupd8684 Backup requested by user 6/20/08 1:04:19 AM /System/Library/CoreServices/backupd8684 Starting standard backup 6/20/08 1:04:19 AM /System/Library/CoreServices/backupd8684 Network mountpoint /Volumes/TMDrive not owned by backupd… remounting 6/20/08 1:04:20 AM /System/Library/CoreServices/NetAuthAgent.app/Contents/Resources/NetAuthSysAgent8685 Warning: accessing obsolete X509Anchors. 6/20/08 1:04:20 AM /System/Library/CoreServices/backupd8684 Failed to remount network volume. 6/20/08 1:04:25 AM /System/Library/CoreServices/backupd8684 Backup failed with error: 19
This is perplexing. I’m starting with a newly formatted disk on the AE and it does this. Should I try doing a full backup to the local mount first to have a sparsebundle to begin with?
Comments (0)
Leave a comment...