Slow copying a Time Machine sparsebundle

Hi everyone,
I stored old and no longer used Time Machine sparsebundle files on my networked Drobo drive. I bought a new DroboFS which is also networked. I have been moving files from the old unit to the new unit, and copying over the network is very fast.
That is, until I tried to copy the sparsebundle files. For example, I tried to move one of the sparsebundle files. Finder says "Preparing to copy". It has been saying that now for 3 days. The sparsebundle files are large, in the 1 TB range. Is Finder unable to copy or move these files? If so, is there another way to move them?
Cheers!
Phil

The Snow Leopard Finder (but not the Leopard version) can copy them, if they're undamaged. Try Repairing them, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum). Use the procedure for a Time Capsule.
But there are many thousands of "bands" in a sparse bundle, and they won't copy quickly under the best of circumstances.

Similar Messages

My Fantom backup drive is failing. I want to copy the time machine contents to a new backup drive and continue on as if nothing has happened. Can I do this and if so how? I have intel iMac running Mountain Lion. Fantom Drive via Firewire 800.

My Fantom backup drive is failing and I have to send it in for warranty repair. Before I do that I want to copy the time machine contents to a new drive and then use it for the backup, continuing on as if nothing had gone wrong with the first drive. Can I do this? Is it as simple as duplicating the first drive and replacing it with the second? New drive arrives Tuesday PM and both drives have dual firewire 800 ports.

I have used the Disk Utility to verify the contents of the backup drive so I don't think I have any corrupt files. The drive just takes a minute or so to spin up to speed. If I turn it off and then back on, it beeps at me for a few seconds and then starts it's slow process of trying to spin. I think it's a power problem not a data problem. I have my fingers crossed that it holds on until Tuesday PM when the new drive arrives. I'm thinking that my two options are to duplicate the bad drive or partition the new drive and put the old backups on one partition and start afresh on the second partition. Any input?
And thanks to both of you for the valuable information so far!

Strange error trying to restore from time machine sparsebundle

I had my iMac hard drive go bad, so I replaced it, powered the unit back up and booted into the Snow Leopard install disk.
I got to the step where I'm trying to restore from my Time Machine .sparsebundle and I selected the date and time of the backup I wanted to restore. When I click Next to go the next screen (Select a Destination) the utility gets stuck "Searching for Disks," and below that a warning icon says
"This disk does not have enough space to restore your system."
This sounds scary, and as the Time Machine drive now has the sole copy of my data I'm reluctant to do anything to it.
Does anyone know what's going on?
Thanks in advance,
Dan.

Are you sure the new drive is formatted properly?
Check it via Disk Utility (you can get there from the same Utilities menu where you selected +Restore from backups).+
Select the top line of the drive (with size and make). Be sure the *Partition Map Scheme* at the bottom says +GUID Partition Table.+
Then select the next line, with the name you gave it, and be sure the Format shown towards the lower left is +Mac OS Extended (Journaled),+ unless you made it +Mac OS Extended (Case-Sensitive, journaled),+
Also see how much space it shows for Available to the right.

Backup time machine sparsebundle

My time machine sparsebundle is corrupted and after trying many different ways to repair it, it is time to reformat the hard drive.
I read that there is a way to copy the TM sparsebundle to an external drive connected to Time Capsule. Unfortunately, I can no longer find the article.
Can anyone tell me how to move my corrupted sparsebundle to an external usb drive?
Thanks

How to load 5.6 into ML.
1. Download 5.6 for Lion.
http://support.apple.com/kb/DL1482
Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
2. Download and install unpkg.
http://www.timdoug.com/unpkg/
Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
For screen shots see this post.
https://discussions.apple.com/thread/4668746?tstart=0
This is only one method.. if you google you will see any number of methods but they generally require you to pay for software.. this is free.

Copy from Time machine to an new iMac doesn't Work ?

I bought a new iMac and want to copy from time machine that is on an external disk. Copying stops after 10 minutes. What to do?

Please visit Pondini's Time Machine FAQ for help with all things Time Machine.

How can I copy a time machine backup from one Time Capsule to another ?

How can I copy a time machine backup from one Time Capsule to another ? I bought a 1 Tb Time Capsule to replace my 512Mb Time Capsule. Now, I like to copy my time machine backup from the old Time Capsule to the new one so I can keep using my backup.

from this support article:
(click on image to enlarge)

Blurb Book in Lightroom 5 on my Mac disappeared after 3 days of work. Where can I find a backed up copy via Time Machine or anywhere else?

Blurb Book in Lightroom 5 on my Mac disappeared after 3 days of work. Where can I find a backed up copy via Time Machine or anywhere else?

Welcome to the WD Community.
1) I assume I can just hook the unit up via USB to my Mac and use iPartiion to reformat the drives, assuming each of the 4T drives will be seen by iPartition as a separate drive. That much seems straighforward.
Yes, and in case you ipartition dont see the unit properly, you can use the disk utilities on your Mac and you will be able to reformat the unit to make it compatible with your system.
2) Is my next step to reinstall the WD software and how do I do that? I've downloaded the Drive Utilities and Securities install apps - I assume I just run these with the drive still connected and that's all I need to do?
Yes, just run the applications.
3) What about the firmware update for Mac - when should I run that??
Normally, firmware updates are released to fix any issues that you might encounter on the drive. the latest one was released on 9/24/2014 and it fixed an issue with the drive dropping off of the list after system wakes up from standby mode.
5) And what about the "My Book Live Duo Setup" app for Mac - is that for a completely different model? What's the difference between "My Book Live Duo" and "My Book Duo"? It's these little things that I find so confusing.
Those are different units. The MBL Duo is a NAS (Network attached system) and the My Book Duo is a DAS (Direct attached system)
6) Lastly, when I have all the software installed, is that when I follow the procedure described in the Knowledge Base article ID 5724, "How to install a My Book Live or My Book Live Duo on Windows (8, 7, Vista, or XP) or Mac OSX for the first time"? Or is that procedure only for "My Book Live Duo" but not for "My Book Duo"??
That procedure is for the network units, not for your drive.

Trying to repair a Time Machine sparsebundle

I am trying to repair a Time Machine sparsebundle file. However I am getting errors at the first step of trying to attach the image.
hdiutil attach -nomount -noverify -noautofsck -verbose /Volumes/ReadyNAS/RobertsiMac.sparsebundle
Initializing…
CBSDBackingStore::newProbe directory, not a valid image file.
DIBackingStoreInstantiatorProbe: interface 0, score    -1000, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score    -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
CBSDBackingStore::newProbe directory, not a valid image file.
DIBackingStoreInstantiatorProbe: interface 0, score    -1000, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score    -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
Attaching…
Error 110 (image not recognized).
Finishing…
DIHLDiskImageAttach() returned 110
hdiutil: attach failed - image not recognized
Any help or suggestions greatly appreciated.
Regards
Bob

Backing up to a third-party NAS with Time Machine is risky, and unacceptably risky if it's your only backup. I know this isn't the answer you want, and I also know that the manufacturer says the device will work with Time Machine, and that it usually seems to work. Except when you try to restore, and find that you can't.
If you want network backup with Time Machine, use as the destination either an Apple Time Capsule or an external hard drive connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
If you're determined to keep using the NAS for backup, your only recourse for any problems that result is to the manufacturer (which will blame Apple.)

Slow 10.8 time machine backup to wired network

I have a MacPro with a big backup drive and a MacBook Pro that backs up to it over a wired network. Ever since I upgraded to ML, my backups have been extremely slow. [An incremental of 70 MB can take a few hours. A full backup reports weeks, and gets slower and slower. I've aborted after 30 days and 50% complete.]
I plugged in a drive directly and that worked fine.
I've tried lots of things I've read about in multiple places: repairing disks and permissions, resetting time machine, turning off spotlight and antivirus. I'm not sure what else to try.
One thing to note: If I mount the sparse backup image volume manually and copy a large (1GB) file to it, it seems to work fine. However, when TM is running it appears to get slower and slower. It becomes extremely slow to access both in the finder and in the terminal [like minutes if I type ls].
Any suggestions offered would be greatly appreciated.

After a safe boot, TM still isn't working normally. It does usually work, it is just glacially slow (backing up over wired gigabit ethernet).
On my just-backed-up laptop, I made a 2GB file from /dev/random. It took about 5 hours for TM to complete.
Note that if I manually mount the backup drive and copy the file, it copies in about a minute.
This is my trimmed log during the TM backup.
I've deleted the following from the log to shorten it:
every 15 minutes I get long messages from CalendarAgent, starting with:
CalendarAgent[469]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=CoreDAVHTTPStatusErrorDomain Code=401 "The operation couldn’t be completed. ...
every 55 minutes I get lots of long spam from GoogleSoftwareUpdateDaemon, starting with:
GoogleSoftwareUpdateDaemon[5576]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
this includes: kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=5574[GoogleSoftwareUp] clearing CS_VALID
and ends with: GoogleSoftwareUpdateDaemon[5929]: -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.
Here's the remaining log:
5/2/13 1:40:53.083 PM com.apple.backupd[5332]: Starting automatic backup
5/2/13 1:40:53.117 PM com.apple.backupd[5332]: Attempting to mount network destination URL: afp://[email protected]/syrinx3
5/2/13 1:40:53.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1367520055
5/2/13 1:40:54.241 PM NetAuthSysAgent[5334]: NAHSelectionAcquireCredential complete: iakerb 206443F1BADDBB64735E9BBA72223AE8 - allen: GSSCred: 0x7fa07db041b0
5/2/13 1:40:54.423 PM NetAuthSysAgent[5334]: NAHSelectionAcquireCredential The operation couldn’t be completed. (com.apple.NetworkAuthenticationHelper error -1765328228 - acquire_kerberos failed [email protected]: -1765328228 - unable to reach any KDC in realm 8.20.153)
5/2/13 1:40:54.444 PM NetAuthSysAgent[5334]: NAHSelectionAcquireCredential The operation couldn’t be completed. (com.apple.NetworkAuthenticationHelper error -1765328353 - acquire_kerberos failed [email protected]: -1765328353 - PREAUTH_FAILED)
5/2/13 1:40:55.588 PM com.apple.backupd[5332]: Mounted network destination at mount point: /Volumes/syrinx3 using URL: afp://[email protected]/syrinx3
5/2/13 1:40:55.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
5/2/13 1:40:55.000 PM kernel[0]: AFP_VFS afpfs_mount: /Volumes/syrinx3, pid 5334
5/2/13 1:40:55.000 PM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80f9811008 /Volumes/syrinx3 (error = 0, retval = 0)
5/2/13 1:40:56.108 PM AddressBookSourceSync[5331]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7fe85181c190 {NSUnderlyingError=0x7fe851a4a9a0 "Could not connect to the server.", NSErrorFailingURLStringKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSErrorFailingURLKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSLocalizedDescription=Could not connect to the server.}
5/2/13 1:41:20.632 PM com.apple.backupd[5332]: Disk image /Volumes/syrinx3/bugs.sparsebundle mounted at: /Volumes/Time Machine Backups
5/2/13 1:41:20.635 PM com.apple.backupd[5332]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
5/2/13 1:45:12.483 PM com.apple.backupd[5332]: Using file event preflight for Bugs
5/2/13 1:46:36.691 PM com.apple.backupd[5332]: Will copy (1.96 GB) from Bugs
5/2/13 1:46:36.694 PM com.apple.backupd[5332]: Found 50 files (1.96 GB) needing backup
5/2/13 1:46:36.706 PM com.apple.backupd[5332]: 2.35 GB required (including padding), 22.92 GB available
5/2/13 1:46:36.707 PM com.apple.backupd[5332]: Waiting for index to be ready (100)
5/2/13 1:47:41.567 PM com.apple.backupd[5332]: Waiting for index to be ready (100)
5/2/13 1:48:47.021 PM com.apple.backupd[5332]: Waiting for index to be ready (100)
5/2/13 1:50:27.916 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 1:50:27.916 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 1:50:27.916 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 1:50:27.917 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 1:50:27.917 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 1:50:28.061 PM WindowServer[98]: Created shield window 0xcd for display 0x042733c0
5/2/13 1:50:28.062 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109a18750(2000), shield 0x7ff109ca9440(2001)
5/2/13 1:50:28.129 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109a18750(2000), shield 0x7ff109ca9440(2001)
5/2/13 1:59:46.546 PM WindowServer[98]: Created shield window 0xce for display 0x003f003d
5/2/13 1:59:46.547 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2000), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 1:59:46.547 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 1:59:46.548 PM WindowServer[98]: Created shield window 0xcf for display 0x003f003e
5/2/13 1:59:46.548 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 1:59:46.548 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 1:59:46.551 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 1:59:46.551 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 1:59:53.584 PM com.apple.kextcache[5425]: / locked; waiting for lock.
5/2/13 1:59:54.000 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 1:59:54.440 PM com.apple.kextcache[5425]: Lock acquired; proceeding.
5/2/13 1:59:54.537 PM com.apple.kextcache[5425]: /: helper partitions appear up to date.
5/2/13 2:09:50.343 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 2:09:50.344 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:09:50.344 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 2:09:50.344 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:09:50.344 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 2:09:50.483 PM WindowServer[98]: Created shield window 0xd3 for display 0x042733c0
5/2/13 2:09:50.483 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109a18750(2000), shield 0x7ff108c72820(2001)
5/2/13 2:09:50.549 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109a18750(2000), shield 0x7ff108c72820(2001)
5/2/13 2:12:31.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=5458[GoogleSoftwareUp] clearing CS_VALID
5/2/13 2:26:48.025 PM WindowServer[98]: Created shield window 0xd4 for display 0x003f003d
5/2/13 2:26:48.025 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2000), shield 0x7ff108c72820(2001), lock state 3
5/2/13 2:26:48.025 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:26:48.026 PM WindowServer[98]: Created shield window 0xd5 for display 0x003f003e
5/2/13 2:26:48.027 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2002), shield 0x7ff108c72820(2001), lock state 3
5/2/13 2:26:48.027 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:26:48.029 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a18750(2002), shield 0x7ff108c72820(2001), lock state 3
5/2/13 2:26:48.029 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:26:53.536 PM com.apple.kextcache[5474]: / locked; waiting for lock.
5/2/13 2:26:53.901 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 2:26:54.537 PM com.apple.kextcache[5474]: Lock acquired; proceeding.
5/2/13 2:26:54.632 PM com.apple.kextcache[5474]: /: helper partitions appear up to date.
5/2/13 2:36:51.818 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 2:36:51.819 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:36:51.819 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 2:36:51.819 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:36:51.819 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 2:36:51.958 PM WindowServer[98]: Created shield window 0xd9 for display 0x042733c0
5/2/13 2:36:51.963 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001)
5/2/13 2:36:52.039 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001)
5/2/13 2:40:14.670 PM com.apple.launchd[1]: (com.adobe.fpsaud[5511]) Exited with code: 210
5/2/13 2:40:55.983 PM AddressBookSourceSync[5515]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7fba8a485710 {NSUnderlyingError=0x7fba8b0169f0 "Could not connect to the server.", NSErrorFailingURLStringKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSErrorFailingURLKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSLocalizedDescription=Could not connect to the server.}
5/2/13 2:41:53.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1367523715
5/2/13 2:47:27.559 PM com.apple.backupd[5332]: Copied 301.1 MB of 1.96 GB, 621 of 621 items
5/2/13 2:49:16.097 PM WindowServer[98]: Created shield window 0xda for display 0x003f003d
5/2/13 2:49:16.097 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 2:49:16.098 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:49:16.099 PM WindowServer[98]: Created shield window 0xdb for display 0x003f003e
5/2/13 2:49:16.099 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 2:49:16.099 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:49:16.101 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 2:49:16.102 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 2:49:21.722 PM com.apple.kextcache[5525]: / locked; waiting for lock.
5/2/13 2:49:22.159 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 2:49:27.015 PM com.apple.kextcache[5550]: / locked; waiting for lock.
5/2/13 2:49:33.711 PM diskarbitrationd[15]: mds [51]:22787 not responding.
5/2/13 2:49:33.757 PM com.apple.kextcache[5525]: Lock acquired; proceeding.
5/2/13 2:49:33.837 PM com.apple.kextcache[5525]: /: helper partitions appear up to date.
5/2/13 2:49:33.837 PM com.apple.kextcache[5550]: Lock acquired; proceeding.
5/2/13 2:49:33.915 PM com.apple.kextcache[5550]: /: helper partitions appear up to date.
5/2/13 2:59:19.892 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 2:59:19.893 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:59:19.893 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 2:59:19.893 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 2:59:19.893 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 2:59:20.036 PM WindowServer[98]: Created shield window 0xdf for display 0x042733c0
5/2/13 2:59:20.036 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109a16860(2000), shield 0x7ff108c72820(2001)
5/2/13 2:59:20.102 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109a16860(2000), shield 0x7ff108c72820(2001)
5/2/13 3:27:27.425 PM WindowServer[98]: Created shield window 0xe0 for display 0x003f003d
5/2/13 3:27:27.425 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a16860(2000), shield 0x7ff108c72820(2001), lock state 3
5/2/13 3:27:27.426 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:27:27.426 PM WindowServer[98]: Created shield window 0xe1 for display 0x003f003e
5/2/13 3:27:27.426 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a16860(2002), shield 0x7ff108c72820(2001), lock state 3
5/2/13 3:27:27.427 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:27:27.429 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a16860(2002), shield 0x7ff108c72820(2001), lock state 3
5/2/13 3:27:27.429 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:27:37.970 PM com.apple.kextcache[5590]: / locked; waiting for lock.
5/2/13 3:27:38.330 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 3:27:40.629 PM com.apple.kextcache[5590]: Lock acquired; proceeding.
5/2/13 3:27:40.708 PM com.apple.kextcache[5590]: /: helper partitions appear up to date.
5/2/13 3:37:36.220 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 3:37:36.221 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 3:37:36.221 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 3:37:36.221 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 3:37:36.221 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 3:37:36.364 PM WindowServer[98]: Created shield window 0xe5 for display 0x042733c0
5/2/13 3:37:36.365 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff10e51bcd0(2000), shield 0x7ff109912780(2001)
5/2/13 3:37:36.431 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff10e51bcd0(2000), shield 0x7ff109912780(2001)
5/2/13 3:40:14.563 PM com.apple.launchd[1]: (com.adobe.fpsaud[5640]) Exited with code: 210
5/2/13 3:40:55.906 PM AddressBookSourceSync[5645]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7f93bed03090 {NSUnderlyingError=0x7f93bc84b860 "Could not connect to the server.", NSErrorFailingURLStringKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSErrorFailingURLKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSLocalizedDescription=Could not connect to the server.}
5/2/13 3:42:52.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1367527374
5/2/13 3:49:39.031 PM WindowServer[98]: Created shield window 0xe6 for display 0x003f003d
5/2/13 3:49:39.032 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff10e51bcd0(2000), shield 0x7ff109912780(2001), lock state 3
5/2/13 3:49:39.032 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:49:39.033 PM WindowServer[98]: Created shield window 0xe7 for display 0x003f003e
5/2/13 3:49:39.033 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff10e51bcd0(2002), shield 0x7ff109912780(2001), lock state 3
5/2/13 3:49:39.034 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:49:39.036 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff10e51bcd0(2002), shield 0x7ff109912780(2001), lock state 3
5/2/13 3:49:39.036 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 3:49:44.847 PM com.apple.kextcache[5655]: rebuilding /System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey
5/2/13 3:49:44.925 PM com.apple.kextcache[5655]: /System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey not cached.
5/2/13 3:49:45.082 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 3:49:46.177 PM com.apple.kextcache[5655]: Successfully updated disk0s3.
5/2/13 3:56:41.106 PM com.apple.backupd[5332]: Copied 915.6 MB of 1.96 GB, 621 of 621 items
5/2/13 4:00:50.828 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 4:00:50.829 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:00:50.829 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 4:00:50.829 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:00:50.829 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 4:00:50.961 PM WindowServer[98]: Created shield window 0xf6 for display 0x042733c0
5/2/13 4:00:50.961 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff108c88910(2000), shield 0x7ff109a39f00(2001)
5/2/13 4:00:51.026 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff108c88910(2000), shield 0x7ff109a39f00(2001)
5/2/13 4:06:22.334 PM WindowServer[98]: Created shield window 0xf7 for display 0x003f003d
5/2/13 4:06:22.334 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff108c88910(2000), shield 0x7ff109a39f00(2001), lock state 3
5/2/13 4:06:22.334 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:06:22.335 PM WindowServer[98]: Created shield window 0xf8 for display 0x003f003e
5/2/13 4:06:22.336 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff108c88910(2002), shield 0x7ff109a39f00(2001), lock state 3
5/2/13 4:06:22.336 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:06:22.338 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff108c88910(2002), shield 0x7ff109a39f00(2001), lock state 3
5/2/13 4:06:22.338 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:06:30.205 PM com.apple.kextcache[5693]: / locked; waiting for lock.
5/2/13 4:06:30.576 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 4:06:31.119 PM com.apple.kextcache[5693]: Lock acquired; proceeding.
5/2/13 4:06:31.214 PM com.apple.kextcache[5693]: /: helper partitions appear up to date.
5/2/13 4:16:28.132 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 4:16:28.133 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:16:28.133 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 4:16:28.133 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:16:28.133 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 4:16:28.272 PM WindowServer[98]: Created shield window 0xfc for display 0x042733c0
5/2/13 4:16:28.272 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001)
5/2/13 4:16:28.337 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001)
5/2/13 4:39:00.173 PM WindowServer[98]: Created shield window 0xfd for display 0x003f003d
5/2/13 4:39:00.173 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2000), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 4:39:00.174 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:39:00.175 PM WindowServer[98]: Created shield window 0xfe for display 0x003f003e
5/2/13 4:39:00.175 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 4:39:00.175 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:39:00.178 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109c3e600(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 4:39:00.178 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 4:39:07.759 PM com.apple.kextcache[5745]: / locked; waiting for lock.
5/2/13 4:39:08.118 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 4:39:08.760 PM com.apple.kextcache[5745]: Lock acquired; proceeding.
5/2/13 4:39:08.865 PM com.apple.kextcache[5745]: /: helper partitions appear up to date.
5/2/13 4:40:14.400 PM locationd[5777]: NOTICE,Location icon should now be in state 0
5/2/13 4:40:14.467 PM com.apple.launchd[1]: (com.adobe.fpsaud[5776]) Exited with code: 210
5/2/13 4:40:20.480 PM com.apple.launchd[1]: (com.apple.xprotectupdater[5780]) Exited with code: 252
5/2/13 4:40:55.752 PM AddressBookSourceSync[5790]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7feb30c6ee10 {NSUnderlyingError=0x7feb3225f6b0 "Could not connect to the server.", NSErrorFailingURLStringKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSErrorFailingURLKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSLocalizedDescription=Could not connect to the server.}
5/2/13 4:43:52.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1367531034
5/2/13 4:49:05.971 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 4:49:05.972 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:49:05.972 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 4:49:05.972 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 4:49:05.972 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 4:49:06.118 PM WindowServer[98]: Created shield window 0x102 for display 0x042733c0
5/2/13 4:49:06.124 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109a62a80(2000), shield 0x7ff108ca6e10(2001)
5/2/13 4:49:06.190 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109a62a80(2000), shield 0x7ff108ca6e10(2001)
5/2/13 4:58:11.909 PM com.apple.backupd[5332]: Copied 1.42 GB of 1.96 GB, 621 of 621 items
5/2/13 5:07:09.291 PM WindowServer[98]: Created shield window 0x103 for display 0x003f003d
5/2/13 5:07:09.291 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a62a80(2000), shield 0x7ff108ca6e10(2001), lock state 3
5/2/13 5:07:09.292 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 5:07:09.293 PM WindowServer[98]: Created shield window 0x104 for display 0x003f003e
5/2/13 5:07:09.293 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a62a80(2002), shield 0x7ff108ca6e10(2001), lock state 3
5/2/13 5:07:09.293 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 5:07:09.296 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109a62a80(2002), shield 0x7ff108ca6e10(2001), lock state 3
5/2/13 5:07:09.296 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 5:07:16.177 PM com.apple.kextcache[5813]: / locked; waiting for lock.
5/2/13 5:07:16.550 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 5:07:21.480 PM com.apple.kextcache[5838]: / locked; waiting for lock.
5/2/13 5:07:27.137 PM com.apple.kextcache[5813]: Lock acquired; proceeding.
5/2/13 5:07:27.220 PM com.apple.kextcache[5813]: /: helper partitions appear up to date.
5/2/13 5:07:27.221 PM com.apple.kextcache[5838]: Lock acquired; proceeding.
5/2/13 5:07:27.303 PM com.apple.kextcache[5838]: /: helper partitions appear up to date.
5/2/13 5:17:14.090 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 5:17:14.091 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 5:17:14.091 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 5:17:14.091 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 5:17:14.091 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 5:17:14.232 PM WindowServer[98]: Created shield window 0x108 for display 0x042733c0
5/2/13 5:17:14.238 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109b01ae0(2000), shield 0x7ff109ca9440(2001)
5/2/13 5:17:14.305 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109b01ae0(2000), shield 0x7ff109ca9440(2001)
5/2/13 5:17:14.000 PM kernel[0]: (default pager): [KERNEL]: ps_allocate_cluster - send HI_WAT_ALERT
5/2/13 5:17:14.000 PM kernel[0]: macx_swapon SUCCESS
5/2/13 5:40:14.658 PM com.apple.launchd[1]: (com.adobe.fpsaud[5878]) Exited with code: 210
5/2/13 5:40:55.690 PM AddressBookSourceSync[5884]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7ff8194cfa60 {NSUnderlyingError=0x7ff81a303760 "Could not connect to the server.", NSErrorFailingURLStringKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSErrorFailingURLKey=https://XuserX%[email protected]/principals/users/XuserX///XuserX%[email protected]/principals/users/XuserX/, NSLocalizedDescription=Could not connect to the server.}
5/2/13 5:44:52.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1367534694
5/2/13 5:59:41.130 PM com.apple.backupd[5332]: Copied 1.89 GB of 1.96 GB, 621 of 621 items
5/2/13 6:06:14.273 PM WindowServer[98]: Created shield window 0x109 for display 0x003f003d
5/2/13 6:06:14.273 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109b01ae0(2000), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 6:06:14.274 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 6:06:14.275 PM WindowServer[98]: Created shield window 0x10a for display 0x003f003e
5/2/13 6:06:14.275 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109b01ae0(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 6:06:14.275 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 6:06:14.278 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7ff109b01ae0(2002), shield 0x7ff109ca9440(2001), lock state 3
5/2/13 6:06:14.278 PM WindowServer[98]: handle_will_sleep_auth_and_shield_windows: err 0x0
5/2/13 6:06:20.005 PM com.apple.kextcache[5897]: / locked; waiting for lock.
5/2/13 6:06:20.381 PM fseventsd[61]: Logging disabled completely for device:1: /Volumes/Recovery HD
5/2/13 6:06:21.051 PM com.apple.kextcache[5897]: Lock acquired; proceeding.
5/2/13 6:06:21.153 PM com.apple.kextcache[5897]: /: helper partitions appear up to date.
5/2/13 6:14:44.788 PM com.apple.backupd[5332]: Copied 2381 files (1.96 GB) from volume Bugs.
5/2/13 6:14:46.209 PM com.apple.backupd[5332]: Using file event preflight for Bugs
5/2/13 6:14:46.374 PM com.apple.backupd[5332]: Will copy (1.3 MB) from Bugs
5/2/13 6:14:46.381 PM com.apple.backupd[5332]: Found 75 files (1.3 MB) needing backup
5/2/13 6:14:46.382 PM com.apple.backupd[5332]: 3.29 GB required (including padding), 21.39 GB available
5/2/13 6:16:18.079 PM WindowServer[98]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/2/13 6:16:18.080 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 6:16:18.080 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
5/2/13 6:16:18.080 PM loginwindow[55]: find_shared_window: WID -1
5/2/13 6:16:18.081 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
5/2/13 6:16:18.394 PM WindowServer[98]: Created shield window 0x10e for display 0x042733c0
5/2/13 6:16:18.394 PM WindowServer[98]: device_generate_desktop_screenshot: authw 0x7ff109a1ecd0(2000), shield 0x7ff109912780(2001)
5/2/13 6:16:18.468 PM WindowServer[98]: device_generate_lock_screen_screenshot: authw 0x7ff109a1ecd0(2000), shield 0x7ff109912780(2001)
5/2/13 6:22:08.798 PM com.apple.backupd[5332]: Copied 2515 files (1.3 MB) from volume Bugs.
5/2/13 6:22:12.499 PM com.apple.backupd[5332]: Created new backup: 2013-05-02-182211
5/2/13 6:22:19.152 PM com.apple.backupd[5332]: Starting post-backup thinning
5/2/13 6:22:19.152 PM com.apple.backupd[5332]: No post-back up thinning needed: no expired backups exist
5/2/13 6:23:08.248 PM com.apple.backupd[5332]: Backup completed successfully.
5/2/13 6:23:22.829 PM com.apple.backupd[5332]: Ejected Time Machine disk image: /Volumes/syrinx3/bugs.sparsebundle
5/2/13 6:23:23.000 PM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/syrinx3, flags 0, pid 5970
5/2/13 6:23:23.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/syrinx3 0xffffff80f9811008
5/2/13 6:23:23.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/syrinx3 0xffffff80f9811008
5/2/13 6:23:23.000 PM kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
5/2/13 6:23:23.359 PM com.apple.backupd[5332]: Ejected Time Machine network volume.
5/2/13 6:30:32.617 PM AppleIDAuthAgent[488]: SERVER AppleIDAuth: Creating CSR for "gr...en@?????.???". (__AppleIDDoCreateCertificateRequestForAppleID()/AppleIDAuthenticationImpl.cpp #480) accountCheckDispatch
5/2/13 6:40:14.428 PM com.apple.launchd[1]: (com.adobe.fpsaud[5991]) Exited with code: 210
5/2/13 6:40:52.551 PM com.apple.backupd[6000]: Starting automatic backup

How can I close my Time Machine Sparsebundle so Time Capsule can do a scheduled backup?

"Time Machine couldn't complete the backup to "Your Time Capsule". The backup disk image “/Volumes/Steven Weinberg's Time Caps-1/Steven Weinberg’s MacBook Pro (4).sparsebundle” is already in use."
I have both a Time Capsule and a 2Tb external drive using Time Machine to back up my laptop.
Is it as simple as when the Time Capsule goes to do a backup and finds that the other drive is in the midst of using Time Machine to do its backup that I get this notice on my desktop?
It's 10:30 AM now. The last Time Capsule backup was almost 12 hours ago.
There have already been 6 Time Machine backups today on the 2nd drive.
Sounds like the Time Capsule really is being blocked from doing its job.
THe 1 Tb Time Capsule backs up to a .sparsebundle document which fills the Time Capsule at 985 Gb. You can't open and peek inside the .sparsebundle backup file.
The other drive backs up to a .backupdb folder within which are subfolders for each backup which appears to be a complete recreation of thebacked-up 500 Gb hard drive on my MacBook Pro laptop. And even though there are 37 separate folders with backups going back to Sept 2013 when I installed the second backup drive, it's only used about 500 Gb of its 2 Tb capacity.
1. How can I solve my primary problem of freeing up the .sparsebundle file for the Time Capsule?
2. Since both drives are using Time Machine to do the backup, why are they producing such diffrent backup file structures?
Steve

David Bean wrote:
So copying from a one-week-old TM volume was failing
Have you run Repair Disk on it?
I now realize that the folder in which the problem file(s) are stored on the backup,.DocumentRevisions-V100, is the folder in which OS X stores its versioning data for all users. I am now trying to work out whether I can safely delete these files from the backup
That does get damaged on occasion. I haven't seen it in quite a while, so it's pretty rare.
You can delete it from the backups, via the TM interface, but you must be able to show invisible items).
First, open the Terminal app (in your Applications/Utilities folder). Be very careful with this app. It's a direct link into UNIX, the underpinnings of OSX, but without the protections of OSX.
In Terminal, the prompt looks like this: <Computer Name>:~ <your name>$
(where <your name> is your short user name). It's followed by a non-blinking block cursor.
Copy, do not type, the following after the prompt:
defaults write com.apple.finder AppleShowAllFiles 1
and press Return.
You should just see the prompt again.
Then see Time Machine - Frequently Asked Question #12 to delete all the backups of it.
and from the live system filestore so they don't get copied out to a backup again.
Yes. You will, of course, lose all previous versions, but since the file is corrupted, you may have lost some, most, or all of them already.
When done, run the same command to hide the invisible items, but replace the "1" with a zero.

Lion Server Time Machine sparsebundles

Subject indicates where I think my problem lies, but for background:
MacBook Pro got bit by Thunderbolt firmware upgrade snafu last week. Contacted Apple Store the next morning, saw Genius at 11:00. Concuded hardware and firmware were OK and because I had a Time Machine backup less than an hour old I gave permission to install a fresh 10.7.3 image on my bare metal.
Got home and booted Command-R. Happily saw my Time Machine shares on Mac Mini Server running Lion Server 10.7.4. Yes, "shares." A Backup and Backup-1.
As a Lion Server novice I found a tip here to "defaults write /private/var/db/dslocal/nodes/Default/sharepoints/Backups timeMachineBackup '(1)' to make my shared mountpoint work with Time Machine over the network. Perhaps thats how one does it if one doesn't have Server. I later found the Time Machine panel in Server and turning that on gave me a Backups-1 share as well.
So back with Command-R my MacBook Pro saw both the Backups and Backups-1, I navigated to Backups and it saw its previous Time Machine archive. I started a bare metal restore and happily went to bed. Next morning found the restore stopped at about 20% of the progress bar and message instructing me to reboot the computer. Repeated, same results.
Back to Command-R I reinstalled a new copy of Lion from Apple over the internet. Did minimal configuration until I could get into Time Machine and try to manually pull files. Again it quit unexpectedly no matter holding the Option key to Verify Backups passed.
So back to the Mac Mini Server I turn off Sharing from System Preferences and Time Machine from Server. The /private/var/db/dslocal/nodes/Default/sharepoints/Backups file disappears when Server Time Machine is turned off.
I have attempted to move "David Kelly's MacBook Pro.sparsebundle" from "/Volumes/Macintosh HD2/Backups" to "/Volumes/Macintosh HD2/Shared Items/Backups" where Server Time Machine seems to expect it. The problem now is that the MacBook Pro doesn't see this Time Machine archive in that location, or see it at all.
I have performed the Disk Utility verify tasks listed in the Time Machine FAQ with no errors found or repaired.
I have seen a -6584 error this week but don't remember exactly when: https://discussions.apple.com/thread/3123920?start=0&tstart=0
How can I get the sparsebundle back under Time Machine Server?

Finally figured it out on my own 2 weeks later.
You have to open the Lion Server app and then turn on Time Machine on the server.
It will then ask what disk you want to use, which in my case was an external 2tb USB.
My confusion was that this is not they way you had to do it on Snow Leopard Server.
On SLS, I never used Time Machine, but had to partition my external disk individually for each user. e.g. 2tb disk was partioned into 4 separate volumes. This was necessary to keep one user's Time Machine backup from taking up the whole disk and not leaving room for the other users.
You then setup these partitions as Time Machine Sharepoint which would then show up as a choice on the users machine under Time Machine preferences, select disks.
Therefore, under SLS, a user could select from any number of partions to backup to on the server. On Lion Server, it appears you do not have a choice and can only backup to the one disk you selected on the Server App.
At the risk of carrying on a conversation with myself online, my concern is now about limiting the size of the individual user's sparse bundle to again keep one user from taking up the entire disk for their Time Machine. I guess that is another fight for another day.

Migrate Time Machine .sparsebundle to DAS

I'm trying to migrate my .sparsebundle off of a 3rd party NAS onto a new Thunderbold DAS but I can't seem to find any documentation to describe how to go about doing this.
Right now, I've mounted the .sparsebundle and I'm doing a Disk Utility restore from it to the new DAS (prompted me to erase the destination as a result). This process seems to want to take one full day by way of the Disk Utility time counter.
Is this the most efficient, fastest way to do it? It only took 5 hours to copy the 800GB sparsebundle over to it's temporary home, so I'm unsure why the restore wants to take 5x longer to complete, unless I'm doing this the hard way. I notice that it seems to be doing a block copy . Would this account for the increase in expected completion time?
Thanks in advance.

There is a way to force the backup history to be inherited, but I consider it too complicated for most users to carry out, and it won't do any good if you've already started using Time Machine with the new setup. If you're familiar with the shell and want to try it, search the tmutil(8) manual page for the terms "inheritbackup" and "associatedisk."
Otherwise I suggest you set the backup drive aside and stop using it until you're sure you'll no longer need the data. Then erase it and start over. Meanwhile, start a new backup on another drive. You need more than one backup to be safe anyway.

Moving Time Machine sparsebundle to new backup drive

Hi all,
This may be a bit of a unique situation, but hopefully I can get some guidance...
I've been backing up two different computers using Time Machine, with the backups stored on a hard drive attached to a third computer (an old MacBook) that's set up as a server. So the backup drive has had two different sparsebundle files, one for each computer.
That drive filled up, so I've recently purchased a larger one. To keep things a little cleaner and to keep the larger computer's backup from crowding out the other one, I've decided to put the TM backups in two separate partitions on the new drive. I set up the partitions in what is hopefully the correct way based on some other discussions I've read (Mac OS-Extended, case sensitive, journaled; partition map scheme: GUID Partition Table).
However, I couldn't find any tips on how best to transfer over the old TM sparsebundles to keep using them on the new drive. SuperDuper probably wouldn't work since I only want to copy one of the sparsebundles into each of the partitions, not duplicate the existing drive.
So I'm hoping I can just copy them over manually using the Finder (that's what I'm doing now — and will be for the next 5 hours or so). Once it's done I'm planning to point the TM Preferences at the new partition and hope that it recognizes the existing backup. (If that fails, I'll mount the sparsebundle first.)
In the meantime, I just wanted to confirm that this is the correct way to go, and see if there are any other factors I need to take into consideration.
Thanks!

maxfreund wrote:
Thanks! Your timing is perfect -- I was just looking at Pondini's FAQ on exactly my situation:
http://web.me.com/pondini/Time_Machine/18.html
This would seem to confirm that I'm on the right track. I guess I'll know for sure in around 5 hours!
Always a Good Read...
Let us know how it goes...

How do I copy old Time Machine back-up data onto my new (second) back up drive?

I recently bought a second back-up drive for use with my MacBook Pro (running 10.9.4).
I'm successfully backing up my computer to both drives on a regular basis using Time Machine. (a Seagate drive and a Western Digital drive respectively)
I was wondering if there's an easy way to add the old back-up files from the old drive to the new drive as well. That is to say, I wish I had all the data that precedes my new back-up drive on BOTH drives. There's plenty of space on the new drive.
Again, I'm already running Time Machine successfully to both drives, is it perhaps as easy as connecting both drives to my computer and copying the older dated back-up files over to the newer drive within the Backups.backupdb folder for my profile?
Thanks for any help!

Although the documentation says you can copy Time Machine backups in the Finder, it's very slow and sometimes doesn't work at all.
This technique will only work if the volume you're copying to is the same size, or larger than, the one you're copying from.
First, open the Time Machine preference pane and click the Options button. You may have to unlock the settings first by clicking the padlock icon in the lower left corner of the window. Authenticate as an administrator.
Delete the volume you're going to copy from the list of backup destinations. Then turn Time Machine OFF.
Launch Disk Utility, open the built-in help, and search for the term "Duplicate." Follow the instructions. All existing data on the destination volume will be erased.
If the volume you're copying was encrypted by Time Machine, you may have to unlock it first. Click the Unlock button in the toolbar of the Disk Utility window.
Turn Time Machine back ON and select the new volume as a backup destination. You can also continue to use the old volume, if you wish. The two will be alternated when both are available.
CAUTION: If the volume you're copying is corrupt, as shown by Repair Disk or Verify Disk in Disk Utility, then that corruption will be copied to the new drive. Don't copy data from a corrupt volume on a malfunctioning drive. Put the drive aside and don't use it until you're sure you'll no longer need the data. Then securely erase it and take it to a recycling center. Do the same if the Restore operation fails with "disk errors."

Reinstall using installer copied from Time Machine.

I was worried about viruses and installed Avira free anti-virus. It messed up a few things (unmounting USB drives and more) so I uninstalled it. However, OS X 10.10 and Safari still seem slow and flakey. I have the installer copied from a Time Machine disk. Can I just copy this into the Application folder, run it and reinstall everything? Has anyone tried this?
Stephenscribe.

Easier would be to simply restart in recovery mode, by holding down command-R at startup, and reinstall that way.
That will require re-downloading, however... if you're trying to avoid that, you can turn the backed-up installer into a bootable install disk:
Create a bootable installer for OS X Mavericks or Yosemite - Apple Support

Slow copying a Time Machine sparsebundle

Similar Messages

Maybe you are looking for