Time Machine ignoring excluded items (performing full backup)

Hi.
I started having problems with Time Machine recently.
My macbook hard drive has 250 GB, 80 GB free. In the Time Machine preference pane options I have selected a couple of folders so that an "estimated full backup" is 52.9 GB. When I'm running TM it tries to backup the full drive (160GB) ignoring the folders I chose to exclude.
I have verified and repaired both my main hard drive and the external drive used for Time Machine.
The log in the console initially says that it is going to backup 44GB and then it continues copying more data:
1/24/10 10:14:02 PM com.apple.backupd[378] Starting standard backup
1/24/10 10:14:03 PM com.apple.backupd[378] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
1/24/10 10:14:10 PM com.apple.backupd[378] Backup content size: 157.0 GB excluded items size: 113.0 GB for volume Macintosh HD
1/24/10 10:14:10 PM com.apple.backupd[378] No pre-backup thinning needed: 53.73 GB requested (including padding), 260.74 GB available
1/24/10 11:14:04 PM com.apple.backupd[378] Copied 4.1 GB of 44.0 GB, 1471 of 782012 items
1/25/10 12:14:05 AM com.apple.backupd[378] Copied 6.3 GB of 44.0 GB, 20599 of 782012 items
1/25/10 1:14:06 AM com.apple.backupd[378] Copied 9.0 GB of 44.0 GB, 48709 of 782012 items
1/25/10 2:14:06 AM com.apple.backupd[378] Copied 11.1 GB of 44.0 GB, 124469 of 782012 items
1/25/10 3:14:07 AM com.apple.backupd[378] Copied 21.9 GB of 44.0 GB, 155468 of 782012 items
1/25/10 4:14:08 AM com.apple.backupd[378] Copied 42.0 GB of 44.0 GB, 156348 of 782012 items
1/25/10 5:14:08 AM com.apple.backupd[378] Copied 62.5 GB of 62.5 GB, 156455 of 782012 items
1/25/10 6:14:09 AM com.apple.backupd[378] Copied 83.1 GB of 83.1 GB, 156517 of 782012 items
1/25/10 7:14:10 AM com.apple.backupd[378] Copied 103.7 GB of 103.7 GB, 156648 of 782012 items
1/25/10 7:56:21 AM com.apple.backupd[378] Copied 183712 files (114.1 GB) from volume Macintosh HD.
1/25/10 7:56:23 AM com.apple.backupd[378] Backup canceled.
1/25/10 7:57:55 AM com.apple.backupd[378] Stopping backupd to allow ejection of backup destination disk!
1/25/10 8:20:53 AM [0x0-0xb50b5].backupd-helper[2308] Not starting Time Machine backup after wake - failed to resolve alias to backup volume
1/25/10 8:46:07 AM com.apple.backupd-auto[2421] Not starting scheduled Time Machine backup - time machine destination not resolvable.
Thanks for the help!

Hi, and welcome to the forums.
We have seen this on rare occasions.
Start by Repairing your Time Machine drive and verifying your internal HD, per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
Also do a "full reset" of Time Machine via #A4 there.
If that doesn't help, there's probably something corrupted in OSX.
You'll need to reinstall it from your Snow Leopard Install disc, then download and install the "combo" update to get back to 10.6.2. Info and download available at: http://support.apple.com/kb/DL959 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

Similar Messages

I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

Did you follow the instructions on the page linked below?
OS X Yosemite: Recover your entire system

Time Machine will not do a full backup when set up

I am trying to set up time machine for the first time on a external HDD, but it just won't do a full backup in the first time I set it up, I knew I had a problem when I entered the time machine and it would only show today and now, I had the time machine set up for about a week. I already checked the time machine options and it says full backup should be 178 GB, but when I set it up it does not do the full backup just a partial, the time machine disk is always empty, I see no errors in the time machine preferences and also formatted the external HDD the HDD Mac OS Extended, Mac OS Extended (Journaled), Mac OS Extended (Case Sensitive), Mac OS Extended (Case Sensitive Journaled) and even tried a different HDD and I always get the time thing, no full backup when I set it up, also fixed permissions on all my disks and no luck... can anyone help???

this is the message I got;
Starting standard backup
Couldn't find en0.
Unable to determine UUID for host. Error: 35 Resource temporarily unavailable
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[NSCFArray initWithObjects:count:]: attempt to insert nil object at objects[0]'\n* Call stack at first throw:\n(\n 0 CoreFoundation 0x00007fff833c05a4 __exceptionPreprocess + 180\n 1 libobjc.A.dylib 0x00007fff887d2313 objcexceptionthrow + 45\n 2 CoreFoundation 0x00007fff8336b317 -[__NSPlaceholderArray initWithObjects:count:] + 407\n 3 CoreFoundation 0x00007fff8337fc68 +[NSArray arrayWithObjects:count:] + 56\n 4 CoreFoundation 0x00007fff8338adb1 -[NSArray arrayByAddingObject:] + 193\n 5 backupd 0x000000010000989b 0x0 + 4295006363\n 6 backupd 0x000000010000a510 0x0 + 4295009552\n 7 backupd 0x0000000100006d00 0x0 + 4294995200\n 8 Foundation 0x00007fff80f04f65 _NSThread__main_ + 1429\n 9 libSystem.B.dylib 0x00007fff80876f66 pthreadstart + 331\n 10 libSystem.B.dylib 0x00007fff80876e19 thread_start + 13\n)
terminate called after throwing an instance of 'NSException'
2009-11-08 22:50:42.463 ReportCrash[235:2503] Saved crash report for backupd[146] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2009-11-08-225042localhost.crash

Time Machine wants to do a full backup. How do I point it to my previous backups so it will do an incremental backup?

I lost my wireless connection to my backup drive for a short time. Now time machine wants to do a full backup. It doesn't know that I have previous backups. How do I point it to the previous backups so that time machine continues to do incremental backups rather than doing another full backup.

I did some more reading and I found that Time Machine would find the older backups once a new backup is completed. The backup ended up being a little larger than previous backups (2.65 GB vs typical incremental backups of several MB's) but when it completed, time machine updated the last backup time/date and the oldest backup time/date properly. So I guess, I don't have a problem.

Time Machine don't make a full backup

I just started with Time Machine. I made my first backup with a USB cabel of my Mac book Pro (28 gb used) but the Time Machine folder is only about 22 gb - how can that be?
Time Machine haven't come up with any errors but I think there is something wrong anyway.
Do one of you have any ideas?
Thanks in advance
/Kudsk

My first backup was with a usb cable but then I went wireless I wanted to use Time Machine but this time it made a new file called "Lars Kudsks computer_001b63b12c5a.sparsebundle" instead of using the "Backups.backupdb" folder. - How can that be?
And my mac book pro only finds the external drive if I open the Finder window (and in some way show "Time Machine" where to find the external drive - if you understand what I mean).

Time Machine doesn't do a full backup

Hi there,
I have a 320GB external hard drive I use as a Time Machine backup. This has always worked before.
Recently I reformatted it and made a small partition (70GB) for other bits and bobs. Now though, whenever it backs up only a few KB of data seem to change, nothing I add or delete on my MacBook HD gets backed up to the external drive. Which is worying!
There's ample room in the backup partition to add the updated files, but it doesn't.
I've troubleshooted it, done a full reset etc, but I can't work it out. Any help would be greatly appreciated. Is it best not to have any partition at all?
Thanks in advance.
- Stevie

I did some more reading and I found that Time Machine would find the older backups once a new backup is completed. The backup ended up being a little larger than previous backups (2.65 GB vs typical incremental backups of several MB's) but when it completed, time machine updated the last backup time/date and the oldest backup time/date properly. So I guess, I don't have a problem.

HT3728 Time Machine only wants to do full backup not incremental

just replaced hard drive and restored from time machine however time machine looks like it is trying to do a full back up and says not enough space available when should be enough for incremental. Do I delete backup and reconnect to time machine?

There are some cases when you can continue to use the old TM backups and situations where you cannot or should not.. but before you delete your backups .. something I am always very reluctant to do, make sure you have all your files.. If you are talking about a Time Capsule you can archive off the old backup to a USB drive using 5.6 version utility or new 6.3 version. It is not available in 6.0-6.2
Then you can safely erase the drive and start over.
Read pondini on continuing your backups.
B5 and B6 here.
http://pondini.org/TM/Troubleshooting.html

How to set time machine to only do a full backup manually?

I just want to do a full backup every once in a while, manually. Then turn TM back off. Can this be done? Or maybe set the frequency to just once a week/month?

To set the frequency, Set to OFF and then place the following launchd plist in ~/Library/LaunchAgents/ (mine is saved as "com.tonyt.StartTimeMachine.plist") and then log-out and back in (or re-boot)
This is set for weekly, Monday at 12:00am:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
          <key>Label</key>
          <string>com.tonyt.StartTimeMachine</string>
          <key>ProgramArguments</key>
          <array>
                    <string>/usr/bin/tmutil</string>
                    <string>startbackup</string>
          </array>
          <key>QueueDirectories</key>
          <array/>
          <key>StartCalendarInterval</key>
          <dict>
                    <key>Hour</key>
                    <integer>0</integer>
                    <key>Minute</key>
                    <integer>0</integer>
                    <key>Weekday</key>
                    <integer>1</integer>
          </dict>
          <key>WatchPaths</key>
          <array/>
</dict>
</plist>
For the 2nd of each month at 12:00am use:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
          <key>Label</key>
          <string>com.tonyt.StartTimeMachine</string>
          <key>ProgramArguments</key>
          <array>
                    <string>/usr/bin/tmutil</string>
                    <string>startbackup</string>
          </array>
          <key>QueueDirectories</key>
          <array/>
          <key>StartCalendarInterval</key>
          <dict>
                    <key>Day</key>
                    <integer>2</integer>
                    <key>Hour</key>
                    <integer>0</integer>
                    <key>Minute</key>
                    <integer>0</integer>
          </dict>
          <key>WatchPaths</key>
          <array/>
</dict>
</plist>

How do you perform full backup after disk change?

My backup disk crashed yesterday so I bought a new one today. I connected the drive and told Time Machine to change the disk to the new one. It performed an incremental backup. Does anyone know how I force a full backup onto the new drive? Thanks

It was very small. However, I went out for a half-hour and when I came back, Time Machine is now doing a full backup (small status bar shows that it will backup 175GB). Thanks for your help.

Time Machine randomly performing full backups instead of incremental

I've been using a Time Capsule since October 2009 with my 13" MBP running Snow Leopard with no issues.
A few weeks ago, I noticed Time Machine decided to do a full 160GB backup, which then filled the Time Capsule and then deleted older backups. It then kept trying to do full backups every single time, resulting in the error 'Not enough space'.
I archived the backups from the Time Capsule, disabled Time Machine and completely erased the Time Capsule.
I set up Time Machine again and it's been working for about a week, but it's doing the same thing again - trying to do another large HD sized backup of 160GB or so (the amount of data my drive has).
I have noticed in the logs the following line
*17/02/2010 13:36:16 com.apple.backupd[946] Event store UUIDs don't match for volume: HD*
Which seems to appear as Time Machine starts to do it's full backup.
Any ideas? It's getting to the point that Time Machine is becoming unusable as I can't rely on it.

Cool, I'll give that a try.
Log files are here. I did rename my machine to remove spaces and punctuation but haven't backed up since then (only a few hours ago).
Should I resume this backup or erase the TC and start again? (I've also renamed the TC network and drive)
Feb 20 00:16:14 marty com.apple.backupd[8919]: Starting standard backup
Feb 20 00:16:14 marty com.apple.backupd[8919]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:22 marty com.apple.backupd[8919]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:32 marty com.apple.backupd[8919]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:16:32 marty com.apple.backupd[8919]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:16:38 marty com.apple.backupd[8919]: No pre-backup thinning needed: 1.13 GB requested (including padding), 264.22 GB available
Feb 20 00:16:47 marty com.apple.backupd[8919]: Copied 8 files (15 KB) from volume HD.
Feb 20 00:16:47 marty com.apple.backupd[8919]: Starting post-backup thinning
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-234422: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-225109: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Post-back up thinning complete: 2 expired backups removed
Feb 20 00:16:48 marty com.apple.backupd[8919]: Backup completed successfully.
Feb 20 00:16:50 marty com.apple.backupd[8919]: Ejected Time Machine disk image.
Feb 20 00:16:51 marty com.apple.backupd[8919]: Ejected Time Machine network volume.
Feb 20 00:23:42 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:23:42 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:23:52 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:24:11 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine network volume.
Feb 20 00:25:24 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:25:24 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:25 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:30 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:25:32 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:34:44 marty com.apple.backupd[9017]: No pre-backup thinning needed: 200.38 GB requested (including padding), 264.22 GB available
Feb 20 00:35:46 marty com.apple.backupd[9017]: Copied 283 files (6.5 MB) from volume HD.
Feb 20 00:35:46 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:35:49 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:35:50 marty com.apple.backupd[9017]: Ejected Time Machine network volume.

Time Machine will not complete a system backup and terminates with "Unable to complete backup. An error occurred while copying files to the backup volume. This follows a problem when Time machne terminated when the volume was almost full.

On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.

jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions.

I bought a new external hard drive for backups, but time machine won't do a full back up. I think it is remembering backing up onto previous external hard drives, which I don't own anymore. How do I do a new full backup?

I bought a new external hard drive for backups, but time machine won't do a full back up.
I think it is remembering backing up onto previous external hard drives, which I don't own anymore. How do I do a new full backup?
When I bought the new (used) iMac, I also bought an external hard drive for backups. It worked fine, but my husband stole it.
Then I bought a new external hard drive (Seagate) and it worked fine for three weeks, then died.
So I just got a new external hard drive, which was put together from an internal hard drive and a hard drive enclosure.
Time machine did the first backup today, and it should have taken 9 hours like it did on the previous first time full back up. Instead, it took 30 minutes. That can't be right. I want to start over and do a full backup to make sure everything gets onto my new external hard drive, but I can't figure out how to do that. Please help.

Triple-click anywhere in the line below to select it:
tmutil compare -E
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).
The command will take at least a few minutes to run. Eventually some lines of output will appear below what you entered.
Each line that begins with a plus sign (“+”) represents a file that has been added to the source volume since the last snapshot was taken. These files have not been backed up yet.
Each line that begins with an exclamation point (“!”) represents a file that has changed on the source volume. These files have been backed up, but not in their present state.
Each line that begins with a minus sign (“-“) represents a file that has been removed from the source volume.
At the end of the output, you’ll get some lines like the following:
Added:
Removed:
Changed:
These lines show the total amount of data added, removed, or changed on the source(s) since the last snapshot.

Time Machine does not automatically delete old backups when drive is full

I back up to a 1TB external drive with TM. It will not delete old back-ups and instead tells me that the drive is full. I thought TM was supposed to manage all of this on its own.

It will, if it can. But it will never delete your last remaining backup.
See #C4 in Time Machine - Troubleshooting, probably the pink box there.
Basically, if Time Machine has to do a full or very large backup, and your Time Machine drive isn't well over twice the size of the data it's backing up, there won't be room for the last backup, plus the new one, plus some workspace.

Time Machine never gets out of Indexing backup...

I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Each time I try to backup the message log contains:
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Backup content size: 253.8 GB excluded items size: 613.1 MB for volume Macintosh HD
303.83 GB required (including padding), 1.82 TB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
So far I have:
1. Verified my main hard disk and my original backup disk.
2. Bought a new external hard disk and set it up as a new backup disk.
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Given the failure earlier today I am really keen to get a full back up done.
Any ideas?
John

JWaterworth wrote:
I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Indexing the backup and actually performing the backup are two different things. Sometimes Lion Time Machine has trouble maintaining the index when used over a wireless network. That doesn't affect the creation of new backups. You can always enter Time Machine and see just how many backups you have.
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
After the initial backup, Time Machine doesn't take much CPU time.
So far I have:
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Please don't do things like this. What you need to do now is:
1) Boot from your recovery volume.
2) Repair your disk and permissions
3) Wait for Spotlight to finish reindexing your hard drive.
4) Erase your Time Machine drive and start Time Machine over again.
Come back if you are still having trouble. If you muck around with low-level files that shouldn't be mucked with, all bets are off.

Time Machine ejecting internal hard drive during backup

I originally posted this in the Time Machine group. It was suggested I post to the Xserve group.
We have an XSERVE running 10.6.4 server. It has 2 internal 1TB drives. The plan is to use one as the main drive and the second as a Time Machine backup. This used to work in 10.5, but since about 10.6.2 or so, it has not worked correctly.
Time machine will come on, begin the backup, and then error off with a message that the drive has been ejected. I have erased the drive, but still no joy. I have partitioned the drive, still no joy. I have verified the drive repeatedly, and all is fine. I can copy files to and from the drive until the cows come home, and all works fine, which means I do not think it is the drive itself. Activate TM, however, and it will fail before the first backup is completed. The only way to get the drive back is to do a complete power down and then power up. Needless to say, that is not a good thing for a server that we rely on.
Any ideas?
10/14/10 10:41:27 AM com.apple.backupd1230 Backup content size: 542.8 GB excluded items size: 474.1 GB for volume Server HD 10/14/10 10:41:27 AM com.apple.backupd1230 No pre-backup thinning needed: 82.46 GB requested (including padding), 930.13 GB available 10/14/10 10:41:27 AM com.apple.backupd1230 Waiting for index to be ready (101) 10/14/10 10:41:27 AM mds70 (Normal) DiskStore: Creating index for /Volumes/backup/Backups.backupdb
10/14/10 10:47:38 AM kernel FusionMPT: Notification = 22 (SAS Discovery) for SCSI Domain = 0 10/14/10 10:47:38 AM kernel Discovery condition = 0x000f0001 10/14/10 10:47:38 AM kernel FusionMPT: Notification = 18 (SAS Phy Link Status) for SCSI Domain = 0 10/14/10 10:47:38 AM kernel SAS Phy Link Status: PhyNum = 0, old link rate = 8, new link rate = 0, SASAddress = 50080007002e8c04
10/14/10 10:48:10 AM kernel SCSIPressurePathManager: Timed out waiting for inactive/error path to become active, loops = 0 10/14/10 10:48:10 AM kernel  10/14/10 10:48:10 AM kernel disk0s2: media is not present.
10/14/10 10:48:10 AM com.apple.backupd1230 Stopping backupd because the backup volume was ejected!  10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Copied 13416 files (4.0 GB) from volume Server HD. 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook called. 10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook done. 10/14/10 10:48:11 AM kernel jnl: disk0s2: close: journal 0xffffff8012b15d20, is invalid. aborting outstanding transactions  

No, it is not always at the same point/file/bytes transferred. It will vary from a few GB (say 3GB) to quite a few GB (say 30GB). I would add amongst the things I have done was to:
Perform numerous Disk Utility Checks. Never any errors found.
Erased the backup drive on multiple occasions. Double checked the GUID and format.
Partitioned the drive and tried backing up to a new partition. (No joy there either)
Copied lots and lots of data from the root disk to said partitions to test them. All went fine.
It really is Time Machine that is causing the issue. I can use the drive all day long as long as TM does not run. When it does, I eventually get a failure message that the drive has been ejected.
While I have not tried making a partition on the home drive (I'd rather not, lots of data there, make users mad, and since TM is not working, I have no backups at present), I do limit the data that is being backed up to JUST that of the system. /Users is being excluded at the moment. So I doubt there is anything out of the ordinary in the system. And, yes, I did a disk check on the root disk and all is fine there too.

Time Machine ignoring excluded items (performing full backup)

Similar Messages

Maybe you are looking for