What Should be on Time Machine Drive?

I decided to look at what I had on the drive I have for Time Machine and noticed that there is a folder called Backups.backupdb and then a copy of my computer (i.e. applications folder, library folder). I thought that was sort of strange and it clicked that Time Machine in system prefs claims that only 11 GB are left on the TM drive, when i dont know how that is possible because my TM drive is a 232.57 DB drive and my internal drive is 185.99 drive. Should i delete everything off my TM drive except that backup folder? I know my dad backed up my computer when i was away over winter break but I thought it was to another drive, not this one.

You're welcome, and thank you for the !
Have fun!

Similar Messages

What happens when the Time Machine drive is full?

I'm on my second iMac. My first one (G5, 1984) died, and I replaced it early 2010 with an Intel mac. The transition when exceedingly well largely due to Time Machine. I just hooked the Time Machine drive to the new system, and I was soon back up running!
My home folder has 70GB of data. The Macintosh drive has 105GB of data and 395GB free. The Time Machine drive has 220GB used and 30GB free.
1. What happens when the Time Machine drive is full?
2. Do I have control over what backups get deleted?
3. If lightning strikes twice, will I still be able to restore my Intel mac like my G5 mac, even if backups get deleted?
4. Is there anyway to control what backups/backup files get deleted?
5. Any other thoughts?
Thanks.

maxseven wrote:
i have deleted the time machine folders and they are now in my trash. when i try to secure empty my trash it will delete everything but the t/m folders. how do i delete them?
Do you mean all of them? The entire Backups.backupdb folder?
That's a large mess. First, even a normal delete will take a very long time, as there are probably hundreds of thousands, or even millions, of files. Your best bet by far is to simply erase them with Disk Utility -- that will only take a few moments. If your TM drive has a single partition, see #1 in [Formatting, Partitioning, Verifying, and Repairing Disks|http://web.me.com/pondini/AppleTips/DU.html]. If there are other partition(s) on the drive, see #2 there.
If not, and you only deleted some of the folders, you have a different, worse problem. Unfortunately, Apple doesn't do a very good job of warning folks: +*Never move, change, or delete anything in your backups via the Finder or Terminal.+*
You shouldn't have to delete backups at all, since Time Machine will do that automatically when the disk/partition gets full. But you can do it without harm via Time Machine. See #12 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
A normal delete will take a very long time, as there are probably tens or hundreds of thousands of items, each of which must be individually deleted. A secure delete will take much, much longer, as each deleted file must be overwritten with zeros.

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?

Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
Quit and you should be able to install OS X now with your Apple ID and password.
see
http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/

New Hard Drive- Should I use Time Machine for "fresh" install?

I have a first generation Early 2008 MacbookPro. Warranty just ended and I want to replace the hard drive w/ the Seagate Momentus XT Hybrid. I'm getting a bunch of spin wheel action and things are just running slowly/sluggish. I'm questioning whether or not I should just do a real "fresh" install and load my applications onto the new drive or use TimeMachine. If I use TM am I not adding all the stuff/files that are not needed? Am I adding bloat that I've collected over the past couple of years? Is it better to start w/ a new clean operating system? I do have CS5 and some photo programs that I think I can reinstall. Anyway I wanted to get people's perspective.
Message was edited by: mikked

It's usually best to clean your system up, and deal with any problems before doing major surgery.
With any other scenario, if something goes wrong, how will you know what it was, much less how to fix it?
I'd start with this: [Intel-based Macs: Using Apple Hardware Test|http://support.apple.com/kb/HT1509].
Then Verify your internal HD, and repair your Time Machine drive, 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).
Then run a +*Repair Permissions+* on your internal HD, via Disk Utility.
Then replace the drive, do a full system restore and run for a while to be sure the new drive and everything else is ok. See #14 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum), for details.
Then start deleting the apps and files you don't need.
Note that, unlike Windoze, leftover files and apps may take up a bit of space, but don't cause any performace problems, unless they're actually running.
The main problems with trying to transfer things selectively are:
Permissions. If you install OSX and set up a user account, that account, even if it has the same name, may not have permission to restore the files on your backups or other drives.
Applications. Simple apps can be transferred individually, such as by restoring from Time Machine. Complex ones usually can't, as their installers put other files in other places. If you don't know what and where they all are, and restore them, too, the app won't work properly, if at all. But if you have all the original discs (and serial numbers/purchase keys), you can just reinstall them.

HT201250 How long should an initial time machine backup of tack for 675 GB?s with a USB external hard drive?

How long should an initial time machine backup of tack for 675 GB?s with a USB external hard drive?

Not much faster than 40 GBs-60GBs per hour. So, minimally, around 12 hours.

Lost the ability to Spotlight Index my Time Machine drive

I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
So I've run out of things to try.
Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
--Bob

Well unfortunately the command
sudo mdutil -E /Volumes/MyDiskName
didn't help.
The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
However, this time there were console messages and a crash report.
The Console shows (with personal information x'ed out):
12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
The Crash Report reads as follows (again with personal information x'ed out):
Process: mds [28]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2007-12-31 13:30:38.746 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
Crashed Thread: 15
Thread 0:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
2 mds 0x00009648 0x1000 + 34376
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x92f15438 kevent + 12
1 mds 0x0007e584 0x1000 + 513412
Thread 9:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 Crashed:
0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
13 com.apple.spotlight.index 0x0016529c runLoop + 72
14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 crashed with PPC Thread State 32:
srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
vrsave: 0x00000000
Binary Images:
0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
Any suggestions before I just Erase the disk and start over with a new backup?
--Bob

I have an external Time Machine drive that I want to reformat. I can't remember the password. How can I do this. Disk Utility won't let me. Thanks.

I have an iMac that had drive problems last winter. Took the iMac to the Apple Store and they reinstalled everything and now it works again. Only thing is that my external Time Machine drive is screwed up now. Its 1.5 TB.
I had the Time Machine drive partioned into two parts. One partion was for an emergency bootup using carbon copy cloner. That partion I can open and mounts on my desktop. The other partion was Time Machine. It once upon a time opened and mounted without a password.
It requests a password to unlock even though I never had it password protected before the iMac drive problems. And so now it won't mount the drive.
I can go to Disk Utilities and I can see Time Machine with both partions. The Carbon Copy partion is mounted. The Time Machine partion is not mounted. For this reason I can't select it and erase it.
What the heck am I supposed ot do now to erase it and start over. Any help would be appreciated. I really don't want to go and buy another drive.
Kevin

Triple-click anywhere in the line below to select it:
{ diskutil list; echo; diskutil cs list; } | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
If any personal information appears in the output, anonymize before posting, but don’t remove the context.

External time machine drive no longer being automatically recognized

Recently my RMBP has stopped recognizing my external time machine drive. When ever I connect my 1 TB WD drive to my mac, it shows up on my desktop as usually but will not get recognized by time machine. I used to be able to connect the drive, have it show up on my desk with the orange USB logo, and then it would be auto recognized and the time machine logo would appear on it and it would start backing up. Now, I connect it and it just stays at the orange USB logo. I have to go to the time machine menu bar icon and open time machine's preferences and manually select the drive to get it to back up. This happens both on battery power and while I'm charging. I have already verified the disk in disk utility and have repaired as well. I don't recall when this started happening. I was running the 10.9.4 beta before its public release, but it hadn't been working before I upgraded to that either.

This simple procedure will clear your Time Machine settings, including exclusions. The backups won't be affected. If you have a long exclusion list that can't be recreated easily, you may prefer a more complicated procedure that preserves the exclusion list. In that case, ask for instructions. Otherwise, do as follows.
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/com.apple.TimeMachine.plist
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A Finder window should open with a file selected. Copy the file to the Desktop. Then move it (the original, not the copy) to the Trash. You'll be prompted for your administrator password. Restart the computer and recreate your settings in the Time Machine preference pane. It will show that you have no backups. Don't worry; your backups haven't been touched. Run a backup to test. The backup may take much longer than usual. If TM now performs as expected, delete the file you copied to the Desktop.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Can't see time machine drive and can't boot

Last week the internal hd on my Mac mini (mid-2010) began failing. I took it in and AppleCare replaced the drive. The genius told me they loaded 10.7.3 and I should be able to use Time Machine (TM) to bring it all back. So I go home, plug in my TM drive and the Mac can't see the drive the TM is on. And yet I know it recognizes the drive because if I turned it off it would give me the nasty warning about disconnecting before unmounting. So not knowing what to do I went and popped in the installation disc that came with my Mac mini (10.6), and booted with the cd. I told it to restore from TM, and this time it sees my drive and transfers the data. When it restarts I get the gray screen with a null (not permitted) sign. So I can't make heads or tails of it an decide that maybe I have to make a clean install and then upgrade to 10.7.4 and then try time machine (I'm grasping at straws now). Only when I attempt to to restart after installing 10.6 it go from a gray screen to a blue screen (of death) and just sits. I'm baffled and don't know what to do. Could my time machine disk, which was backing up a failing internal HD, have been bad? What do I do?

Hello:
If I were you (and I am not), I would bundle up the repaired computer and your Time Machine drive and take it in and ask the Apple person to bring it back to life. IMHO, that should have been done the first time.
Barry

Should I use Time Machine?

I have a new Western Digital My Passport Essential 320GB external hard drive. I also have an old PowerPC iBook G3, with a 40GB hard drive and a dead logic board. I can still access the iBook's HD by hooking it up to my current MacBook and starting it up in Target Disk mode. My current MacBook has a 120GB hard drive, which is getting full.
This is the first time I've ever used external storage. What I would like to do is:
a) copy the contents of the iBook's HD to the external HD;
b) back up the contents of the MacBook's HD;
c) free up some space on the MacBook's HD.
My questions:
1. Do I need to format the external drive before doing anything? If so, am I right in thinking that I should do this in Disk Utility > Erase, and choose 'Mac OS X Extended (Journaled)'?
2. If I do this, do I need to worry about the files that were already on the drive when it arrived from the manufacturer? (I might keep the User Guide pdf, but everything else seems to be .exe files, or files for which there is no default application specified to open them.)
3. Do I need to create a partition on the external HD for the contents of the old iBook HD?
4. Will Time Machine work on a partitioned external HD?
5. Should I use Time Machine to back up the contents of my MacBook, or do it manually? The things that I'm most concerned to back up are my photographs. However, these are also the files which take up the most room on my MacBook HD (I shoot in RAW - lots of 10MB+ files), so are the obvious candidates for files to keep on the external HD in order to free up space on the MacBook. If I back up using TM, then erase some photos from the MacBook hard drive, will TM then erase them from the external hard drive as well - either immediately or when the external hard drive fills up - or will they be safe forever? Sorry, I'm not entirely clear how TM actually works...
I'm a real novice here. Advice on any or all of the above will be much appreciated.
Michael

GoonInChief wrote:
My questions:
1. Do I need to format the external drive before doing anything? If so, am I right in thinking that I should do this in Disk Utility > Erase, and choose 'Mac OS X Extended (Journaled)'?
If it's not HFS+, it needs to be formatted to HFS+ (Mac OS Extended - Journaled) via Disk Utility. All data will be lost. See Answer 4.
2. If I do this, do I need to worry about the files that were already on the drive when it arrived from the manufacturer? (I might keep the User Guide pdf, but everything else seems to be .exe files, or files for which there is no default application specified to open them.)
If you want to keep the files, copy it to another location.
3. Do I need to create a partition on the external HD for the contents of the old iBook HD?
If you want to.
4. Will Time Machine work on a partitioned external HD?
Yes, but it needs to be formatted HFS+. If you are creating a separate partition, you use a GUID partition map for an Intel iMac (APM for PPC).
5. Should I use Time Machine to back up the contents of my MacBook, or do it manually? The things that I'm most concerned to back up are my photographs. However, these are also the files which take up the most room on my MacBook HD (I shoot in RAW - lots of 10MB+ files), so are the obvious candidates for files to keep on the external HD in order to free up space on the MacBook. If I back up using TM, then erase some photos from the MacBook hard drive, will TM then erase them from the external hard drive as well - either immediately or when the external hard drive fills up - or will they be safe forever? Sorry, I'm not entirely clear how TM actually works...
Absolutely NOT! TM is not for archiving. You delete files are NOT safe forever.

WD World Edition 1TB as a Time Machine drive with Mac and XP?

I plan on buying a WD World Edition 1TB to use as my Time Machine drive over wireless netowrk at home for my 320GB MBP.
My wife has a Windows XP PC so I would like to partition the 1TB into maybe 600MB for me and 400MB for her.
First of all, will this type of partition work with TM and also, what format should the WD Drive be? I have installed MacFuse and NTFS-3G on my MBP.
Any info from someone who does something simalr would be greatly appreciated.
Dave

That sounds fine.
So in theory, the WD comes with no partitions so I could set the whole thing up on the XP machine and set the partition sizes, then go the Mac, connect to the partition I've set aside for myself and select it, at which point the Mac will format it to HFS and start backing up?
You say the Mac is oblivious to partitions so what would stop it formatting the entire drive to HFS?
Ideally I'd like to get the WD software to backup the XP machine to the XP partition and TM to backup the Mac to the HFS partition. Do you know if this is likely to work? Hopefuilly someone with this drive will be able to answer as well.
Thanks for your help so far

Time Machine drive continually gets compromised

More that one external Time Machine drive loses the ability to create folder due to what appears to be a drive issue. Disk Utility reports the following:
Incorrect number of extended attributes
(It should be 936186 instead of 936185)
Incorrect number of Access Control Lists
(It should be 936184 instead of 936183)
Time Machine works for a while after restart or disk repair. Have used different Time Machine drives, different boot drives, reset Time Machine, reformatted Time Machine drives.Time Machine drives formatted GUID OS Extended (Journaled). All the Time Machine drives work fine on my older 2ghz Mac Mini running. OS 10.5.8. What am I missing?

Hi, and welcome to the forums.
Something is corrupting the file system. Are you careful to eject it before disconnecting? Any power failures while it's connected?
Make sure all connections are snug and secure; try different port(s) and cables, and combinations -- a plug that works fine in one port may not quite make a good connection in another.
Some drives that worked with Leopard need driver or firmware updates to work with Snow Leopard. Check with the maker to see if they have updates for yours (especially if they're all the same make).
Verify the internal HD, just to be sure something there isn't corrupted.
If nothing else helps, it could be a problem with your installation of OSX. I'd suggest downloading and installing the 10.6.4 "combo" update. That's the cleverly-named combination of all the updates to Snow Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards. Don't delete the download yet, though.
If that doesn't help, reinstall OSX from your Snow Leopard Install disc (that won't affect anything else), then apply the "combo" again.

What to do when time machine seems stuck on "Preparing Backup"

This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help.

Comments inline below.
Pondini wrote:
joshua raphael wrote:
This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
You may want to revisit that strategy:
A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version. But you can't do that from that backup.
Indeed!
Backing-up apps that way will also be useless in some cases. 3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well). Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
I think you're confusing each other with terminology. iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X. "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders. This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
I have tried reparing the disk using disk utility, but that didn't help.
Disk Utility changed a bit in Lion. When you select an entire disk, it only repairs the partition map, not all the volumes. You must repair each one separately.
Wow, good to know. (What a stupid change to make, for backwards compatibility, if for no other reason!)
See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
Whew. This editor makes it so hard to make comments inline. The key thing when time machine seems stuck is patience. Sometimes it needs to be left to run overnight. Unfortunately, it doesn't log or report it's progress very well.
Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress. And even so, there is very little logging indicating progress.
sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
The parts in italics will need to be adjusted. Tab completion makes this easy, e.g type
sudo tail -f /Volumes/
and hit tab, type the first few letters of the relevant volume name, hit tab...
Also, I have a hypothesis which needs testing.
I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been. I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working. After thinning the volume, it started working again.

How do we regain control over our Time Machine drive revisited

+I posted this question as two posts over in the+ *Intel-based iMac* +forum but I think I may have put it in the wrong place. Please forgive me if you've already read this over there. If someone tells me how to delete a post I will or perhaps a Moderator can/will do it for me.+
+O M Oz+
Recently our 2.66 Intel Core 2 Duo started into a cycle of rebooting itself during the startup sequence. Eventually we decided to Restore the disk from the Time Machine Backup which is kept on an external 1TB La Cie drive.
After the Restore was complete; Time Machine attempted to do a backup run but we got an error message saying the drive could not be accessed to write the backup. Only the very last backup could be seen from the Star Wars screen. The icon had changed to the generic usb drive icon with a padlock.
I attempted a Full Reset of Time Machine by deleting the Preferences as described in the Troubleshooting thread. Since then we have not been able to access the Time Machine drive at all with either Time Machine or Finder.
A check of Sharing and Permissions shows that all users are listed having custom access which seems to mean you cannot read or write the drive. Disk Utility reports the drive as seeming to be okay when run in either Verify or Repair modes.
I have also attempted to run the sudo command from Terminal with no success. I'm running out of ideas. I don't want to do a low level reformat of this drive yet because it IS a backup drive and I'm not clear on the status of the restored drive.
*Next Day after sleeping on it, I posted...*
I've been thinking it over carefully and think I might have done the damage myself.
Before things went pear shaped I needed to back up the 80GB Hard Drive for a laptop but was just a little short of space on the 1TB drive. In Finder I went into the backup.backup folder and deleted the oldest backup under Finder.
From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
If I am right can I recover from this and still save the the older backups?
Old Mac Oz

I half expected you would be the first to reply, Pondini
Pondini wrote:
Old Mac Oz wrote:
. . . The icon had changed to the generic usb drive icon with a padlock . . .
. . . *we are not able to access* the Time Machine drive at all *with either Time Machine or Finder*. > >. . .From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
Not exactly, but yes, that can damage your backups.
Try to repair them, per #A5 in the Troubleshooting Tip. If that succeeds, your backups are probably ok. If not, It's possible that +Disk Warrior+ can. It's expensive (about $100), and probably a good investment for the future, but there's no guarantee.
I have already tried that but Disk Utility reports that there is nothing wrong with the disk; clearly that is wrong. I cannot reset the permissions to let me (as the Administrator) even read the disk
If that succeeds, and the 80 GB backup from another Mac is still there, you can delete it via Time Machine. See #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
The 80GB backup was a simple Finder copy from the extracted Hard Disk onto my Time Machine disk, just simply regaining Finder access will allow me to rescue that
Also, everything you restored to your internal HD is considered as new, so it must be backed-up again. That will, of course, take a lot of space. It's possible that Time Machine deleted a large number of your old backups to make room. If it didn't, because it couldn't do the backup, it will when it can.
I understand that is what should happen.
So . . . try the repair. If that works, see if the old backups are still there, and also see how much space is available on your TM drive. If there's not enough room for a new full backup of your internal HD, plus 20% for workspace, TM will have to delete some old backups. If the disk isn't well over twice the size of the data it's backing-up, your best bet may be to erase the drive and let Time Machine start fresh.
I am coming to that conclusion. The drive is plenty big enough, it's a Terabyte backing up a 300GB disk. Activity Monitor and Finder using +Get Info+ both tell me the drive has 931.39GB available with about 907GB used, we just cannot access any of the data this usage represents due to the locked permissions.
Since I last posted I have also tried resetting PRAM and running sudo from Terminal as per #C5 in the Troubleshooting Tip to reset the permissions to no avail.
The Restore has not been a success so I am probably going to have to wipe the whole computer and rebuild the system, something I am understandably unwilling to do.
I asked here because the problem seems to be related to a recent Time Machine run and the drive I used. Am I asking my question in the correct forum?
Thanks for your input so far.
Old Man Oz

How can i put music drive AND a time machine drive on wireless network?

Right now I have a MacBook with ONE external drive with my music and movies… and ANOTHERexternal drive for my backups.
I would LOVE to figure out how to hook both the music drive and the time machine drive to a wireless router so the only plug I have for my laptop is the power plug.
I already have a NetGear wireless router… but it only has ethernet ports out, no usb.
What would be the best/easiest way to network these two external hard drives?
tx!

Another option, where you can still utilize your existing drives, is to consider a dedicated NAS device that supports both Time Machine and iTunes functions. One such NAS device is the Synology DS415+. It would be far superior than what you have now. Albeit at an additional cost.

What Should be on Time Machine Drive?

Similar Messages

Maybe you are looking for