Resume time machine over AFP

Question

Level 4

1,282 points

Resume time machine over AFP

I have a Time Machine drive that I attached to a Raspberry Pi and set up to use AFP (http://willitscript.com/post/39019058361/raspberry-pi-hfs-and-time-machine)

I have a months' worth of old backups on the drive. I made sure to mount the drive under the same name as the old one.

Time Machine sees the drive fine, but doesn't seem to recognize the backups (Oldest backup: None, Latest backup: None). Is there any way to get it to continue from the old backups?

MacBook Pro with Retina display, OS X Mountain Lion (10.8.4), 2.33/8/256

Posted on Aug 5, 2013 7:30 AM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Aug 5, 2013 10:04 AM in response to musicwind95

If you want network backup with Time Machine, use as the destination either an Apple Time Capsule or an external hard drive connected to another Mac or a mini-tower (802.11ac) AirPort base station. Only the 802.11ac base station supports Time Machine, not any previous model.

Reply

Answer 2

Eric Root

Level 10

685,215 points

Aug 5, 2013 1:17 PM in response to musicwind95

Inherit a Backup

Inherit a Backup (2)

Reply

Answer 3

musicwind95 Author

Level 4

1,282 points

Aug 5, 2013 5:08 PM in response to Eric Root

Thanks. Unfortunately, I'm getting the same errors as seen here:

https://discussions.apple.com/thread/4210419?start=0&tstart=0

sudo tmutil inheritbackup "/Volumes/Time Machine Backups/Backups.backupdb/MacBook Pro"

Unexpectedly found no machine directories for "/Volumes/Time Machine Backups" during collision check.

sudo tmutil associatedisk -a / /Volumes/Time\ Machine\ Backups/Backups.backupdb/MacBook\ Pro/2013-07-27-193353/Macintosh\ HD

/Volumes/Time Machine Backups/Backups.backupdb/MacBook Pro/2013-07-27-193353/Macintosh HD: Not a snapshot volume.

Any ideas? Looks like for inheritbackup it's only checking the volume, even though I'm dragging in the machine path…

Reply

Answer 4

Pondini

Level 8

38,863 points

Aug 5, 2013 5:47 PM in response to musicwind95

musicwind95 wrote:

. . .

Time Machine sees the drive fine, but doesn't seem to recognize the backups (Oldest backup: None, Latest backup: None).

That (alone) doesn't mean TM doesn't recognize the backups -- TM just doesn't bother to display the dates in some circumstances. See #B3 in Time Machine - Troubleshooting.

I have a months' worth of old backups on the drive. I made sure to mount the drive under the same name as the old one.

Are these backups for the same Mac and OSX volume? If so, there's no need to inherit either the backup set or the disk. Those are needed only when you get a new Mac or logic board; or replace or erase a volume; and don't put your data on the new Mac or drive with a full restore or Setup/Migration Assistant. See #B6 in Time Machine - Troubleshooting for details (same as the second link provided by Eric).

I take it you're talking about an external HD that was connected to something while you did some backups to it, and you've now connected it to the Raspberry? If so, what was it connected to before?

As Linc says, the Raspberry is not supported with Time Machine. Hacking to make that sort of thing work is sometimes partially successful, but usually unreliable, and certainly not recommended.

Reply

Answer 5

musicwind95 Author

Level 4

1,282 points

Aug 6, 2013 8:38 AM in response to Pondini

Backups are for the same system and volume, yes.

The USB TM drive used to be connected to my mac; I'd like to attach it to a network so I have more freedom with my rMBP.

Connecting to the drive by local IP address (rather than the server share's name), TM begins trying to make a backup, creates an 800MB sparsebundle representing my current system, but then stops because it's out of space (currently have a bit less than 100GBs of data on my system (200GB partition size); TM drive is 1.3TB with 75GBs free. Logs from Time Machine buddy:

Starting automatic backup

Attempting to mount network destination URL: afp://pi@192.168.0.183/Time%20Machine%20Backups

Mounted network destination at mount point: /Volumes/Time Machine Backups-1 using URL: afp://pi@192.168.0.183/Time%20Machine%20Backups

Disk image /Volumes/Time Machine Backups-1/MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1

Backing up to /dev/disk2s2: /Volumes/Time Machine Backups 1/Backups.backupdb

Forcing deep traversal on source: "Macintosh HD" (device: /dev/disk0s2 mount: '/' fsUUID: XXXXXXXX-5E50-3D17-B858-XXXXXXXXXXXX eventDBUUID: XXXXXXXX-72A0-4E27-8F17-XXXXXXXXXXXX)

Total content size: 95.24 GB excluded items size: 14.16 GB for volume Macintosh HD

Found 1377772 files (81.08 GB) needing backup

97.3 GB required (including padding), 75.7 GB available

Ejected Time Machine disk image: /Volumes/Time Machine Backups-1/MacBook Pro.sparsebundle

Compacting backup disk image to recover free space

Failed to compact disk image, DIHLDiskImageCompact returned: 78

Not starting automatic Time Machine backup: Computer is on battery power.

Compacting backup disk image to recover free space

Failed to compact disk image, DIHLDiskImageCompact returned: 78

Not starting automatic Time Machine backup: Computer is on battery power.

Compacting backup disk image to recover free space

At that point, I get a notification that it fails. Clicking on Details opens up the Pref. pane and says there's not enough space. Looks like it's attempting to backup, but not picking up from the old backups.

Reply

Answer 6

Pondini

Level 8

38,863 points

Aug 6, 2013 9:29 AM in response to musicwind95

musicwind95 wrote:

. . .

The USB TM drive used to be connected to my mac; I'd like to attach it to a network so I have more freedom with my rMBP.

That's not going to work. Backups are stored differently when done over a network. See the blue box in #E2 of Time Machine - Troubleshooting for an explanation.

TM has created a new sparse bundle disk image, and is trying to start an entirely new backup set there, but there isn't enough free space on the disk.

Your best bet is to delete that sparse bundle, put that drive "on the shelf," and start fresh with a different one. You can always access the old ones via the Browse Other Backup Disks option, per the green box in the above link.

EDIT: That's assuming, of course, that TM will work reliably to that unsupported device, which is doubtful.

For best results, use a supported destination (see Time Machine - Frequently Asked Question #2). At the very least, start making "secondary" backups, per #27 in the same link.

Message was edited by: Pondini

Reply

Answer 7

musicwind95 Author

Level 4

1,282 points

Aug 9, 2013 1:05 PM in response to Pondini

Fiddled around with my setup, but now it's working perfectly over the network. Indeed, it's not picking up from the old ones, just starting new backups. Thanks for the help!

Reply

Answer 8

Pondini

Level 8

38,863 points

Aug 9, 2013 1:54 PM in response to musicwind95

😎

Reply