Start time machine over?

I just upgraded my 2006 imac running leopard to a mbp 13" running mountain lion. I migrated everything to the mbp from my time machine backup and everything transferred ok. There are now 2 problems. First one is when i plugged in the external hard drive to start backing up again, time machine said it was cleaning up old backup files, and now it shows the oldest backup as 2 april 2013. (its not the end of the world because i am happy that i have everything on my new mbp)
Secondly, it now says the backup is too large. Backup requires 82gb but only 72gb is available. Are my options here either buy a new drive, or start fresh with current one by erasing and starting again?

How large is your TM backup drive?

Similar Messages

Just baked up my macbook pro to an external hard drive. my computer died on me and i plugged it in and rebooted it ,started time machine and finished backing up but. just wondering if thats good or should i delete and restart

just baked up my macbook pro to an external hard drive. my computer died on me and i plugged it in and rebooted it ,started time machine and finished backing up but. just wondering if thats good or should i delete and restart

I wouldn't trust that backup.
Make sure the system is connected to AC and Do Over.

Why full, rather than incremental, when re-starting TIme Machine

I had to stop Time Machine a couple of weeks ago, and remove the dedicated external drive. Yesterday, on reconnecting the drive and re-starting Time Machine it appeared to try to make a full backup (which I had to abort after two and a half hours) rather than the incremental I assumed it would make. Does this mean that each time one turns Time Machine off, it will make a full back up the next time it is restarted and an external drive connected? This seems to make irrelevant the backups already on the drive.

V.K. wrote:
I'm not completely sure but I think if you don't do a TM backup for ten days TM gives you a warning that you haven't backed up in 10 days and if you ignore it, it erases TM history. this makes it start a new series of backups once you reconnect.
I use my G5 rarely, sometimes not for weeks and I have never had a TM warning about a "stale" backup. When I turn it on, it simply schedules the next backup, which is incremental, as always, and proceeds about an hour later.
I have never seen that "Ten Day" warning.
I think I have also let my other MBP sit unused for over 10 days and have never seen the warning.
However, I always start up these machines with the TM drive connected. Running them with the drive disconnected may be a completely different situation. In oher words, when I start these two rarely used computers, there is really nothing new to backup. That may be the difference. If you use the computer for 10 days or more with the TM drive disconnected that may cause the warning flag to be raised.
Message was edited by: nerowolfe

Lion unresponsive after starting Time Machine

I accidentally deleted a file so I started Time Machine to restore it. The machine seems to be hung. There is no title bar and no dock. I can see the application windows and I can move the mouse pointer but I can't click on it. The machine has been in this state for over 90 minutes. The screen saver didn't start but I can see dialogs that have popped up. Unfortunately, I can't click on any of these dialogs.
How do I get out of this? Do I have to pull the plug? How do I prevent this from happening in the future?

I tapped the power button in anticipation of powering down the whole machine. This closed Time Machine without powering the machine down. I closed a bunch of applications and restarted Time Machine. I restored the file successfully. I wish I did this two hours ago.

Everytime I start time machine, my computer backs up +/- 250MB, then freezes. Tried it with 3 different external drives, all stop at about the same point (they all work fine on other macs). Any suggestions?

The drives I have are Seagate 1TB GoFlex portable drives (one has UBS 3.0, the other USB 2.0), and a WesternDigital 1TB passport (USB 3.0). I originally tried to backup with Time Machine using the Seagate USB 3.0, and when that didnt work, Seagate suggested maybe since my operating system is a little older, that I try with a USB 2.0, so they sent me another NEW external hard drive, with the USB 2.0. Had the same issue. Frustrated and convinced that Seagate just sucked, I went and bought the 1TB WesternDigital passport (USB 3.0). Have the exact same issue again. Every drive was new, and formatted for mac. When I started time machine it started to back up my files, but froze after copying give or take 250 MB (usually 252.5MB, to be exact). I went and tried the drive on several other macs, and none of them presented any problems. I also tried dragging individual files, but it still freezes on pretty much anything bigger than +/- 100MB. Disk Utility says that all the drives are fine. Obviously this is a problem with my computer, and not the 3 brand new external drives. I thought about upgrading to OSX 10.6, but don't know if this'll help or not (plus, I'd really prefer to have all the files backed up on a drive before doing that, just in case). I dont know what else to do.. called apple, but I'm not about to pay them $50 to have them MAYBE give me a solution (done that twice now for previous unrelated issues, and each time they just told me to take it to a computer repair place.) Just seeing if anyone out there has a solution before I cave and take it back to the certified computer guys for them to figure it out.. Also, I live in Montana and theres no apple store anywhere close (not suprising), so taking it to an Apple Store is just not an option.
Side note: Seagate tech support is awesome; they tried everything to solve the problem, and they even bent their rules a little to send me a new drive, even though it wasn't a malfunction issue with their drive. Really helpful, friendly people, which is much more than I can say for Apple at this point...

this is what you need to do to exclude everything apart from desktop.
on time machine preferences, click on Options
click plus sign, on the new window, click macintosh HD
do a Control + A then deselect users then click okay
go to options again, plus sign, go to users, control +A then deselect your user account
go to options again, plus sign, go to your user account, control + A, deselect desktop
start the back up.

Time Machine over AirPort to Time Capsule... maybe a solution

Like a lot of people on this forum, apparently, I have been suffering from the inability to make reliable Time Machine backups to a Time Capsule over AirPort. Here's what I did to solve the situation.
Here's my network setup:
I have an ADSL wireless box with b/g network connected over ethernet to a 1-TB Time Capsule which has a 5 GHz 'n' network. Using 5 GHz 'n' network where I am means no interference. All equipment that is not capable of 'n' is on the wireless box, 'n' equipment (basically, only my MacBook Pro) gets on the Time Capsule. It doesn't make internet faster, but sure makes the Time Capsule accessible. Both networks are hidden and secured with WEP (b/g) or WPA2 (n).
(the Time Capsule is double-NATted, unfortunately, to cut down on network chatter in the system log)
After upgrading to 10.5.6, I think I haven't been able to make a reliable Time Machine backup over AirPort. It may have been well before that (possibly with the AirPort Extreme update) but I don't remember. Most of the time, before the wireless box arrived, I have been making far-too-irregular backups over ethernet to the Time Capsule.
Anyway, I had been trying to get Time Machine to work over AirPort to the backup on the Time Capsule. I had made the original backup over ethernet (all 500 GB worth over a weekend). For the incremental backups, though, I would prefer AirPort because keeping a cable attached really is a pain. Of course, it didn't work right away.
What I couldn't figure out was why. Time Machine mounted the sparsebundle volume on the Time Capsule, but after that it seemed to do nothing with it. I left it for half a day and found little by way of relevant network activity. I tried the following to no avail:
* disabled Little Snitch (outgoing firewall) and the OS X firewall (incoming firewall)
* disabled security on the network
* disabled and re-enable Time Machine
* changed the name of the sparsebundle volume (that was dumb!)
* trash Time Machine preferences and re-select the backup disk
* reboot, reboot, reboot
Whatever I did, it sucked. Connecting over ethernet was excellent, and incremental backups went really quick, but AirPort just didn't fly. It would have been worse if it were slow; chances are then it'd be a hardware problem. But nothing was going over AirPort with Time Machine.
In amongst the surfing, I found somewhere how to downgrade the firmware on the Time Capsule. Worth a try since nothing was working. I opened up the AirPort Utility and checked, but it would only give me 7.3.2 (AirPort Utility 5.3.2). I searched and found the AirPort 5.3.1 software, and using Pacifist extracted the AirPort Utility application. That would let me 'downgrade' the Time Capsule firmware to 7.3.1 (and 7.3). It downloaded the 7.3.1 for me and put it on the Time Capsule without problems.
I then made a test run with Time Machine over ethernet, that was fine. The I tried over AirPort - and hey presto! it worked! I re-enabled my network setup (firewalls, security) and it's still working fine.
So, if your Time Capsule is on 7.3.2 firmware and Time Machine over AirPort *****, try downgrading to 7.3.1. The AirPort 5.3.1 software, which can download and install the 7.3.1 software (5.3.2 doesn't) can be found here:
http://support.apple.com/downloads/TimeCapsule_and_AirPort_Base_Station__802_11n__Firmware_7_31
Note: you need Pacifist to extract the AirPort Utility application;
do not install the software over your existing AirPort software

This may be tough because TM isn't supported over wi-fi unless you're using a Time Capsule. There are a couple of resources available to you and I'd also recommend posting in the Snow Leopard forum because TM is part of OS X the OS X forum would be the right venue. The first thing is I'm guessing you are using a router, if so make sure the firmware on it is up-to-date. You will need to refer to the router's manual. You also should do the same with the modem too. Some written resources are:
Time Machine FAQs
Time Machine Troubleshooting
Pondini Time Machine Tips
That's about all I can help you out with.
Good luck!

Time machine over a network volume

So since Snow Leopard (and I think Leopard), when you use Time machine to back up over a network share (for example, a USB drive attached to a mini server), the OSX creates a sparsebundle image where all time machine files are stored.
In Lion, If I encrypt my hard drive, and I keep on backing up using time machine over this network share.. will the sparsebundle image be encrypted or not?

I don't see much difference between using a sparsebundle image or an encrypted sparsebundle image.
I've sent this feedback to Apple see if they enable this in subsequent updates.

Time Machine over the Network: Terribly Slow

Hello,
I've been using Time Machine for over 3 years now with no issues over the network; the destination being a 2TB external Seagate connected to another iMac connected through gigabit ethernet. Everything has been working flawlessly: Every hour Time Machine would MOUNT the sparseimage it created on the disk, BACKUP the data and UNMOUNT the disk image when finished.
Until I upgraded to Lion. The above process is still working per se, however it is PAINFULLY slow! A 50MB backup can take up to AN HOUR! Searching around on the net, advised that there could be an issue with Spotlight as well, however this is not the case for me, since Spotlight finished a new index in under 30 mins. Followed every tutorial I could find on the issue, to no avail..
I then upgraded to Mountain Lion with the hope that the issue will clear itself. Cleared my old backups, resetted Time Machine by erasing its .plist file, restarted my iMac just to make sure and connected Time Machine to the network share anew, creating a "sharing only" account on the host iMac, i.e. the one that has the external HD connected through USB. Still no luck.
I painfully realize that I still have the same issue. While backing up, network traffic is under 100KB, and activity monitor does not show any backupd or mds or any similar processes taking anything over 3% of CPU time.
What could be wrong?

Hello again,
Tries on the other iMac (also running 10.8.2) and things are exactly the same: Image creation takes almost half an hour, and copying crawls at under 1MB/min. While time machine image is mounted and Time Machine is "backing up", accessing ANY disk on the host Mac is VERY slow. Seems like something hogs up appleshare when Time Machine is in use. Mind you, there is insignificant network traffic as seen by Activity Monitor, as well as insignificant CPU usage while backing up.
Stopping backup and using tmutil to set the Time Machine destination to the mounted image as mounted by Finder, solves the issue again, revving up Time Machine throughput to over 20MB/sec! There is also no issues acessing the other Mac as well, under this scenario.
Up to this point, the only way I have managed to use Time Machine over a networked external HD is through the NAS server. Both configurations where I am using a Mac running 10.8.2 as a server of the external disk have failed with very low throughput while backing up. Something must be wrong in 10.8.2's afp when Time Machine is mounting the image by itself.
I may need to remind you that I have been successfully backing up to the external HD for 4 years now; something broke a few months after the client iMac was upgraded to Lion and at the time when the host iMac was upgraded to Mountain Lion. Will try to locate a Mac running some later OS X version to do some more testing.
Also reminding that I have used two distinctive iMacs and two external HD drives for my tests so far. The client iMac has remained the same, however 10.8.2 has been reinstalled on it a couple of times. Have also used an afp-enabled NAS server which worked fine with Time Machine.

Getting (error code -6584) when starting time machine

Hello, I have an early 2011 mbp running Lion. I tried this morning to start time machine and got the error described above. I have access to my time capsule but the program will not start. This is the first time I start time machine since installing lion.
What could be wrong?
thanks in advance

To fix the error code -6584 you would need to verify and repair your Time Machine Backup.
Go to System Preferences > Time Machine.
Hold down the Option key on your keyboard and click the Time Machine menulet and then selecting "Verify Backups".

"Do you still want to start Time Machine?"

I'm using Time Machine with Time Capsule connected to another wireless router via Ethernet, and my Mac is wirelessly hook up with the router.
My problem is that when I click on the Time Machine icon on Dock, "Do you still want to start Time Machine--Backup volume is now available" message appears after a couple of minutes! If I choose "Continue," I can enter Time Machine, no problem. But waiting for a few minutes for the message to pop up is kinda annoying for me. Once I click "Continue" button on the message, Time Machine launches almost simultaneously thereafter only for a while, though.
Does anyone know what is causing this problem and how to solve it?

For those who can kindly look at the messages on my Console log for this issue, I posted the Time Machine-related and Time Capsule-related messages below. Thanks in advance.
*Time Machine-related messages:*
6/28/08 8:59:17 AM /System/Library/CoreServices/backupd[2819] Ejected Time Machine disk image.
6/28/08 8:59:21 AM /System/Library/CoreServices/backupd[2819] Ejected Time Machine network volume.
6/28/08 10:17:27 AM /System/Library/CoreServices/backupd[3029] Ejected Time Machine disk image.
6/28/08 10:17:32 AM /System/Library/CoreServices/backupd[3029] Ejected Time Machine network volume.
6/28/08 11:18:20 AM /System/Library/CoreServices/backupd[3148] Ejected Time Machine disk image.
6/28/08 11:18:25 AM /System/Library/CoreServices/backupd[3148] Ejected Time Machine network volume.
6/28/08 11:41:25 AM /System/Library/CoreServices/backupd[3234] Ejected Time Machine disk image.
6/28/08 11:41:31 AM /System/Library/CoreServices/backupd[3234] Ejected Time Machine network volume.
6/28/08 12:20:40 PM /System/Library/CoreServices/backupd[3366] Ejected Time Machine disk image.
6/28/08 12:20:45 PM /System/Library/CoreServices/backupd[3366] Ejected Time Machine network volume.
6/28/08 1:56:36 PM /System/Library/CoreServices/backupd[3518] Ejected Time Machine disk image.
6/28/08 1:56:40 PM /System/Library/CoreServices/backupd[3518] Ejected Time Machine network volume.
6/28/08 3:36:51 PM /System/Library/CoreServices/backupd[3606] Ejected Time Machine disk image.
6/28/08 3:36:58 PM /System/Library/CoreServices/backupd[3606] Ejected Time Machine network volume.
6/28/08 4:13:30 PM /System/Library/CoreServices/backupd[3707] Ejected Time Machine disk image.
6/28/08 4:13:37 PM /System/Library/CoreServices/backupd[3707] Ejected Time Machine network volume.
6/28/08 5:27:13 PM /System/Library/CoreServices/backupd[3867] Ejected Time Machine disk image.
6/28/08 5:27:19 PM /System/Library/CoreServices/backupd[3867] Ejected Time Machine network volume.
6/28/08 9:33:57 PM /System/Library/CoreServices/backupd[4138] Ejected Time Machine disk image.
6/28/08 9:34:03 PM /System/Library/CoreServices/backupd[4138] Ejected Time Machine network volume.
*Time Capsule-related messages:*
6/28/08 8:56:52 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule, pid 2730
6/28/08 8:56:53 AM /System/Library/CoreServices/backupd[2819] Network volume mounted at: /Volumes/Time Capsule
6/28/08 8:56:56 AM /System/Library/CoreServices/backupd[2819] Disk image /Volumes/Time Capsule/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 8:59:21 AM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule, flags 0, pid 2835
6/28/08 9:05:34 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule, pid 2888
6/28/08 9:05:34 AM /System/Library/CoreServices/backupd[2887] Network volume mounted at: /Volumes/Time Capsule
6/28/08 9:05:38 AM /System/Library/CoreServices/backupd[2887] Disk image /Volumes/Time Capsule/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 9:47:12 AM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 9:47:12 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 9:47:12 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 9:47:13 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 9:47:13 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 9:47:15 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 9:47:15 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 9:47:18 AM kernel AFP_VFS afpfs_Reconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Time Capsule
6/28/08 9:47:19 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 9:47:19 AM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 9:47:19 AM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 10:14:49 AM /System/Library/CoreServices/backupd[3029] Network volume mounted at: /Volumes/Time Capsule
6/28/08 10:14:50 AM /System/Library/CoreServices/backupd[3029] Disk image /Volumes/Time Capsule/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 10:17:32 AM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule, flags 0, pid 3048
6/28/08 11:16:21 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule, pid 3143
6/28/08 11:16:21 AM /System/Library/CoreServices/backupd[3148] Network volume mounted at: /Volumes/Time Capsule
6/28/08 11:16:23 AM /System/Library/CoreServices/backupd[3148] Disk image /Volumes/Time Capsule/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 11:18:25 AM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule, flags 0, pid 3182
6/28/08 11:35:29 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule, pid 3207
6/28/08 11:38:12 AM /System/Library/CoreServices/backupd[3234] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 11:39:29 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3235
6/28/08 11:39:29 AM /System/Library/CoreServices/backupd[3234] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 11:39:45 AM /System/Library/CoreServices/backupd[3234] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 11:41:30 AM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3264
6/28/08 11:51:07 AM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 11:51:07 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 11:51:07 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 11:51:08 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 11:51:08 AM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 11:51:08 AM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 11:51:22 AM /System/Library/CoreServices/backupd[3299] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 11:52:37 AM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3300
6/28/08 11:52:37 AM /System/Library/CoreServices/backupd[3299] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 11:52:53 AM /System/Library/CoreServices/backupd[3299] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule-1
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule-1 failed 65.
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule-1
6/28/08 12:19:01 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule-1
6/28/08 12:19:22 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 12:19:22 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 12:19:22 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 12:19:22 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 12:19:22 PM /System/Library/CoreServices/backupd[3366] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 12:19:22 PM kernel AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Time Capsule
6/28/08 12:19:23 PM /System/Library/CoreServices/backupd[3366] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 12:20:45 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3379
6/28/08 1:52:30 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 1:52:30 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 1:52:30 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 49.
6/28/08 1:52:30 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 1:52:30 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 1:52:32 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 1:52:33 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 1:52:33 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 1:52:33 PM /System/Library/CoreServices/backupd[3518] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 1:53:49 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3519
6/28/08 1:53:49 PM /System/Library/CoreServices/backupd[3518] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 1:54:08 PM /System/Library/CoreServices/backupd[3518] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 1:56:40 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3553
6/28/08 3:33:27 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 3:33:27 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 3:33:27 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 3:33:28 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 3:33:28 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 3:33:30 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 3:33:31 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 3:33:31 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 3:33:31 PM /System/Library/CoreServices/backupd[3606] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 3:34:46 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3607
6/28/08 3:34:46 PM /System/Library/CoreServices/backupd[3606] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 3:35:04 PM /System/Library/CoreServices/backupd[3606] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 3:36:58 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3640
6/28/08 4:10:04 PM /System/Library/CoreServices/backupd[3707] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 4:11:19 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3708
6/28/08 4:11:20 PM /System/Library/CoreServices/backupd[3707] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 4:11:38 PM /System/Library/CoreServices/backupd[3707] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 4:13:36 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3733
6/28/08 5:23:56 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 5:23:56 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 5:23:56 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 5:23:56 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 5:23:56 PM /System/Library/CoreServices/backupd[3867] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 5:25:11 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3868
6/28/08 5:25:11 PM /System/Library/CoreServices/backupd[3867] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 5:25:27 PM /System/Library/CoreServices/backupd[3867] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 5:27:15 PM /System/Library/CoreServices/backupd[3867] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 5:27:19 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3893
6/28/08 5:28:30 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3892
6/28/08 5:28:30 PM /System/Library/CoreServices/backupd[3867] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 5:28:32 PM /System/Library/CoreServices/backupd[3867] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 8:37:04 PM /System/Library/CoreServices/backupd[3923] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule-1
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule-1
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule-1
6/28/08 8:37:04 PM kernel AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Time Capsule-1
6/28/08 8:37:07 PM /System/Library/CoreServices/backupd[3923] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 8:37:28 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 3951
6/28/08 8:37:43 PM /System/Library/CoreServices/backupd[3959] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 8:38:58 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 3960
6/28/08 8:38:58 PM /System/Library/CoreServices/backupd[3959] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 8:39:02 PM /System/Library/CoreServices/backupd[3959] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 9:30:12 PM /System/Library/CoreServices/backupd[4138] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 9:30:13 PM /System/Library/CoreServices/backupd[4138] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 9:34:03 PM kernel AFP_VFS afpfs_unmount: /Volumes/Time Capsule-1, flags 0, pid 4158
6/28/08 9:44:12 PM /System/Library/CoreServices/backupd[4190] Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
6/28/08 9:45:28 PM kernel AFP_VFS afpfs_mount: /Volumes/Time Capsule-1, pid 4191
6/28/08 9:45:28 PM /System/Library/CoreServices/backupd[4190] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 9:45:45 PM /System/Library/CoreServices/backupd[4190] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule-1
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule-1 failed 65.
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Time Capsule
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule failed 65.
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 10:07:39 PM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Time Capsule-1 failed 65.
6/28/08 10:07:40 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule
6/28/08 10:07:40 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule
6/28/08 10:07:40 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule
6/28/08 10:07:42 PM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Time Capsule-1
6/28/08 10:07:43 PM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Time Capsule-1
6/28/08 10:07:43 PM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Time Capsule-1
6/28/08 10:07:43 PM kernel AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Time Capsule-1
6/28/08 10:15:18 PM /System/Library/CoreServices/backupd[4282] Network volume mounted at: /Volumes/Time Capsule-1
6/28/08 10:15:22 PM /System/Library/CoreServices/backupd[4282] Disk image /Volumes/Time Capsule-1/My Name’s Computer_0016cb8a3d59.sparsebundle mounted at: /Volumes/Backup of My Name’s Computer

Operating Time Machine over a remote Back to My Mac connection is a challenge -- can I do restores in Terminal?

When operating Time Machine remotely via Back to My Mac (and by remotely, I mean from Illinois to Ohio ), seeing your remote mouse cursor is largely a no-go, even in Lion. It simply does not get displayed, with very minor, flickering exceptions. Certainly it becomes impossible to operate the Time Machine's Finder window in any mouse-clicking way. I can barely operate the CANCEL or RESTORE buttons, and that's if I help myself by mousing over from outside the Screen Sharing Window, and kind of estimating if I am over the button area. Similarly, I can get the mouse to give me some approximate date in the backups progression. But the way to select a file, I found, is through arrow-keys. I can get to the right directory before starting the Time Machine, and I can navigate to the correct file with much delay using the arrow-keys. In short, it's a major freaking pain, because of all the lag and invisible mouse.
But I was able to do what I needed, given enough pain and perseverance.
Question: Given the impoverished visuals for mouse operations, is there a way to do this on the command line, not through the moving galaxy syntactic sugar that just gets in the way? Can I run the whole restore operation in Terminal? Of course, still via Back to My Mac, because I don't know how to get to the remote iMac in any other way remotely, given that it sits behind a cable modem and a Time Capsule router with NAT. And I don't want to set up port forwarding, if I don't have to.
Thanks for reading, and I'll take your considered expert advice.
-- Marek

Well, I have now reformatted/partitioned my poor WD Elements 2TB drive about a dozen times as well as restarted my 1TB Time Capsule so many times it's no wonder it's as confused as I am! <G>
Last night, at your suggestion, William, and in respect for your continued support, I tried creating two 1TB Mac OS Extended (Journaled) partitions on the WD external USB drive, both with GUID partition tables. Both volumes mounted to my laptop's desktop flawlessly and without issue.
Once the external drive was connected to the Time Capsule, however, it was a crap shoot as to whether or not the drive was recognized at all, reporting a problem with the disk, or, even at one point, mounting one of the two volumes but not both. <sigh>
I read somewhere on the Internet that you need to restart the Time Capsule for volumes on an external USB drive to be recognized.
So I tried that. I connected the freshly partitioned/formatted disk to the Time Capsule and restarted it. This succeed in removing the issue of reporting a nameless drive with a capacity of 0MB. It then reported the drive with its correct name but would not recognize whatever volumes in whatever partitions that particular crack at it contained with the exception of the once, as I mentioned above, when only one of two volumes mounted correctly and was listed with the right name and capacity on the Time Capusule's Setup's Disk tab.
At this point I have given up on my goal to use the external drive with Time Machine to back up my Macs or to hope I will ever be able to see its contents remotely via Back to My Mac. All I would like to do now is simply find a reason why I can't get it successfully connected and playing nice with my Time Capsule in the first place!
Any further suggestions or advice as to what steps I might take next would be greatly appreciated.
Thank you all.

Time Machine over the Network

Hello,
I've been using Time Machine for over 3 years now with no issues over the network; the destination being a 1TB-limited sparseimage setup as instructed by this tutorial. The image resides on an external HD connected on a network-connected iMac. Everything has been working flawlessly: Every hour Time Machine would MOUNT the disk image on its own, BACKUP the data and UNMOUNT the disk image as well.
Until I upgraded to Lion. The above process is still working per se, however it is PAINFULLY slow! A 50MB backup can take up to AN HOUR! Searching around on the net, advised that there could be an issue with Spotlight as well, however this is not the case for me, since Spotlight finished a new index in under 30 mins.
While testing, I tried to copy a 200MB file ONTO the Time Machine disk (mounted from the sparseimage automatically by Time Machine) and it took OVER 3 hours! I then stopped Time Machine (which tool half an hour) and mounted the image via Finder and the same file copied in 4 secs!
I really don't get it; I bet both times the mounted Volume runes under the same protocol, AFP via TCP, why is it behaving so strangely when auto-mounted by Time Machine?
Next, I read about tmutil has been added to Lion upwards and that setting a mounted disk image as destination is now supported by TM. So I went on and mounted the image via the Finder, set the mounted Volume as the time machine destination via tmutil and gave the backup a try. The process went away really fast, was extremely pleased!
However: As soon as the backup finishes, the Volume EJECTS and TM reports that the next backup is to be made "when the backup disk is connected"! It will NOT mount the image by its own, neither to backup or to access old backups. But wait, there's more: Be selecting "Backup now" via the TM menu item, the Volume MOUNTS INSTANTLY and the backup takes place, with no issues whatsoever!
What I need is a TM that backs up quickly over the network and mounts its disk automatically.
Well, I guess if you had the time and will to read the above text, you may try to help, if you have a clue, that is...
Thank you.

I am afraid that the information on the excellent tutorial (which I have already checked many times) don't help me much... I have two main questions:
1. Why is the TM-mounted volume so slow? Mounting the same volume through the Finder works blazing fast! Is there something special in the way TM mounts its volumes?
2. Is there a proper way to force TM to start an automatic backup, when the backup volume is not mounted? It used to work when the destination was the network volume, but does not work when the destination is set to the sparsebundle volume which inside the network volume.

Automatically Start Time Machine

Since upgrading to OS X Mavericks over a month ago, I have to open Time Machine Preferences and select my external HD/disk EVERY time that I reboot my iMac. Otherwise, Time Machine will not start despite the TM slide being "On." I was talking with an Apple Care representative about an Aperture 3.5 issue this morning and mentioned this. (I originally thought that it was something new with Mavericks. He said that it should not be doing this, but was not an expert in TM.)
Thank you in advance for any help!

Hi there oozie1982,
You may find the troubleshooting steps in the article below helpful.
Time Machine: Troubleshooting backup issues
http://support.apple.com/kb/ht3275
-Griff W.

OS X 10.5.3 update... Does Time Machine over network still work

Anyone updated to the new 10.5.3 and know if Time Machine still works over the network via AEBS?

I was hoping 10.5.3 would fix things for time machine/time capsule, I had issues with it hijacking my laptop and the network doing fsck_hfs. So I looked forward to fixes, had been doing only back up now, since having to reset everything. I tried it, it took an our to get past preparing, then had 15 meg out of 2 gig backing up, stuck there for hours. I finally killed it by dismounting the disk. When my disappointment reduces I may try a fresh start. I am sure they worked very had on it.

Time Machine over WiFi with Airport Extreme

I have had an iMac for 5 years with a WD 500 gb drive hardwired (Firewire 400) into the machine for use with Time Machine. I just got a new Macbook Pro 15". When I opened the machine, I migrated everything over from my old iMac using the Time Machine Backups drive. Everything was working fine and TM recognized all of my old backups.
A couple days later, I wanted to up the portability of the laptop so I plugged my drive in USB to my Airport Extreme. The Macbook immediately recognized the shared drive and every put a little "Time Machine Backups" icon mounted on the desktop. I went into the Time Machine preferences and designated the network drive as my backup drive. It seemed to be working but the first time it went to backup, it created a new .sparsebundle file, even though I still have the Backups folder full of the old backups. It then tried to create another .sparsebundle file with the same name as my computer but with a 1 at the end.
I went to my local Genius bar and the guy plainly said "Time Machine does not work wirelessly unless its a time capsule. (Sarcastically) The only people who can answer that question are the software engineers who designed Time Machine".
The fact that Time Machine and the MBP immediately recognized the wireless drive as a backup disk tells me that its possible to do it. Is there anyway to tell Time Machine to include all of the backups on the drive and not to start from scratch??
Thanks.

iliv4apl wrote:
But I was not using a new backup drive, it was the same drive, just different connection. How do I tell it to incorporate the backup files on the drive into the time machine program?
You can't. Time Machine stores it's backups differently when they're done over a network, and you can't switch between the two.
You might be able to copy the "local" backups to be used over the network. See #18 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).
And you need to know that backing up with Time Machine to a USB drive connected to an Airport Extreme is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).

Start time machine over?

Similar Messages

Maybe you are looking for