Time machine backups too much

I recently started using time machine, backing up automatically wireless to timecapsule(1TB). I noticed that every hour, time machine is backing up approximately 20GB (while i only use 100GB in total of a 250hard drive). is it possible it has something to do with running Windows in VMwarefusion at the time the system is backing up? why would time machine make such huge backups and how do i prevent that from happening?

Thomas is entirely, 100%, correct.
Besides taking up a huge amount of space, Time Machine will sometimes choke on those VM files (as it's one monster file to OSX).
If you want, you can delete all the backups of it, per #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum.

Similar Messages

Time Machine backup too large for backup disk

My Mac hard drive is 750GB (25GB free).
My LaCie external dedicated backup hard drive is 1TB (342GB free).
I am now getting the error "Time Machine couldn't complete the backup" "This backup is too large for the backup disk"
I thought once my initial backup of 750GB happened, it would be incremental backups from then on (with old changes betting deleted as space was needed for new changes).
Is this not the case? Do I need a much larger backup drive or something?
Thanks much for any help.

It's true but Time Machine has also to make complete backups again in case you want to restore your Mac with a more recent Time Machine backup.
Clearly the external drive you have doesn't have enough storage to back up your Mac. As you have about 725 GB of used space, I recommend you to get at least a 3 or 4 TB external drive to make backups, and even with this, don't think you will have more than four backups. Another thing you can do is to remove folders from the backup in System Preferences > Time Machine > Options

Time machine spends too much time backing up

Even when I have very little changed information to back up - say 15MB - time machine takes 10-15 minutes.   Every hour.   It spends like 3-4 minutes "Setting up", another 5-8 minutes "Backing up XXX of 15.2MB", and then another 3-5 minutes "cleaning up".
Syncing or backing up changed data on the same drive takes Synchronize! X Plus barely over a minute. Maybe a 1 minute compare time and then 10s of file copying, then done.   Why is TM so much slower?
Since I can't change how often TM runs (that's really annoying, BTW, Apple), this means that almost 25% of the time my mac is disk-bound and slow. Extremely frustrating to work on.   I often end up working on my 3-year-old macbook pro because it doesn't have to deal with TM (I just sync it to the desktop every couple of days with Synchronize! X Plus) and so in practice it's a whole lot faster to work with than the mighty 2.66 Ghz Quad-Core Xeon Mac Pro with 8GB RAM.
I don't think it's anything wrong with the TM disk.   I've observed this kind of behavior on every mac I've used with TM in the last four years - at least three different macs and at least nine different external drives.
Why on Earth does TM take geological time to back up my mac every hour?    I know it has some comparisons to do, but copying those files should only take a few seconds.     Does it behave this way for everyone, or am I just unlucky?

this means that almost 25% of the time my mac is disk-bound and slow.
I run Time machine on my server. It uses under 2 percent of CPU. I find that it works at low priority and does not interfere with other activities. I have not observed any substantial slowdown due to disk access or any other reason.
know it has some comparisons to do, but copying those files should only take a few seconds.
If you want it locked up so hard that you cannot even type, it probably could copy those files in a few seconds. It is intended to do its work in the background, and allow you to continue to do other work.
Since I can't change how often TM runs...
Oh yes, you can. Apple did not give access to those parameters directly, but those settings and others are in several .plist files and can be changed with third-party utilities.
What computer are you backing up, and how much memory is installed?
Are you ever seeing any Pageouts on the Activity Monitor Memory display?
Are you backing up directly to a local disk, over Wireless, or over Ethernet, and at what speed?
Is the disk that contains the Time Machine backup files used for any other purpose?
Have you ever made changes to the Time Machine disk using the Finder?

After System Restore Time Machine does too much!

I had some issues with boot camp that I will not go into now. Haha. After reinstalling Leopard and using my previous time machine backup stuff to resort to, my computer is fine. It's just like the way I left it the last time i did a backup. However, when I went to do a current back up, it has to back up like 100 GB of stuff which makes no sense, I have done nothing new. I think it's backing up the same stuff that it already has. Somehow after the system restore it can't tell that it already backed up everything that's on my computer. Any suggestions!? Thanks.

Is there anything I can do so that I don't have to waste so much space with the same stuff?

Time machine backup too big for empty disk??

So I restart my MacBook Pro a few minutes after completing a full Time Machine backup. When it restarts it goes through the grey startup screen, then gets stuck on the blue screen just before the desktop normally appears. This happens whenever I startup. I am still able to hit the power button and get the Restart/Shut Down dialog, so I restart using my Snow Leopard boot disk, run Disk Utility, repair permissions, and repair disk, but the problem still remains. I decide to Restore from Time Machine Backup, so I erase my disk (80 GB, had only 200 MB free), go to the Restore screen and connect my backup disk. Now the weird part -- it says my latest backup is too big for the disk, even though i just erased everything, and 74.2 GB show as free. All my previous backups seem to fit fine, but apparently the last time Time Machine backed up more from my disk than can fit on my disk! It seems having a hard disk close to full is enough to render a backup effectively useless. Guess I'll have to restore from a previous backup, then manually copy the newer files. Just wanted to alert others to this insane problem, so it doesn't happen to them.

dgordon412 wrote:
(80 GB, had only 200 MB free)
That's likely corrupted your system. You should have a minimum of 10% - 15% free at all times. That's almost certainly why it wouldn't restart.
even though i just erased everything, and 74.2 GB show as free.
There must be something else on the drive; if you erase it, it should have just under 80 GB free. Is there another partition?
Did you erase with a Leopard Install disc or a Snow Leopard disc? If you used a Leopard disc, that might explain showing only 74.2 GB free (it counts differently).
If so, use your +Snow Leopard+ install disc to do a complete reformat, and try to restore the backup. A Leopard disc cannot restore a Snow Leopard backup. Even the Snow Leopard disc may not work, as it's just too full and/or your system was damaged by getting too full.
All my previous backups seem to fit fine, but apparently the last time Time Machine backed up more from my disk than can fit on my disk! It seems having a hard disk close to full is enough to render a backup effectively useless.
Having an OSX drive that full will make your Mac extremely sluggish, cause data corruption and/or loss, apps to crash, etc.
Guess I'll have to restore from a previous backup, then manually copy the newer files. Just wanted to alert others to this insane problem, so it doesn't happen to them.
If you can get your Mac running, you need to make several GBs of space immediately.
If all else fails, reformat the internal HD and install OSX from your Snow Leopard Install disc, then use +Setup Assistant+ after the Welcome video to transfer +*most, but not all+* of your stuff from the backup. Omit the contents of one or more large sub-folders in a home folder (such as Photos, Music, or Movies).
See #19 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.

Time machine backup too large

i had a weird quirky thing happen to my computer. It crashed and when I restarted, all my login items and programs were asking me for my licenses and registration nos. as if i had just installed them. Plus all their settings went back to default. Recovering all my registration information would have taken an act of god, as my appshelf data was corrupted too. After many different recovery attempts, I scrapped it all, did one final Time Machine backup, and restored my computer from a date I knew was working (about 3 weeks earlier), using the system disk. My Time Machie backups went back nearly a year. When I was up and running, I then went in to Time Macine and brought over piecemeal new files that had been added since three weeks ago.
A couple days later, I attempted to get something from an old Time Machine backup, but now the bakups did not extend back as far, but they only went to the date I restored from 3 weeks earlier. I thought that was weird, but continued on. Later, it was only going back a couple days. Having a "working system" I thought nothing of it..but now it is telling me July 25 is the oldet backup, taking up 230.84 GB of 499.76, and any successive backup fails. Instead of incrementally backing up, Time Machie is now attemptng to do a full bnackup, requiring 250 GB, but only 230 are available. Does asnyone know it's not just backing up the changes, but attempting to backup the whole thing??

Sometimes, this error is legitimate. The user may not realize that they need to exclude additional hard disks that TM may be seeing. This is done in the “Options…” window of the Time Machine Preferences.
Nevertheless, many times this error just doesn’t make sense, stating that not enough free space exists for a backup that is clearly smaller. (“The backup requires 45.9 GB but only 182.6 GB are available”)
The answer and fix may have been discovered by a poster in the macosxhints forums: (http://forums.macosxhints.com/archive/index.php/t-84284.html)
Essentially, while Time Machine DOES delete old backups from the sparsebundle, it DOES NOT free up the space occupied by those old backups. Eventually, "all previous backups were deleted and no space was gained. . . . What appears to be going on here is that the sparsebundle isn't self-shrinking - unused bands aren't being automagically discarded."
The solution is to compact the TM backup sparsebundle in Terminal using:
hdiutil compact yoursparsebundlefilename.
He concludes, "I gained 30+gb of space on the backup volume by compacting that sparsebundle. And now TM runs just fine, since it has plenty of space."
Obviously, this is a bug in TM. It does not appear to effect everyone, and only seems to appear under certain curcumstances.
Let us know if this works for you.

Why is my Time Machine backup so much larger than the files being backed up?

Mac Mini Server 10.7.1 on a 2011 Mac Mini Server
Here are the drives on my system:
Here are the items excluded from backup:
Note that Server HD and Archive are the only non-excluded disks and the estimated backup size is 563.2 GB (this corresponds with the actual usage on those drives.
However, when I run time machine, it keeps going until by 2TB backup drive is nearly full! And that's with only a single backup instance and nothing else on the drive:
What's going on here??? If I don't backup the other external drive, the backup size doesn't blow up like this.

Just to clarify, the reason why Time Machine backups are generally small is that TM makes extensive use of hard links. symbolic links are small files that point to a different file system entry, while hard links point directly to the original file data on disk (hard links are unintuitive - they are like having multiple doors into a room, except that you can place the doors anywhere you like and still get to the room). So even though there may be dozens of backups of a disk, most of the backed-up items will only have one data source on disk, with only items that have changed needing new representations.
I suspect that when you try to backup a time machine backup, it is converting the hard links into separate on-disk representations - basically taking every pointer to a given piece of on-disk data and creating a new file from it. I'm not sure if that would be a linear or geometric size increase (it sounds like the latter), but either way it's going to get ugly fairly fast.

Time machine backup too long.

I use an ethernet connection to backup to my time capsule - wireless takes too long. I am backing up 292.6 GB onto a time capsule with 602 GB available (Airport 5.6). The backup is crawling. The time to backup shows 7 days. This has never happened before. Any ideas?
MacBook Pro
OS X 10.7.3
Thank you.

Update: The backup time is now down to 13 hours. However still incredibly slow.

Restore using Time Machine to new hard drive, but last "full" backup was 2012. how do I restore the rest of the Time Machine backups, particularily IPHOTO libraries for each user?

Restore using Time Machine to new hard drive, but last "full" backup was in 2012. How do I restore the rest of the Time Machine backups, particularily IPHOTO libraries for each user?
I entered Iphoto for my user and only photo up until 2012 were in the library. I thought the restore would do the incremental Time Machine backups too.....
Running 10.8.2

It usually means you are running Mavericks but have an earlier version of iPhoto. Open the App Store and upgrade your version of iPhoto to the Mavericks version.
The iWork apps are free with a new iOS device since 1 SEP 2013. They are free with a new Mac since 1 OCT 2013. They are also free with the upgrade to OS X Mavericks 10.9 if you had the previous version installed when you upgraded.The iWork apps are free with a new iOS device since 1 SEP 2013. They are free with a new Mac since 1 OCT 2013. They are also free with the upgrade to OS X Mavericks 10.9 if you had the previous version installed when you upgraded.
iWork and iLife for Mac come free with every new Mac purchase. Existing users running Mavericks can update their apps for free from the Mac App Store℠. iWork and iLife for iOS are available for free from the App Store℠ for any new device running iOS 7, and are also available as free updates for existing users. GarageBand for Mac and iOS are free for all OS X Mavericks and iOS 7 users. Additional GarageBand instruments and sounds are available for a one-time in-app purchase of $4.99 for each platform.

TIme Machine backup grows too large during backup process

I have been using Time Machine without a problem for several months, backing up my imac - 500GB drive with 350g used. Recently TM failed because the backups had finally filled the external drive - 500GB USB. Since I did not need the older backups, I reformatted the external drive to start from scratch. Now TM tries to do an initial full backup but the size keeps growing as it is backing up, eventually becoming too large for the external drive and TM fails. It will report, say, 200G to back up, then it reaches that point and the "Backing up XXXGB of XXXGB" just keeps getting larger. I have tried excluding more than 100GB of files to get the backup set very small, but it still grows during the backup process. I have deleted plist and cache files as some discussions have suggested, but the same issue occurs each time. What is going on???

Michael Birtel wrote:
Here is the log for the last failure. As you see it indicates there is enough room 345g needed, 464G available, but then it fails. I can watch the backup progress, it reaches 345G and then keeps growing till it give out of disk space error. I don't know what "Event store UUIDs don't match for volume: Macintosh HD" implies, maybe this is a clue?
No. It's sort of a warning, indicating that TM isn't sure what's changed on your internal HD since the previous backup, usually as a result of an abnormal shutdown. But since you just erased your TM disk, it's perfectly normal.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
2009-07-08 19:37:53.659 FindSystemFiles[254:713] Querying receipt database for system packages
2009-07-08 19:37:55.582 FindSystemFiles[254:713] Using system path cache.
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 309.5 GB excluded items size: 22.3 GB for volume Macintosh HD
No pre-backup thinning needed: 345.01 GB requested (including padding), 464.53 GB available
This is a completely normal start to a backup. Just after that last message is when the actual copying begins. Apparently whatever's happening, no messages are being sent to the log, so this may not be an easy one to figure out.
First, let's use Disk Utility to confirm that the disk really is set up properly.
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the Format must be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac.
If any of this is incorrect, that's likely the source of the problem. See item #5 of the Frequently Asked Questions post at the top of this forum for instructions, then try again.
If it's all correct, perhaps there's something else in your logs.
Use the Console app (in your Applications/Utilities folder).
When it starts, click +Show Log List+ in the toolbar, then navigate in the sidebar that opens up to your system.log and select it. Navigate to the +Starting standard backup+ message that you noted above, then see what follows that might indicate some sort of error, failure, termination, exit, etc. (many of the messages there are info for developers, etc.). If in doubt post (a reasonable amount of) the log here.

HT201250 Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in and if so, do I really need all the old backups on my smaller ext

Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in and if so, do I really need all the old backups on my smaller external drive?

50maz wrote:
Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in
Yes, it will do a full backup.
and if so, do I really need all the old backups on my smaller external drive?
Only if you want to be able to go back in time to those previous Time Machine backups. When you plug in the new larger external drive, you will only be able to go back as far as the first day you plugged it in and ran the first Time Machine backup on it.

Used Time Machine Backup Today- Now This backup is too large for the backup

Hey Everyone!
Some advice please,
My Hard Drive recently crashed. Fortunately, I've been using Time Machine. Apple Store gave me a new Hard Drive (for free), and I came home and restored to Time Machine. I am very impressed, and have lost no data or applications.
So now I have a problem. I can no longer back my hard drive, presumably because there were so many changes to the software today. I am getting This backup is too large for the backup volume. What is the easiest way to delete my old time machine backup and start from scratch with my computer in its current state? Everything seems to be working smoothly, so I don't see any reason to keep my old backups. Any suggestions? Is there any logical reason why I would keep the old backup?
Message was edited by: David Selevan

Thanks Barry!
I called Apple (had to anyway for a new OS Leopard DVD) and he had me go into Disk Utility and choose Erase Disk (as you suggested). I didn't have to do any formatting.
The next step was to go into System Preferences and select Change Disk and set it to None. After that, he had me choose Change Disk again, and select the USB drive, and click Use For Backup.
Now it's backing up the new version of my computer. Problem solved. Thank you.
After having to get an brand new Hard Drive today, I highly recommend that everyone purchase some kind of external hard drive and run Time Machine regularly. Although the backups get large, I've never experienced such a pleasant experience getting my files back after a hard drive failure. This is awesome technology. I can't believe 95% of my applications still worked.
David

Time machine backups take way too long

Greetings,
Having trouble with Time Machine backups taking way too long. (No, it's not the first backup after some momentous event, as 90% of what I read about slow backups mentions; it's _every_ backup.)
20" iMac purchased Oct 2008. OS 10.6.8. 500 GB internal hard drive. 3 TB external backup drive. Was tested at the local "Genius" Bar, but they found nothing wrong with it. The best they could do is to recommend a restore from Time Machine, and if that didn't work, start clean and reload the OS and then copy my stuff back. I don't think so. I actually did a full Time Machine restore for a different reason, and it didn't help (except that I gained a few GB of disk space!).
My Time Machine backups now take about 39 minutes to complete. I have a 500 GB internal drive and this problem happens regardless of which external drive I use. (I have 3: 2 WD hard drives and one [noisy!] G-drive.) My current backup drive is a 3 TB WD drive with 2 TB of free space.
These are small incremental backups, typically about 35 MB. It doesn't take half an hour to copy 35 MB!
All phases take a long time, but the most irritating one is where TM appears to get stuck for a long time at the beginning and end of the copying phase. For example, at one point it will say something along the lines of Backing Up 7 KB of 34.4 MB. And it'll be like that for minutes on end. Later it will say something like 35 MB of 35 MB and hang there for minutes on end. During these periods the write I/O rate will go up and down, and CPU usage will often be very high (with backupd using 90 - 100%, in addition to highly elevated System CPU usage). In one particular backup the I/O write rate for one part of it looked like a heartbeat on an EKG! I should have taken a screenshot.
At the beginning during the Calculating Changes phase, backupd is using between 90 and 100% CPU.
There is also high CPU usage during the next phase, Preparing. And the number of items being prepared is in the thousands.
It always goes in two rounds because it finds that the root directory (/) has been modified.
I've Googled and searched Mac forums and found nothing useful. I started with a new .plist file and nothing's changed.
Can anyone help? Thanks!
I wrote the above Jun 28. Yeah, finally getting around to posting it. Since then it's gotten worse. I now do a manual backup once a day and it takes almost an hour. I tried re-indexing Spotlight. No good.
Can anyone help? Again, this is not a "first backup." It is _every_ backup.
Thanks!
AEF

Thanks for your efforts. Here are my answers, comments, and further info:
I believe I have repaired permissions on my drive as part of my troubleshooting. And I'm sure I checked SMART status, which came up with a thumbs up, so to speak. I'm trying again. I don't see any useful messages in any logs on the console. I'm looking at "All Messages" and there is so far nothing useful. Oh, I think you must mean repair as in "Repair Disk," not "Repair Disk Permissions." I believe the "genius" at the Apple store did that or something just as good. The machine checked out fine according to them.
Checked SMART status just now: passed. Ran Quick Drive Test: also passed.
Oh, I installed "Time Machine Buddy". Occasionally, and only occasionally, I get a "deep traversal needed message" like this (I copied this from .Backup.log):
Running preflight for "Macintosh HD" (mount: '/' fsUUID: BF606E9A-5FD0-3B92-8D76-33DC63E7B2B1 eventDBUUID: 30DD929D-8982-46C2-BAE6-F0BD1E73916A)
        Scanning nodes needing deep traversal
        Node requires deep traversal: /Users/alanfeldman/Pictures/iPhoto Library/Database/apdb reason:contains changes|must scan subdirs|fsevent|missed reservation|
        Calculating size of changes
        Should copy 2919 items (27.8 MB) representing 7116 blocks of size 4096. 546805181 blocks available.
Preflight complete for "Macintosh HD" (mount: '/' fsUUID: BF606E9A-5FD0-3B92-8D76-33DC63E7B2B1 eventDBUUID: 30DD929D-8982-46C2-BAE6-F0BD1E73916A)
Time elapsed: 1 minute, 39.000 seconds
But the vast majority of the time I do NOT get this message. But if there's something wrong with this apdb file, what can I do to fix it?
Note that there is usually, if not always, a lot of CPU activity or I/O (disk) activity, but not a lot getting done.

How much should I partition for Time Machine/Backup?

Hi all,
I upgraded my PB G4 HD to a 160GB recently and have just purchased a 1TB External HD. How much should I partition in the external to be used for Time Machine backup purposes of my internal HD? Will the same size suffice, or should I allocate more?
Also, I was thinking of formatting the drive so that it's both Windows and OS X friendly, but that means formatting it to MS-DOS something (I was just reading about it in another thread), will that cause any issues for the partition for Time Machine that I created? Thanks.

Also, I was thinking of formatting the drive so that it's both Windows and OS X friendly, but that means formatting it to MS-DOS something (I was just reading about it in another thread), will that cause any issues for the partition for Time Machine that I created? Thanks.
That's not practical. If you want to use the hard drive on a Windows machin while still being useful for Time Machine you should use MacDrive.
I upgraded my PB G4 HD to a 160GB recently and have just purchased a 1TB External HD. How much should I partition in the external to be used for Time Machine backup purposes of my internal HD? Will the same size suffice, or should I allocate more?
I would make the partition at least twice the size of the internal drive. Preferably, you would want 50 GB for a Leopard install that includes just the base operating system so you can boot off the 50 GB to recover your Time Machine data if your Leopard installer disc ever becomes unusable.
Also since you have a Powerbook, your 1 TB hard drive should be Firewire. USB will not boot Powerbooks. If it is USB only, you can remove the external hard drive case and replace it with one compatible with the drive inside that case from http://www.macsales.com/ that has Firewire.

Time Machine: Backup is too large and I have space on my Time Capsule !

Hi Everybody,
I am using Time Machine with my 1T Time Capsule. Everything was running nice till I get message telling that backup could not complete because there was an error copying backup files. I searched for solutions, erased TM disk, reset TM, and reset TC too. Now I have 937g available on TC, I tried to backup 63g but a message came out telling that backup is too large !
Any ideas please !?

Hi
The backup failed too !
These are the messages from the console:
Apr 2 11:53:12 hussain-almarshoods-macbook kernel[0]:
Apr 2 11:53:42: --- last message repeated 1 time ---
Apr 2 11:54:10 hussain-almarshoods-macbook com.apple.backupd[413]: Stopping backup.
Apr 2 11:54:10 hussain-almarshoods-macbook kernel[0]:
Apr 2 11:54:27: --- last message repeated 1 time ---
Apr 2 11:54:27 hussain-almarshoods-macbook com.apple.backupd[413]: Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Originals/2010/2010-03-272/IMG0687.JPG to (null)
Apr 2 11:54:31 hussain-almarshoods-macbook com.apple.backupd[413]: Copied 168977 files (58.2 GB) from volume Macintosh HD.
Apr 2 11:54:31 hussain-almarshoods-macbook com.apple.backupd[413]: Copy stage failed with error:11
Apr 2 11:54:37 hussain-almarshoods-macbook com.apple.backupd[413]: Backup failed with error: 11
Apr 2 11:54:40 hussain-almarshoods-macbook [0x0-0x11011].com.tomtom.HOMERunnerApp[135]: Notifying device changed
Apr 2 11:54:42 hussain-almarshoods-macbook com.apple.backupd[413]: Ejected Time Machine disk image.
Apr 2 11:54:42 hussain-almarshoods-macbook [0x0-0x11011].com.tomtom.HOMERunnerApp[135]: Notifying device changed
Apr 2 11:54:42 hussain-almarshoods-macbook com.apple.backupd[413]: Ejected Time Machine network volume.
These are from TM buddy:
Starting standard backup
Attempting to mount network destination using URL: afp://Hussain%[email protected]/Hussainz
Mounted network destination using URL: afp://Hussain%[email protected]/Hussainz
Disk image /Volumes/Hussainz-1/Hussain Almarshood’s MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Backup content size: 67.9 GB excluded items size: 3.8 GB for volume Macintosh HD
No pre-backup thinning needed: 76.92 GB requested (including padding), 874.08 GB available
Copied 3.6 GB of 64.1 GB, 152 of 620764 items
Copied 7.3 GB of 64.1 GB, 31990 of 620764 items
Copied 9.7 GB of 64.1 GB, 143329 of 620764 items
Copied 13.3 GB of 64.1 GB, 151861 of 620764 items
Copied 17.3 GB of 64.1 GB, 153066 of 620764 items
Copied 20.9 GB of 64.1 GB, 154141 of 620764 items
Copied 25.0 GB of 64.1 GB, 154854 of 620764 items
Copied 29.3 GB of 64.1 GB, 155711 of 620764 items
Copied 33.7 GB of 64.1 GB, 156613 of 620764 items
Copied 38.0 GB of 64.1 GB, 157522 of 620764 items
Copied 42.2 GB of 64.1 GB, 159199 of 620764 items
Copied 46.3 GB of 64.1 GB, 160927 of 620764 items
Copied 50.7 GB of 64.1 GB, 161025 of 620764 items
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Data/2010/2010-03-273/IMG0128.jpg to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0112.JPG to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0115.JPG to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0123.JPG to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0125.JPG to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0136.JPG to (null)
Error: (-36) SrcErr:YES Copying /Users/s9am8/Pictures/iPhoto Library/Modified/2010/2010-03-273/IMG0137.JPG to (null)
Copied 54.6 GB of 64.1 GB, 168977 of 620764 items
This is the TM message:
http://img.skitch.com/20100402-mmjqp1ecca6f1mukn1aggp4uw6.jpg
I this the problem is that there are still some corrupted(damaged) photos in the iPhoto library? Is that right?
Do I have to verify the internal HD ? or find a way to delete the iPhotos files "which I do not want them thou"?
OR you have other method?
Thanks

Time machine backups too much

Similar Messages

Maybe you are looking for