HT3275 start time machine backup immediately

How to start a time machine backup immediately ?

Click on the Time Machine "clock" icon at the top of the Mac's screen
Click Backup Now
Otherwise, backups will occur automatically each hour.

Similar Messages

Using Automator to start Time Machine backup then eject?

I've been fooling around with Automator because I want to create an application so when I mount my Time Machine disk and I run the application, the Time Machine backup with start and once it's finished it will automatically eject the volume.
I used the following shell script to begin the TM backup:
/System/Library/CoreServices/backupd.bundle/Contents/Resources/backupd-helper &
I used the following Applescript to eject the volumes:
tell application "Finder"
eject (every disk)
end tell
The problem is, when I save it as an application and I run it, I can see TM backup starts but it immediately ejects the disk. What can I add so it will eject the disk AFTER the TM backup has completed?
I have a MBP (late 2011) with OS X 10.7.4

Two comments:
1) Try removing the ampersand ("&") from the end of that command. The ampersand causes the command to continue in the background while the script continues to the next step. You want the script to wait until that command is complete.
2) You posted your question in a section for Apple's Time Capsule Wi-Fi router. Presumably you want support for the Time Machine backup hardware. Such a question should be posted in the section for the OS X version you're running.

HT3275 Reuse Time Machine Backup after moving to new Machine

So I've been using TIme Machine for ages, and usually the restore are fine, but one thing has always bugged me:
When I restore (say for a new hard drive) or bought a new machine (in this case i got the Retina MBP)... and i turn on Time Machine again... I haven't been able to find a way to use the old backup disk on my Time Capsule.
Looking into the support info, I found this:
Message: Time Machine starts a new, full backup instead of a smaller incremental backup
There are three reasons why this may occur:
You performed a full restore.
Your Computer Name (in Sharing preferences) was changed--when this happens, Time Machine will perform a full backup on its next scheduled backup time.
If you have had a hardware repair recently, contact the Apple Authorized Service Provider or Apple Retail Store that performed your repair. In the meantime, you can still browse and recover previous backups by right-clicking or Control-clicking the Time Machine Dock icon, and choosing "Browse Other Time Machine disks" from the contextual menu.
Reading that, I'm led to assume that's just one of the quirks and I can't do anything, and deleting Time Machine backups is quite a hassle as it is.
Is there really no way for my new Retina Macbook to use my old MBP time machine backup and just keep adding incremental data to it? It seems redundant then as say a week ago I deleted something... I actually have no way of getting to it now if I deleted the backup and started again. At the moment, my Time Capsule doesn't have enough space for a complete new one, so i'd HAVE to delete the old one.
Is there a way around this?
Thanks.

ladines wrote:
My account name is the same in both systems.
The account name isn't what controls the permissions; it's the automatically-assigned and mostly-invisible User ID number, also called a UID. The first user account you create is number 501, the next 502, etc. So if you ever had more than one user account, the one(s) you have now may be different. See the pink box in Problems after using Migration Assistant for a detailed explanation.
You really can't change the permissions on Time Machine backups (that would kinda defeat the purpose).
Try creating another account, and see if it has permission to the backups. If it does, you have a couple of options:
* Copy everything now on your system to the new User Account you created above. That's tedious and error-prone, but can be done. See Transferring files from one User Account to another.
* Your existing user account should be able to see and restore from new backups (done from the new drive). When you need to view or restore things from the old backups, use the new account. Eventually, as the older backups are deleted, the problem will fade away.

HT3275 My time machine backup hangs up when partly completed. It seems to back up 7.4 MB out of 159.8 MB, and then keeps on turning but nothing seems to be happening. I tried troubleshooting it by doing a disk utility on the external hard drive used for T

My Time Machine seems to be hanging up (stopping) beforew completion. I'm running Mountain Lion (OS X 10.8.2) on my iMac G5, and I already trouble-shot the external drive used for Time Machine by using Repair on Disk Utilities. So--what gives?

IMac G5 with Mountain Lion.. amazing.. I am pretty sure support for early Intel stopped at ML and support for G5 long before that.
Load the widget and see if you get error message that the TM is ejecting the drive.. before the backup is complete.. that is one of those nice.. features.. Apple has made available in recent updates.. sometimes called bugs.
A1 in here http://pondini.org/TM/Troubleshooting.html
Also look at the other info.. C12 C17 are common issues.

Time Machine backup disappears when iMac sleeps

Tried finding this topic but could not find the specifics. I have an Intel iMac running 10.6.7 and I use a Mercury enclosure with a Seagate Barracuda 2TB SATA for Time Machine backup, connected with FireWire. Every time my Mac goes to sleep overnight, the next morning, the Time Machine icon disappears from the desktop. It's been disconnected, because when I run Check Time Machine, the log reads thusly:
<<Thu Apr 21 10:29:30 com.apple.backupd-auto Not starting scheduled Time Machine backup - time machine destination not resolvable.
Thu Apr 21 12:30:05 [0x0-0x2d22d2].backupd-helper Not starting Time Machine backup after wake - failed to resolve alias to backup volume
>>
Occasionally I'll get the error message on the Mac that a device has been "improperly disconnected" but most of the time when it sleeps the TM drive icon just goes away (even tho the backup drive is still on).
Any ideas? Can I fix this or have to live with it? Are there alternatives to TM that may work better?
Thanks for any help/suggestions.
Best,
Mike

I had the same problem as Bru-Hed, but with a Samsung G3 Station 1 TB with USB-connection. After waking up the MAC the message "improperly disconnected" appeared. Was happy with the solution you gave and changed the power save settings accordingly, the drive holds its power, but....... things did not change. Switching off the MAC and restarting gives no problems with the back-up drive, but after waking up I have to reinstall the back-up drive every time by disconnecting and connecting the USB-connector. After choosing the drive again in Time Machine, everything works properly until the next time the MAC goes asleep......
Any other solution to this problem ?

Time Machine Backup - 1st time very long?

Iv'e finally decided to use this app - bought an external drive, and started time machine backup. I have 3 internal drives with over 400 GB total info to back up and it's been going for almost 24 hours so far, and the file on the drive is 100 GB or so. Is this normal? At this rate the backup could end up taking another 2 days. That seems like an awfully long time! Any comments on this would be helpful.
Thanks!

OK, thanks for the input again. All subsequent backups have been recorded as successful by the way…
Here's the log from the first one that gave the "Unknown" status:
Starting standard backup
Backing up to: /Volumes/GLYPH-1 TB/Backups.backupdb
No pre-backup thinning needed: 454.50 GB requested (including padding), 889.92 GB available
Copied 12.3 MB of 378.2 GB, 505 of 1998322 items
Copied 20.6 MB of 378.2 GB, 799 of 1998322 items
Copied 107.6 MB of 378.2 GB, 1089 of 1998322 items
Copied 18.0 GB of 378.2 GB, 177956 of 1998322 items
Copied 18.0 GB of 378.2 GB, 178236 of 1998322 items
Copied 18.0 GB of 378.2 GB, 178516 of 1998322 items
Copied 18.0 GB of 378.2 GB, 178795 of 1998322 items
Copied 18.0 GB of 378.2 GB, 179095 of 1998322 items
Copied 18.0 GB of 378.2 GB, 179379 of 1998322 items
Copied 50.8 GB of 378.2 GB, 210562 of 1998322 items
Copied 210563 files (51.1 GB) from volume StudioA!.
Copied 355630 files (174.6 GB) from volume StudioB!.
Copied 174.7 GB of 378.2 GB, 355894 of 1998322 items
Copied 174.8 GB of 378.2 GB, 356307 of 1998322 items
Copied 174.9 GB of 378.2 GB, 356703 of 1998322 items
Copied 175.0 GB of 378.2 GB, 357101 of 1998322 items
Copied 175.4 GB of 378.2 GB, 357528 of 1998322 items
Copied 175.9 GB of 378.2 GB, 358133 of 1998322 items
Copied 176.0 GB of 378.2 GB, 358613 of 1998322 items
Copied 176.0 GB of 378.2 GB, 358966 of 1998322 items
Copied 176.1 GB of 378.2 GB, 359678 of 1998322 items
Copied 176.4 GB of 378.2 GB, 360936 of 1998322 items
Copied 177.7 GB of 378.2 GB, 362831 of 1998322 items
Copied 225.6 GB of 378.2 GB, 396918 of 1998322 items
Copi
As I said, though, it looks like all the files are there. If this is a good and "safe" backup then I'm good to go!
Hypothetically though, if I wanted to start from scratch, how would I do it?
Thanks again,
Wayne

"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

Can't boot my Mac after attempt of Time Machine backup

So guys,
I just bought new Macbook Pro and it came with Yosemite. It is one thing that I specifically asked not to get with it, but I did. Anyway, since I didn't want it, I instantly went to Time Machine backup my previous Mac to the new one.
I booted my new Mac in recovery and started the time machine process. It went trough, found a backup that I wanted, asked me for my password and all looked nice. When the process started, it said something is wrong and rebooted. Now each time I want to start time machine backup process, I get the same message that says "searching for disks" when it comes to the moment of finding the system drive in the lap top. It will not boot any longer to the system. When i wanted to reinstall Yosemite, it doesn't see the drive that is supposed to see to install it. It sees only some small recovery drive. When I go to disk utility, I see Machintosh HD and some disk 1 drive that has sub group OS X Base System. Non of the options on drives like erase, format or similar are available. I basically can't do anything.
Someone has any idea what should I do?
Thanks in front!

Please install OS X on an external device (USB/FW/TB/Flash disk-16GB) using OS X: Installing OS X on an external volume - Apple Support and boot from it.
Post the output of the following command from OS X Terminal when booted from this external device. Enter your password when prompted, and it will not be echoed back.
sudo gpt -vv -r show /dev/disk0

HT3275 What do i do when, having reconnected my Time-Machine Backup disk, i'm told that there is not sufficient space to do a backup ? it seems somehow that my previous backup was "closed" and i cannot continue using it, so Time machine appears to start a

I use an external 500 GB WD hard drive for my Time-Machine backup.
Sometimes - several times - after i've disconnected the drive to go travelling, when i reconnect the external drive, Time Machine tries to resume but tells me there is not enough space on the drive, and to chose a bigger disk.
It is as if the previous backup file is "closed' and cannot be written to again.
The only fix i can find is to erase, start again from scratch and do a full backup from scratch - which totally defeats the purpose of Time Machine.
I've tried repairing the disk, nothing appears to allow the previous backup to be continued.
Suggestions please ??
Jean-Noel Cozon

Hi Linc,
Thanks for getting back - if i understood correctly, the info you suggested i collect is hereunder ...
Jan 22 06:08:09 MBP-15 com.apple.backupd[4353]: Starting standard backup
Jan 22 06:08:10 MBP-15 com.apple.backupd[4353]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 06:10:54 MBP-15 com.apple.backupd[4353]: No pre-backup thinning needed: 3.12 GB requested (including padding), 234.07 GB available
Jan 22 06:18:20 MBP-15 com.apple.backupd[4353]: Copied 28083 files (2.2 GB) from volume MBP-15.
Jan 22 06:21:57 MBP-15 com.apple.backupd[4353]: No pre-backup thinning needed: 3.13 GB requested (including padding), 231.88 GB available
Jan 22 06:29:10 MBP-15 com.apple.backupd[4353]: Copied 23509 files (2.2 GB) from volume MBP-15.
Jan 22 06:32:01 MBP-15 com.apple.backupd[4353]: Starting post-backup thinning
Jan 22 06:32:01 MBP-15 com.apple.backupd[4353]: No post-back up thinning needed: no expired backups exist
Jan 22 06:32:02 MBP-15 com.apple.backupd[4353]: Backup completed successfully.
Jan 22 07:08:09 MBP-15 com.apple.backupd[4474]: Starting standard backup
Jan 22 07:08:10 MBP-15 com.apple.backupd[4474]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 07:10:52 MBP-15 com.apple.backupd[4474]: No pre-backup thinning needed: 3.13 GB requested (including padding), 231.88 GB available
Jan 22 07:18:26 MBP-15 com.apple.backupd[4474]: Copied 28091 files (2.2 GB) from volume MBP-15.
Jan 22 07:22:02 MBP-15 com.apple.backupd[4474]: No pre-backup thinning needed: 3.13 GB requested (including padding), 229.69 GB available
Jan 22 07:29:22 MBP-15 com.apple.backupd[4474]: Copied 23517 files (2.2 GB) from volume MBP-15.
Jan 22 07:32:14 MBP-15 com.apple.backupd[4474]: Starting post-backup thinning
Jan 22 07:32:14 MBP-15 com.apple.backupd[4474]: No post-back up thinning needed: no expired backups exist
Jan 22 07:32:15 MBP-15 com.apple.backupd[4474]: Backup completed successfully.
Jan 22 08:08:10 MBP-15 com.apple.backupd[4595]: Starting standard backup
Jan 22 08:08:10 MBP-15 com.apple.backupd[4595]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 08:10:56 MBP-15 com.apple.backupd[4595]: No pre-backup thinning needed: 3.13 GB requested (including padding), 229.68 GB available
Jan 22 08:18:19 MBP-15 com.apple.backupd[4595]: Copied 28099 files (2.2 GB) from volume MBP-15.
Jan 22 08:21:50 MBP-15 com.apple.backupd[4595]: No pre-backup thinning needed: 3.14 GB requested (including padding), 227.49 GB available
Jan 22 08:29:18 MBP-15 com.apple.backupd[4595]: Copied 23525 files (2.2 GB) from volume MBP-15.
Jan 22 08:32:09 MBP-15 com.apple.backupd[4595]: Starting post-backup thinning
Jan 22 08:32:09 MBP-15 com.apple.backupd[4595]: No post-back up thinning needed: no expired backups exist
Jan 22 08:32:10 MBP-15 com.apple.backupd[4595]: Backup completed successfully.
Jan 22 09:08:09 MBP-15 com.apple.backupd[4716]: Starting standard backup
Jan 22 09:08:10 MBP-15 com.apple.backupd[4716]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 09:10:55 MBP-15 com.apple.backupd[4716]: No pre-backup thinning needed: 3.13 GB requested (including padding), 227.49 GB available
Jan 22 09:18:48 MBP-15 com.apple.backupd[4716]: Copied 28107 files (2.2 GB) from volume MBP-15.
Jan 22 09:22:40 MBP-15 com.apple.backupd[4716]: No pre-backup thinning needed: 3.27 GB requested (including padding), 225.30 GB available
Jan 22 09:32:35 MBP-15 com.apple.backupd[4716]: Copied 23533 files (2.3 GB) from volume MBP-15.
Jan 22 09:35:25 MBP-15 com.apple.backupd[4716]: Starting post-backup thinning
Jan 22 09:35:25 MBP-15 com.apple.backupd[4716]: No post-back up thinning needed: no expired backups exist
Jan 22 09:35:26 MBP-15 com.apple.backupd[4716]: Backup completed successfully.
Jan 22 10:08:09 MBP-15 com.apple.backupd[4840]: Starting standard backup
Jan 22 10:08:10 MBP-15 com.apple.backupd[4840]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 10:10:51 MBP-15 com.apple.backupd[4840]: No pre-backup thinning needed: 3.14 GB requested (including padding), 225.18 GB available
Jan 22 10:18:12 MBP-15 com.apple.backupd[4840]: Copied 28115 files (2.2 GB) from volume MBP-15.
Jan 22 10:21:49 MBP-15 com.apple.backupd[4840]: No pre-backup thinning needed: 3.14 GB requested (including padding), 222.99 GB available
Jan 22 10:29:05 MBP-15 com.apple.backupd[4840]: Copied 23541 files (2.2 GB) from volume MBP-15.
Jan 22 10:32:00 MBP-15 com.apple.backupd[4840]: Starting post-backup thinning
Jan 22 10:32:00 MBP-15 com.apple.backupd[4840]: No post-back up thinning needed: no expired backups exist
Jan 22 10:32:01 MBP-15 com.apple.backupd[4840]: Backup completed successfully.
Jan 22 11:08:09 MBP-15 com.apple.backupd[4963]: Starting standard backup
Jan 22 11:08:10 MBP-15 com.apple.backupd[4963]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
Jan 22 11:10:53 MBP-15 com.apple.backupd[4963]: No pre-backup thinning needed: 3.14 GB requested (including padding), 222.82 GB available
Jan 22 11:18:10 MBP-15 com.apple.backupd[4963]: Copied 28123 files (2.2 GB) from volume MBP-15.
Jan 22 11:21:46 MBP-15 com.apple.backupd[4963]: No pre-backup thinning needed: 3.14 GB requested (including padding), 220.63 GB available
Jan 22 11:30:13 MBP-15 com.apple.backupd[4963]: Copied 23553 files (2.2 GB) from volume MBP-15.
Jan 22 11:33:03 MBP-15 com.apple.backupd[4963]: Starting post-backup thinning
Jan 22 11:33:03 MBP-15 com.apple.backupd[4963]: No post-back up thinning needed: no expired backups exist
Jan 22 11:33:04 MBP-15 com.apple.backupd[4963]: Backup completed successfully.
Currently, having once again yesterday flattened and restarted my T-M from scratch i probably overwrote all the backups since the last time i had to do that - and as long as i don't disconnect my external backup drive it seems OK now.
I'm a bit paranoid as i use my MBP both as my Mac, but also as my Virtual PC so i have a lot of technical and commercial data which i need to keep properly backed up.
Is it possible when i've ejected my TM backup disck, gone travelling, and then reconnected it some days later - that i am causing a new backup to start by hitting the 'Backup Now' command on the menu bar.... should i let TM pickup by itself automaticvally without porvoking a Backup Now command ?
Thanks in advance for any futher advice

I have a mid2009 MacBook Pro for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

I have a mid2009 MacBook Pro running Mavericks for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

no archive/ backup is perfect, HD clones can be set to make incremental additions, same as time machine however, though they are more time involved in doing so.
See the + and - of all data backup/ archives below and "spread it around".... or the "dont put your eggs all in one basket" philosophy.
Peace
Data Storage Platforms; their Drawbacks & Advantages
#1. Time Machine / Time Capsule
Drawbacks:
1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
6. Restoring from TM is quite time intensive.
7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
13. *Level-1 security of your vital data.
Advantages:
1. TM is very easy to use either in automatic mode or in 1-click backups.
2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
#2. HD archives
Drawbacks:
1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
Advantages:
1. Fills the gap left in a week or 2-week-old HD clone, as an example.
2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
4. Best-idealized 1st platform redundancy for data protection.
5. *Perfect primary tier and level-2 security of your vital data.
#3. HD clones (see below for full advantages / drawbacks)
Drawbacks:
1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
Advantages:
1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
3. HD clones are unconnected and isolated from recent corruption.
4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
7. *Level-2 security of your vital data.
HD cloning software options:
1. SuperDuper HD cloning software APP (free)
2. Carbon Copy Cloner APP (will copy the recovery partition as well)
3. Disk utility HD bootable clone.
#4. Online archives
Drawbacks:
1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
Advantages:
1. In case of house fire, etc. your data is safe.
2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
5. *Level-1.5 security of your vital data.
#5. DVD professional archival media
Drawbacks:
1. DVD single-layer disks are limited to 4.7Gigabytes of data.
2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
Advantages:
1. Archival DVD professional blank media is rated for in excess of 100+ years.
2. DVD is not subject to mechanical breakdown.
3. DVD archival media is not subject to ferromagnetic degradation.
4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
5. DVD media is once written and therefore free of data corruption if the write is correct.
6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
7. Best-idealized 4th platform redundancy for data protection.
8. *Level-3 (highest) security of your vital data.
[*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
#6. Cloud based storage
Drawbacks:
1. Cloud storage can only be quasi-possessed.
2. No genuine true security and privacy of data.
3. Should never be considered for vital data storage or especially long-term.
4. *Level-0 security of your vital data.
Advantages:
1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
2. Easy source for small-file data sharing.

How to manually start a Time Machine backup?

Is there any way to invoke a time machine backup?
It seems that it's set on its schedule and that's that .... you can't tell it to run a backup.....

Make sure you have the TM icon in your dock (drag it from Applications if necessary)
To start a back immediately, right-click the icon and select 'Back Up Now'

Can't start with Snow Leopard Time Machine backup in Lion

Hi,
I have seen coverage in MacWorld (http://www.macworld.com/article/161421/2011/07/migrate_time_machine_backup_to_ne w_mac_in_lion.html) of using my Snow Leopard Time Machine backup as the starting point for my Lion TM backup. This saves all my revision history of all my documents and makes them available in Lion. However, when I follow the steps given in the MacWorld article, I don't get the same set of dialog boxes and am never given the option to use a previous disk.
Any hints to getting this to work would be much appreciated.
-Eric

A whole lot about Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
Pondini's Time Machine FAQ

Trying to use a new, larger external hard drive for my Time Machine backup. However, every time I start the backup, it gets started then fails. And, I can't delete the few files that did save on the external. Sort of a catch 22. Any ideas?

Trying to use a new, larger external hard drive for my Time Machine backup. However, every time I start the backup, it gets started then fails. And, I can't delete the few files that did save on the external. Sort of a catch 22. Any ideas?

Is it a USB hard drive? USB hard drives have the problem of not giving full speed if they are hooked up on the same bus as keyboards and mice. Double check your profiler to make sure that is not a problem. If it is Firewire, make sure there aren't other firewire devices in use at the same time. I recommend not only keeping a Time Machine backup, but also a clone, and if you do use Time Machine, to make sure the Time Machine drive or partition is at least twice the size of the original drive.

Restored system from Time Machine backup disk but the system could not start-up

On MacBook Pro early 2008, restored the entire system from Time Machine backup disk to the entire disk.
The previous system on the backup disk had FileVault turned on.
The restore completed successfully and I was prompted to restart the system via the new restored system disk.
I heard the normal start-up sound, then the Apple logo, but it stuck at the logo screen. And the cooling fan run at almost full speed?
I have been waiting for a few hours, guessing it might FileVault the disk.
Finally I have to shutdown the machine as it stuck at the logo screen forever.
Anyone has the same issue? Any ideas?

BTW, I also tried Repair the system disk, Fix permissions via Disk Utility.
I guess I must lose some files either during the backup or the restore.

Is there any way to create a time machine backup to an external hard drive with content already on it? I have a hard drive that i have used for pictures but when i try to run a backup it says i need to start from a blank drive. Can i get around it?

Is there any way to create a time machine backup to an external hard drive with content already on it? I have a hard drive that i have used for pictures but when i try to run a backup it says i need to start from a blank drive. Can i get around it?

It would be much better if you had separate drives for the pictures and Time Machine backups.....but, if you want to use the same drive for both purposes, temporarily move the folder with the pictures to another location for safe storage.
Run the Time Machine backup on the hard drive and verify that everything is working correctly. Time Machine will format the disk for you in Mac OS Extended (Journaled) as part of the backup process.
Then move the folder with the pictures back to the hard drive with the Time Machine backups.
When you have tested to make sure that everything is working again, then and only then should you delete the folder with pictures from the temporary storage area.
Again....it would be much better to keep Time Machine backups on a drive just for that purpose, and other data on another drive for that purpose. This is clearly one of those times when the fact that you can do something does not mean to imply that you should do it.

HT3275 start time machine backup immediately

Similar Messages

Maybe you are looking for