Time Machine... seems silly to exclude

I have Time Machine running every day. I'm sure it's fine and thankfully I haven't had to use it yet.
However, it occurred to me that something is simply wrong with a system that doesn't fully list what it's backing up, but lets you exclude by specifying.
I've thought about it pretty hard, and as far as I'm concerned, it makes no sense. I'm sure there's some justification for it, but, then, my kids also had justification for putting perfume and shaving cream all over our rug when they were 5.
IMO, Time Machine should work by having the user specify EXACTLY which volumes, folders, and files it backs up, rather than excluding drives.
The reason I'm trying to get some clarity here is because I have an external drive with some really important stuff. Is it being backed up?
How would I know?
And yes, I've submitted the suggestion. No need to put the link here, thank you.
Cheers,
Andrew

The Blue Chunks wrote:
As an example, what if I have a folder on a network drive I want to back up? I'd like to be able to browse to it and include it.
Like most backup apps, Time Machine cannot back up from a network drive. As MotionMan says, take a look at Chronosync.
Or maybe there's only a single folder on an external drive I want to back up...
Exclude everyitihng else.
As the others have said, Time Machine is designed to back up your entire system. Logically, it's an either/or sort of thing: either specify what you want to back up, or what you don't. Apple has chosen the latter for Time Machine, to make it simple for most users.

Similar Messages

In Lion, Time Machine seems to be perpetually running - and running slowly

Up through Snow Leopard, Time Machine did its incremental backup every hour quickly and stopped.
Since upgrading to Lion back in July, Time Machine seems be be running almost all the time - and very very very slowly. There doesn't seem to be any exessive Spotlight indexing going on anymore. That was long ago. So I don't think that's it.
Preparing for backup takes a long time. It take hours to eke through the backup itself, even if there weren't many changes, and finishing backup takes a long time.
I would say each backup, no matter how small, takes more than three hours.
At these forums there seems to be lots of discussion threads about this, and help pages linked to, but the suggested solutions seem to be a jumble, with some people saying they worked and many saying it didn't.
I did do a disk repair on the Time Machine volume just in case. And there is nothing else on that drive except for Time Machine backups. The drive is directly connected to my iMac (3.06 GHz Dual Core Duo, 12 GB RAM). While not vital, I'd rather not reformat the drive and lost all my old backups, which go back over a year. If I knew for sure that was the solution I'd do it. But in the discussions here there are people who seem to have tried that and reported back that it didn't help.
Right now it says it's backing up 3.5 MB of 132.9 MB - and taking forever to do it.
I know that since the last backup I haven't changed anywhere near 132.9 MB of data. Unless Lion is making massive behind-the-scene changes.
Something definitely seems to be wrong with Time Machine in Lion.
Have there been any additional thoughts on this? Is Time Machine just buggy in Lion?
Thanks,
doug

I feel ya, dawg, as they say. Right now I'm running a backup that has taken 43 minutes thus far. On an idle machine, it backed up 29.8 MB (17,949 files) followed by 19.5 MB (17,256 files). 12 min. for the first batch, 11 min., for the second. 13 min. of "Finishing backup" until it transitioned to "Cleaning up," which just completed after 12 min. Each backup typically goes 70–90 minutes. So backups are running for 65% – 80% of the time, if I leave TM running. I don't; instead, I turn on backups before going to bed, and turn them off on the first happy occasion when I notice that TM is idle.
TM backups have been behaving this way for about 2 months. Before that they were as speedy as Snow Leopard, for a couple of weeks. Before that they were taking 3 hours with the dreaded "Waiting for index to be ready" messge repeating for on hour or more. I fixed this latter problem by "trying everything" from http://pondini.org/TM/D2.html (a fine resource but, as you say, all over the map as all of the suggestions are).
TM in Lion is hosed. It's as simple as that.

Time Machine is listed as excluded folder after migration

I just bought a new iMac and used Time Machine to migrate files and folders over. The first time the new iMac attempted to do a Time Machine backup, I clicked for it to inherit backup history. I just entered Time Machine to look for a file that existed prior to the migration and my backups only go back to the date of the migration, about 2 days ago. However, when I go into Finder and click on Time Machine, it has all of my old backups in folders and I am able to open each folder and see the backups/contents of each day prior to migration. Also, when I click on options in Time Machine System Preferences, it has Time Machine listed as an excluded folder for back up.
How can I get the Time Machine application to recognize the folders saved on the Time Machine external harddrive, i.e., I want to click on Time Machine in the dock and view old backups rather than go into Finder and search the folders for each back up?
Thanks!!

I'm not sure I understand what you mean. The Time Machine volume itself is always excluded from backup. That has nothing to do with what I believe to be your problem, which is that you can't directly access snapshots of your old boot volume where you expect them to be in the time-travel view. That's the subject of the page I linked to.
The snapshots are grayed because they contain no data from your new boot volume. You have to go up to the Computer level, then navigate to the snapshot you want to restore from, and then down to the files.

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.

Time Machine seems to be deleting files from the backup disk.

My main disk has about 400 GB of data including nearly 300 GB of movie files. Since I started using Time Machine in February, the backup disk has had about 400 GB of data on it. This morning Time Machine has said on the System Preferences display that it is "finishing backup" and in the process the backup disk contains only 108 GB of something - hopefully some of my data. The file structure looks OK on the backup disk but I am not sure that the data is there.
I turned Time Machine off and back on and for awhile it seemed to be moving data to the backup disk but then it went back to the "finishing backup" mode and the amount of data on the backup disk began to decrease again. This evening I turned Time Machine off and left it off but it turned itself back on. Somehow this does not seem right. This has happened a number of times.
The net result is that I have about 400GB of data on the iMac system disk and about 108 GB on the backup disk. What can I do to get out of this trap and start getting valid backup?
For starters I will dismount the backup drive and then disconnect the backup drive and at least I will have something left on the disk.
Thanks for the help.

Well, I can't really say what the problem is. You could try to repartition (not just erase) the HD and start Time Machine over again.
Or you could check Time Machine's logs in Console.app, and maybe someone else can help you if it's putting out errors (not my area of expertise).
Message was edited by: bcr88

Time machine seems stuck

During backup, the time machine tries for hours and never completes a backup-- The time machine logo just spins in the menubar. I finally have to force a close. This is for an incremental back up, not the initial back up, so in theory this should be quick. Volume should be light-- 5 music CDs and 25 photos.
How do I get unstuck?
The last successful back up was July 18th.

BavarianWheels wrote:
Thank you for your reply and help...I don't understand what I did, but I tried to do as you suggested and it SEEMED to work fine. The whole thing got backed up, but as this is a macbook pro, I don't want to keep the thing connected to the ext. drive 24/7. I assumed I should just click the 'stop' button and procede to eject the drive, but I rcvd an error message when it stopped that the backup failed...
Yes: if you interrupt a backup, it didn't complete. That's not a successful backup.
So how does one use this TM thing if it runs continually in the background and when you want to eject the backup drive, it fails?? Do I need to make an appt at the genius bar for explanations? It seems there is VERY LITTLE information or documentation on using TM. All I find is "Connect the drive and voila..." It's certainly NOT that easy.
Your first backup copies your entire system. That obviously takes a long time; more in your case because of whatever is/was wrong slowing it down.
But that's only the first one. Once you get a successful, completed backup, subsequent ones are "incremental" -- only what's changed. Ordinarily they should be very quick (especially if you've really solved whatever was slowing down the first one).
I understand that you don't want to be "tied" to the external drive all the time; but the more often you let TM run it's hourly backups, the better you'll be protected.
While it's not a good idea to interrupt a backup, TM will usually recover from it the next time. But until you get a normal completion, they're going to take a while. You'll see a long "preparing" phase in each attempt until then.
You might want to review this: http://www.apple.com/findouthow/mac/#tutorial=leopardtimemachine
and this: http://www.apple.com/macosx/features/timemachine.html
and perhaps this: http://discussions.apple.com/thread.jspa?threadID=1964018

Time Machine seems confused - can somebody explain what I am seeing?

This is on my new MacBook Pro retina 13 inch. And I just started using Time Machine with it about 10 days ago.
I was just looking at a certain folder via Time Machine and found the following strange results, as I "go back in time."
Now: a folder and 3 files (that is correct).
Today at 12:47 pm: 1 file (that is correct, because I created the folder after that, and added the 3 files).
Today at 12:47 pm: no content - why is this entry even here? It's time-stamped the same as the later one.
Today at 11:46 am: a folder and 3 files! The same as "Now." Why would that be? It doesn't make any sense.
Today at 11:45 am: the same folder and 3 files as "Now" - with a time-stamp one minute earlier.
Today at 11:45 am: a repeated entry.
It seems to be confused with all the entries prior to Today at 12:47 pm.
Any idea why?
Thanks,
Doug

Anyway, I see what the Time Machine problem is. It is an artifact resulting from the fact that the finder window I was examining is on an external monitor.
Time Machine displays on the MBP monitor, but none of the items are selectable, and some entries are incorrect.
If I move the finder window to my MBP display and run Time Machine the entries are correct and selectable.
So Time Machine apparently just doesn't play well with what is showing on an external monitor.
AppleCare's response to that was: "Well, that is odd."
Anyway, that is how it appears to work. I'll just make sure to not use Time Machine with a finder window on an external monitor for now.
I don't know whether to mark this as "resolved" or not. I think I will, but Time Machine does seem to have a bug regarding finder windows on external monitors.
doug

Time machine seems to have losts valauble brain cells

Time machine on my macbook is seriosuly stupid. When you wake the macbook up and there is no network available time machine will constantly try to mount the disk to back up (I back up over my home network)
The consequence to this can be devastating. For instance if I try to open or save anything the finder cannot find the network either and allt hat occurs is you get a system wide crash.
This used to happen in 10.4 and 5 and seemed to be fixed for a while in 6, but its back with a vengence.
It mightn ot be time machine persay, but an issue of the fact that snow leopard is a bit stuipd so does not realise that if a network is not available its not going to find the disk that was on that network.
So why does it not just stop looking instead of crashing my mac?

Gary i wrote:
TM will constantly attempt to find the disk, it will spin dumbly all day.
But I think this is merely the manifestation of a larger issue in that SL is too stupid to work out that my network is not there.
No. It doesn't on mine when I am at work - it looks once, fails and gives up so the fault is somehow in your machine. In fact, when I reconnect to the TM at home, it will not restart until I prompt it to do it. This is how it operates when not being confused by something. The something is in your machine, not in the TM or TC interface so lets try and find out what the problem is.
Could you download the Time Machine Buddy Widget and let it run when you are next at work and extract the logs. Post them here please. ? We can then see what is happening.
Initial thoughts are that somehow your system thinks the backup drive is mounted even though it isn't there and so it will try and keep backing up. Normally when you disconnect, or a drive isn't there, there is an ignore button which one can use to temporarily fool the system while a backup drive is being swapped for example. Its almost as if someone is pressing the Ignore button and the backup drive is staying mounted.
Thanks

Time machine seems to not be backing up everything

Basically, after installing Yosemite I have this issue where most of the time I want to use Time Machine with my external HDD it says "Backing up... 1MB/6.35GB". It seems to be only backing up around about 6GB of my computer, where I know that there is definitely over 200GB of data that needs to be backed up. I have noticed that if I erase my backup HDD and then run a backup, it seems to work perfectly, however I do not want to erase my backup disk incase there happens to be a problem with the new backup which results with me not having a backup at all. Is this a bug or is it my hard disk drive? Is there a way I can fix this issue?
Thanks
I am running OS X Yosemite 10.10.1

If this isn't the initial backup, Time Machine just backs up what has changed, which is a much smaller amount than the total data size.

With a new exHD, time machine seems to copy backups, then stalls.

Hi, my old external hard drive backup, a MyBook, is filling up, so I bought a Seagate Backup Plus to take over the Time Machine backups. I formatted and partitioned the new EHD, and it seemed to start the process of copying the TM backups. But then I get a message:" You may need to enter the name and password for an administrator on this computer to change the item named backups.backupdb."
However, it gives me no option to entering the name and password. It basially gives me the option of Skipping, continuing, or stopping. Any choice results in the copying progress bar freezing.
In addition I *did* give the name and password at the beginning of the process. So I really don't understand what's going on. Also, I am able to copy old files from the MyBook to the second partition on the Seagate with no problem.
Could the size of the TM backup be an issue? It's about 1.5 TB.
Appreciate any help, thanks.

Thanks Eric,
I have followed the steps in the first link. It's in the copying the old drive backup to the new drive where the freeze happens.
I've also had Disk Utility check the disks, which seem OK.
One thing I'm noticing now is that I do *not* see the "Ignore ownership" check box in the Sharing and Permissions" section for the new Time Machine partition, which is weird, because I'm pretty sure the first time I tried it, it was there. That check box is still visible in the other partition, but not in the partition I've created for Time Machine. I have no idea what it means.
Not sure what else to try. I may try to contact Seagate support tomorrow and just see how responsive they are.
Thanks again.

Time Machine seems to be culprit in kernel errors which crash system

I have had a rash of seemingly random crashes. The system has a kernel panic and boom I am dead and rebooting...
reinstalled OS, removed any third party extensions... no joy. Still happening.
Running time machine to Airport 3TB Time Capsule... and an external USB connected HD.
Turned off Time Machine, haven't had a repeat. Turned it back on and bam kernel panic and reboot.
Any suggestions?

Post the Kernel Panic Report. If you don't know how please click How to log a kernel panic

Time Machine won't "un-exclude" external drive

Any help appreciated. I have a Western Digital Passport 120G external hard drive that Time Machine won't backup. It's mounted fine; operates fine; when I go to Preferences>Time Machine>Options it's listed under "Do not back up" but it's grayed out. It won't allow me to "un-exclude" it.
Any suggestions?
Cliff

Well, I checked and it was factory formatted FAT32. I'll move my data to a DVD and reformat. I tried to read up on Apple.com but couldn't find any TM/HFS+ docs; I never would have found this info. Thanks, Barry.

Time Machine seems to wake up my external hard drive for no reason?

I'm not sure why it does this. It doesn't sync all the time as far as I know, it's really annoying and it's wearing the hard drive for no reason. Is there some way to stop it and only wake up when I need something off of it, or when Time Machine is backing up? It randomly goes to sleep and then wakes up again.
I have already set "put hard drives to sleep" in the System Preferences.
Also, since I believe it is Time Machine causing this issue, could I simply eject the partition that I use for backups / Time Machine? It's still plugged in then and if TM needs it, it will maybe scan the computer again and eventually find it?

Anon M wrote:
Well, I don't save anything to the hard drive. So it's kind of weird that it starts spinning.
I think it happens even if you bring up a save dialog.
Can I disconnect it from Time Machine from time to time? Like, does it matter if I connect the drive only once a day or so to the Mac, or does it have to be permanently connected to be able to work with TM?
Sure. Time Machine will even remind you after 10 days of not backing up.
Some people have installed scripts to ping external drives to keep them spinning. It doesn't hurt the drive any.

Time machine seems to crash my MacBook

I hope someone can help. I have a MacBook and back it all up on a 1tb partitioned external hdd via my airport extreme over my network. This has been working fine for the past 2 months on hourly backups but two days ago when the backup started it would search for the hdd, not actually start the backup and freeze. The screen would darken and a message across the screen pops up saying I need to restart my MacBook. After a hard restart I have to turn off time machine to ensure it doesn't happen again. It would if I didn't turn time machine off. Am I sceptical that this timing is linked to me attempting to update to 10.7.3 at the same time and for some reason it didn't complete the download and install the update. I hear this update is flawed and the timing was the same as when this problem first happened. Can anyone help please? (I hope this makes sense!) Michael.

Is this what you want?
Thu Feb 23 20:04:16 2012
panic(cpu 0 caller 0xffffff80004db38c): "hfs_getnewvnode: bad ca_blocks (too small)"@/SourceCache/xnu/xnu-1699.24.8/bsd/hfs/hfs_cnode.c:1046
Backtrace (CPU 0), Frame : Return Address
0xffffff804166b900 : 0xffffff8000220702
0xffffff804166b980 : 0xffffff80004db38c
0xffffff804166ba70 : 0xffffff80004e37e9
0xffffff804166bc20 : 0xffffff80003169a4
0xffffff804166bc60 : 0xffffff80002f494a
0xffffff804166bce0 : 0xffffff80002f37bc
0xffffff804166bd80 : 0xffffff80002e3abe
0xffffff804166bf50 : 0xffffff80005caa9b
0xffffff804166bfb0 : 0xffffff80002d8363
BSD process name corresponding to current thread: backupd
Mac OS version:
11C74
Kernel version:
Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64
Kernel UUID: <edited out>
System model name: MacBook7,1 (Mac-F22C89C8)
System uptime in nanoseconds: 13085868023578
last loaded kext at 12408824950916: com.apple.filesystems.afpfs       9.8 (addr 0xffffff7f80eff000, size 356352)
last unloaded kext at 12602137783562: com.apple.iokit.IOEthernetAVBController   1.0.0d5 (addr 0xffffff7f80795000, size 20480)
loaded kexts:
com.Symantec.kext.SAVAPComm     11.0.6
org.virtualbox.kext.VBoxNetAdp      4.1.2
org.virtualbox.kext.VBoxNetFlt        4.1.2
org.virtualbox.kext.VBoxUSB            4.1.2
org.virtualbox.kext.VBoxDrv            4.1.2
com.apple.filesystems.afpfs 9.8
com.apple.nke.asp_tcp          6.0.1
com.apple.driver.AppleHWSensor   1.9.4d0
com.apple.filesystems.autofs            3.0
com.apple.driver.AudioAUUC           1.59
com.apple.driver.AppleMikeyHIDDriver     122
com.apple.driver.AppleMikeyDriver           2.1.3f7
com.apple.driver.AppleUpstreamUserClient          3.5.9
com.apple.driver.AppleMCCSControl          1.0.26
com.apple.GeForce    7.1.2
com.apple.driver.AppleHDA 2.1.3f7
com.apple.driver.AGPM        100.12.42
com.apple.driver.AppleLPC 1.5.3
com.apple.driver.AppleBacklight     170.1.9
com.apple.driver.SMCMotionSensor           3.0.1d2
com.apple.iokit.IOUserEthernet       1.0.0d1
com.apple.Dont_Steal_Mac_OS_X      7.0.0
com.apple.driver.AudioIPCDriver    1.2.1
com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.5d4
com.apple.driver.AppleUSBTCButtons        225.2
com.apple.driver.AppleUSBTCKeyboard    225.2
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless      1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache            33
com.apple.iokit.SCSITaskUserClient            3.0.1
com.apple.iokit.IOAHCIBlockStorage           2.0.1
com.apple.driver.AirPort.Brcm4331           512.20.18
com.apple.driver.AppleUSBHub      4.5.0
com.apple.driver.AppleAHCIPort     2.2.0
com.apple.nvenet      2.0.17
com.apple.driver.AppleUSBEHCI     4.5.0
com.apple.driver.AppleUSBOHCI     4.4.5
com.apple.driver.AppleEFINVRAM 1.5.0
com.apple.driver.AppleRTC 1.4
com.apple.driver.AppleHPET           1.6
com.apple.driver.AppleSmartBatteryManager      161.0.0
com.apple.driver.AppleACPIButtons           1.4
com.apple.driver.AppleSMBIOS       1.7
com.apple.driver.AppleACPIEC        1.4
com.apple.driver.AppleAPIC            1.5
com.apple.driver.AppleIntelCPUPowerManagementClient          167.0.0
com.apple.nke.applicationfirewall   3.2.30
com.apple.security.quarantine        1
com.apple.driver.AppleIntelCPUPowerManagement        167.0.0
com.apple.security.SecureRemotePassword          1.0
com.apple.kext.triggers         1.0
com.apple.driver.DspFuncLib          2.1.3f7
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.driver.AppleSMBusPCI   1.0.10d0
com.apple.driver.AppleBacklightExpert     1.0.3
com.apple.nvidia.nv50hal    7.1.2
com.apple.NVDAResman      7.1.2
com.apple.iokit.IOSurface     80.0
com.apple.iokit.IOBluetoothSerialManager            4.0.1f4
com.apple.iokit.IOSerialFamily         10.0.5
com.apple.iokit.IOAudioFamily         1.8.3fc11
com.apple.kext.OSvKernDSPLib      1.3
com.apple.driver.ApplePolicyControl          3.0.16
com.apple.driver.AppleGraphicsControl     3.0.16
com.apple.iokit.IONDRVSupport      2.3.2
com.apple.driver.AppleHDAController        2.1.3f7
com.apple.iokit.IOGraphicsFamily    2.3.2
com.apple.iokit.IOHDAFamily           2.1.3f7
com.apple.driver.AppleSMC 3.1.1d8
com.apple.driver.IOPlatformPluginFamily 4.7.5d4
com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.1f4
com.apple.driver.AppleUSBBluetoothHCIController         4.0.1f4
com.apple.iokit.IOBluetoothFamily 4.0.1f4
com.apple.driver.AppleUSBMultitouch       227.1
com.apple.iokit.IOUSBHIDDriver     4.4.5
com.apple.driver.AppleUSBMergeNub       4.5.3
com.apple.driver.AppleUSBComposite        3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice        3.0.1
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily          1.7
com.apple.iokit.IOCDStorageFamily 1.7
com.apple.driver.XsanFilter 403
com.apple.iokit.IOAHCISerialATAPI 2.0.1
com.apple.iokit.IOSCSIArchitectureModelFamily   3.0.1
com.apple.iokit.IO80211Family       411.1
com.apple.iokit.IOUSBUserClient     4.5.3
com.apple.iokit.IOAHCIFamily          2.0.7
com.apple.iokit.IONetworkingFamily           2.0
com.apple.iokit.IOUSBFamily            4.5.3
com.apple.driver.NVSMU      2.2.9
com.apple.driver.AppleEFIRuntime            1.5.0
com.apple.iokit.IOHIDFamily            1.7.1
com.apple.iokit.IOSMBusFamily       1.1
com.apple.security.sandbox 165.3
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet     7
com.apple.driver.DiskImages           331
com.apple.iokit.IOStorageFamily      1.7
com.apple.driver.AppleKeyStore     28.18
com.apple.driver.AppleACPIPlatform         1.4
com.apple.iokit.IOPCIFamily 2.6.7
com.apple.iokit.IOACPIFamily          1.4
System Profile:
Model: MacBook7,1, BootROM MB71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB, SMC 1.60f5
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313132533654465238432D47372020
Memory Module: BANK 1/DIMM0, 1 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313132533654465238432D47372020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.100.98.75.18)
Bluetooth: Version 4.0.1f4, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Hitachi HTS545025B9SA02, 250.06 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0x06630000 / 5
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x06300000 / 2

HT3275 How do I restart the time machine. seems like this is causing my computer to operate slow the last several weeks.

How do I re-start the Time Mchine. I continue to get pop ups telling me time machine cannot complete the uodating

What OS is on the computer?
If you run lion, make sure you install the supplement.
This is specifically for TM.
http://support.apple.com/kb/DL1599
If you run Mountain Lion there is no fix.. but check the ML section of discussions as there are several issues with TM failing.

Time Machine... seems silly to exclude

Similar Messages

Maybe you are looking for