Time Machine Backups are stuck in my trash...

OK, benefit of hindsight. NEVER try to delete Time Machine backups by putting them in your trash. That aside... I did that. So... How the **** do I get them out?
- without having to format the drive Time Machine is on... (this is full of other files)
- I don't mind deleting all my backups...
- Have tried emptying trash in every conceivable way inc. using Clean My Mac
Somebody? Anybody?

Try restarting and then emptying.
Try holding down the option button while trying to delete the Trash. If that doesn’t work, here is some more information.
Trash – Error Code 8003
Trash Permission Error
Trash Permission Error (2)
Trash Can’t Empty – Big Files
Trash – Can’t Empty or Move File To Trash
Trash – Empty When File is Locked or in Use
You also might want to un-install CleanMyMac. Those type of programs can ruin your system by deleting necessary files.
Myth of the Dirty Mac
CleanMyMac - Uninstall
CleanMyMac2 Un-install

Similar Messages

Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks

Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr...

I deleted my Time Machine backups using Finder, now the trash won't empty

Hello
I've just been to the Apple genius bar and thought this was solved, there the trash emptied no problem. But I realized that the problem has to do with two external drives that have time machine backups on them. I deleted some of the older back ups because my drive was filling up and I didn't see any other way to delete them.
Now they can't be reinstated back where they were, and the trash won't empty using any method. I've even tried the Terminal SUMO methods on here and other sites, and the Trashi It app, and Cocktail app - nothing works.
The only solutions I've found say to wipe your back up drive completely and start over but that is NOT an option as I have ALL of my photos on there. I use my external drive for my images (I am a photographer) and use time machine to back up my MacBookPro onto there as well. I had no idea deleting those was going to be an issue. Now I've tried to delete other things on both external drives and they are all stuck in the trash.
Someone please help!

photogirl67 wrote:
I use my external drive for my images (I am a photographer) and use time machine to back up my MacBookPro onto there as well.
Not a good idea, as you've learned the hard way.
And especially bad in the same partition, as you can't just erase the TM partition.
Plus, how do you back up the images?
For best results, consider getting another external HD; one for the images, and one for TM. Then you can have Time Machine back up both your Mac and the external. See Time Machine - Frequently Asked Question #32 for details and considerations.
But my question for Pondini is this - if I use that command will it erase that entire drive, or just the trash on it?
Just the trash folders. I've reworded those instructions a bit, hopefully more clearly and safely, and put them in #E6 of Time Machine - Troubleshooting.

File Sharing drops regularly, Time Machine Backups are delayed on OSX 10.7.3. Solution?

Hi there folks,
I'm having an issue with the new 10.7 server. We're running 10.7.3 Server on an Late 2006 XServe with 10GB RAM , connected to a Drobo Pro for Time Machine Backups of our 50+ users via our internal network.
Recently, Time Machine backups have been getting delayed, stating that they can't connect up to the backup drive (which is out Drobo Pro handling 16TB of space). The Drobo Pro hass not unmounted, and all the IP Addresses coming from and going to the Server handling the backups will still ping.
We've also be having trouble with Server resident drives and shared folders that people can mount using the ⌘+K shortcut or "Connect to Server" option in finder. People will choose the IP address, and finder will think for a few minutes then give an error stating that it cannot connect the the specified IP. The only way I can reestablish connection to the file sharing through a remote computer is to remote or physically login to the server, then go into System Preferences and turn "File Sharing" off, then on again. After that, the ⌘+K on a remote machine can find the drives again.
It's driving me crazy why this is ocurring. I don't know why, and people in the office are beginning to complain that they can't access certain files on the servers or are worried because their backups are not completeing.
It should also be known that a majority of the machines we have in the ofice are still running 10.6.8, with only a handful on 10.7, as we haven't had the time to make the major switchover yet.
I'm not the best when it comes to server software or Unix CLI managment (the office outsourced our Network Admin to the east coast), so I'm a bit stumped.
Does anyone have any suggestions to try? Is there a link between the number of Time Machine Users and the connection failures? Should I just tel the NetAdmin to create a script that will restart the File Sharing protocol on the server every couple of hours?
Hopefully someone will be able to help.
Thanks,
JYHASH

I started having connectivity issues to my 10.6.8 server from my 10.7 client immediately after updating the client to 10.7.3. FWIW. Takes forever to connect, when it does. After just milliconds before.

How can I tell if my Time Machine backups are encrypted?

Hi - I would really appreciate it if someone could help me find out if my Time Machine backps are actually encrypted.
I know that there is an 'encryption' option when choosing a disc for Time Machine to backup to, but the problem is I cannot remember whether or not I actually ticked it (as it was a couple of years ago).
Other info that might be helpful:
- The disk I use Time Machine to backup to is actually a Apple Time Capsule
- I do have FileVault2 enabled on my mac
- I have never encrypted the Time Capsule disc itself (via Disk Utility or anything similar)
- One possible clue might be: When I go into Time Machine preferences, and click on 'Select Disk...' (as if to choose another disk to back up to), and select the disc that Time Machine currently backs up to (i.e. the Time Capsule disc), it does show an 'Encrypt backups' checkbox at the bottom of the window... however this checkbox is unchecked and also greyed out.
Thanks in advance
a_quinn

a_quinn wrote:
- Because I originally created this Time Machine Backup (to the Time Capsule) back in my 'OS X Lion' days,
I wondered; you posted in the Mountain Lion forum, but your profile still says Lion.
that means that my backups now (and moving forward) will continue to be un-encrypted
Correct (as of now, anyway). You cannot encrypt existing network backups. I doubt that will be available in the future, and would take forever.
- The only way to encyrpt my backups now, moving forward, is to remove this Time Capsule disc (from Time Machine Preferences), and start all over again ensuring that I check the checkbox next to 'Encrypt Backup' when selecting the Time Capsule's disc to backup to.
Well, in theory it's possible, but would take forever, squared.
You could archive the TC's contents to a USB drive connected to it, per #Q6 in Using Time Machine with a Time Capsule).
Then delete the original, start a backup with encryption, and as soon as the encrypted sparse bundle is created, cancel the backup.
Mount the sparse bundle, open the disk image, and delete the Backups.backupdb folder inside it.
Connect the USB drive to your Mac, mount that sparse bundle, open its disk image, and copy the Backups.backupdb folder to the one on the TC.
Depending on how large the sparse bundle is, that could easily take a couple of days, at least, even connected via Ethernet.
Just for testing one day, I encrypted a very small set of existing test backups on a F/W 800 drive - 6 dated backups using a whole 12 GB. Took an hour.
An alternative would be, just do the "archive" and keep the USB drive "on the shelf" for a while. You can always connect it to your Mac and access those backups via the Browse Other Backup Disks option.
Trying to keep a couple of years worth of backups usually isn't a good idea. It's a very complex structure, so the odds of damage increase, it takes much longer to populate the TM browser, and it works slower and slower, and if you didn't need something for 6 months, are you really going to need it in 2 years?

After Server 4.1 update, Time Machine backups are huge

Hi,
After updating to Server 4.1, every one of my Time Machine backups for the machine (Late 2012 iMac) running OS X Server (which is backed up to a USB connected drive) is between 3GB and 7GB. When a backup finishes, I can immediately force a manual backup and it's >= 3GB.
Using the timedog utility, I narrowed the problem down to the OS X Server install, the largest file being:
/Library/Server/Wiki/Logs/postgres-xpg.log
Every 10 seconds, an entry similar to the following is added to this file:
2015-04-16 23:04:31 XPG.5941: matched path for pg_receivexlog file: /Library/Server/Wiki/Database.xpg/backup/000000010000006300000035.partial
This particular log file is around 3GB in size. It appears to have every log entry since I installed OS X Server December 2013. I find it odd this is happening in the Wiki directory as the Wiki service is disabled. I am using the following services:
Caching
Calendar
Contacts
File Sharing
Time Machine (for my Macbook backups)
I went into Time Machine (on the iMac) and deleted all the backups for /Library/Server/Wiki and that freed up 160GB. I could just exclude that from backups, but I don't want to do that. I would like to know why these entries keep getting put into that log and also why, if those entries are appropriate, the log is not rotated.
Any help would be appreciated!
Thanks, Patrick

Hi Patrick,
That particular log-file has had an issue for some time now.
Even when the wiki is not loaded the wiki proces generates errors which keeps on filling this log.
Exclude it from the backup simply solves your backup issue.
However there are some suggestions for "fixing" this enormous log around in the Apple Support Community.
I don't worry too much about it anymore, but you can generate a new file and throw out the old for instance.
As long as you have enough storage you're fine.
Some usefull steps for a fix are mentioned here:
http://apple.stackexchange.com/questions/113837/library-server-wiki-database-xpg -consuming-huge-amount-313gb-of-disk-space
Goodluck
Jeffrey

My Time Machine backups are significantly larger, and slower, over WiFi than Ethernet

My regular hourly backups from my Time Capsule began acting up a month ago. They were abnormally large (25-100 MBs) and took a long time--once, six hours.
I connected my Time Capsule to my MacBook Air through ethernet to repair the disk through Disk Utility, (I turned Airport off on the Air, but not the Time Capsule), and then to rebuild the Spotlight index for the Time Capsule.
Backups over ethernet work just fine now. The backup will happen in two parts, of around 200 KB each, and take two or two and a half minutes. But when I turn Airport on the Air back on, reconnect to the WiFi network, unplug the ethernet cable, and immediately start a new backup over WiFi, the two parts balloon to around 20 MB each, and the backup takes hours.
This is a backup over ethernet, which took 2 minutes, 21 seconds:
Starting standard backup
Attempting to mount network destination using URL: afp://Martin%[email protected]/External%20HD
Mounted network destination using URL: afp://Martin%[email protected]/External%20HD
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/External HD/Martin Fox’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
No pre-backup thinning needed: 1.70 GB requested (including padding), 733.41 GB available
Copied 1082 files (104 KB) from volume Macintosh HD.
No pre-backup thinning needed: 1.70 GB requested (including padding), 733.41 GB available
Copied 429 files (153 bytes) from volume Macintosh HD.
Starting post-backup thinning
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Martin Fox’s MacBook Air/2012-05-11-225349: 733.41 GB now available
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Martin Fox’s MacBook Air/2012-05-11-200538: 733.41 GB now available
Post-back up thinning complete: 2 expired backups removed
Backup completed successfully.
Ejected Time Machine disk image.
Ejected Time Machine network volume.
This is the second backup after that one, done over WiFi. (The first was incompletely recorded by Time Machine Buddy, but took around half an hour.) It took 1 hour, 54 minutes, 50 seconds:
Starting standard backup
Attempting to mount network destination using URL: afp://Martin%[email protected]/External%20HD
Mounted network destination using URL: afp://Martin%[email protected]/External%20HD
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/External HD/Martin Fox’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
No pre-backup thinning needed: 100.0 MB requested (including padding), 733.41 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Copied 26 KB of 20.6 MB, 98 of 98 items
Copied 1485 files (22.0 MB) from volume Macintosh HD.
No pre-backup thinning needed: 1.72 GB requested (including padding), 733.41 GB available
Error: (-8084) SrcErr:YES Copying /Users/foxmarti/Library/Application Support/Firefox/Profiles/ehjqi949.default/places.sqlite-wal to (null)
Copied 1941 files (27.5 MB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
Eject

slyfox1908 wrote:
I live in an apartment building so there are a number of WiFi networks around.
Not to mention cordless phones, microwaves, etc., any of which can interfere.
On iStumbler, my network shows up twice--once on channel 149, with signal strength of 50-65% and noise of 15%--and again on channel 10, with signal strength of that wildly varies from 20% to 90% and noise of 20%. Other networks in the building are on channels 1, 2, 6, and 11. The graph of channel 149 is very smooth, while the graph of channel 10 is choppy.
It's probably using 149, as those numbers are pretty good. Press Alt/Option before clicking the Airport icon in your menubar to see which band it's using.
Watch the band it's using while running a backup. Try other channels in the area of 149. Unfortunately, it's a bit of a "hit and miss" thing.
Why are there two networks? Is that part of the problem? My Time Capsule is located about three feet right and a foot below my desk, so I can't think of a reason why it wouldn't be 100% for both channels.
It's a dual-band router. As I understand it, OSX will pick the best signal.
I really want to know I have a clean, safe, accessible back-up before I replace it though. Right now I don't trust the Time Capsule.
Do at least your last backup via Ethernet.

How can I delete time machine backup folders moved into the trash from an external drive?

I made the mistake of moving Time Machine backup files into the trash, but I can't seem to delete them. I tried the option key when clicking on "Empty Trash" and "Secure Empty Trash" (before and after rebooting), but that always led to error 8003. The files won't allow me to change their name. Using approchaes to Terminal from three different Mac-related webpages also failed. I also tried Trash It, but it seemed to be making little progress after letting it run 48 hours. Any other suggestions before calling Apple?

Assuming these were not backups made over a network (thus not in a sparse bundle disk image), see #E6 in Time Machine - Troubleshooting.
But any way you empty the trash on that disk/partition is probably going to take a very long time -- there's no doubt several hundred thousand files there, perhaps a million or more.
You may have to just erase the disk (with Disk Utility) and start over.
You really shouldn't have to delete Time Machine backups, as it will do that automatically when the destination gets full. But if you really want to, see #12 in Time Machine - Frequently Asked Questions.

Can't get old time machine backups to delete from the trash can

time machine backups won't delete from my trash can

You shouldn't be deleting old Tima Machine backups. When TM runs out of space it automatically deletes the oldest backups to make rioom for the new
http://pondini.org/TM/12.html

Time Machine backups are bigger than expected

Hi everyone,
I was wondering if anyone would know why, all of a sudden after a day or two ago, my Time Machine is suddenly insisting on backing up well over 4GB at a time? Before then my backups would almost always be below the 100MB mark. Has some update happened that would have caused this?
I have looked in Console but unfortunately am none the wiser. Is there some way of finding out a list of the files Time Machine is actually backing up? If so then I'd be able to track down this problem since I am fast running out of space on my Time Machine backup drive!
Many thanks for listening...
:-Joe

Jowie,
Consider the following info that I have gleaned, some of it may explain some it.
*Incremental Backups Seem Too Large!*
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” (http://discussions.apple.com/thread.jspa?threadID=1209412)
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer may be describing what you are experiencing: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder it you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.

HT201250 Time Machine backups are extremely slow

Time Machine backups filled an older, smaller external HD, began deleting oldest files. TM backups began to be very slow, I assumed because of the deletion of older files. I replaced external HD with a new LaCie 3.0TB external HD (p9233). Backups are still very slow, take a very long time. It appears TM is backing up all files each time it runs - literally hundreds of thousands of files each backup when only a few files should have changed from one hour to the next. I have tried on and off as well as setting up TM anew, nothing seems to affect time and speed. Any help?

Sunnyside77 wrote:
... Any help?
See Pondini’s excellent Information Here...
http://pondini.org/TM/Troubleshooting.htm

Time Machine backup gets stuck - Please help

Hi all,
I'm backing up my MBP via ethernet to a Time Capsule. The incremental backups take forever and are driving me nuts. The backups seem to be getting stuck midway. The disk sounds like it's spinning but the progress bar doesn't move. Also, it seems to be copying over too many files every hour, like >60000 or so (log below). I doubt that so many files get modified every hour.
I've tried everything (I could think of and find on the discussion boards) like deleting the sparsebundle, deleting the entire backup drive, playing with the backup frequency, nothing works.
Please help!!
Thanks,
DB
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd[7045] Starting standard backup
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd[7045] Network mountpoint /Volumes/TC Backup Disk not owned by backupd... remounting
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd[7045] Network volume mounted at: /Volumes/TC Backup Disk-1
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd[7045] Disk image /Volumes/TC Backup Disk-1/Dhiren's MBP_002332d43774.sparsebundle mounted at: /Volumes/Backup of Dhiren's MBP
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd[7045] Backing up to: /Volumes/Backup of Dhiren's MBP/Backups.backupdb
11/27/08 10:04:39 PM /System/Library/CoreServices/backupd[7045] No pre-backup thinning needed: 570.5 MB requested (including padding), 426.79 GB available
11/27/08 10:14:44 PM /System/Library/CoreServices/backupd[7045] *_Copied 87124 files_* (20.3 MB) from volume Macintosh HD.
11/27/08 10:14:48 PM /System/Library/CoreServices/backupd[7045] No pre-backup thinning needed: 559.1 MB requested (including padding), 426.69 GB available
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd[7045] Unable to rebuild path cache for source item. Partial source path:
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd[7045] Error: (-39) SrcErr:YES Copying (null) to (null)
11/27/08 10:15:14 PM /System/Library/CoreServices/backupd[7045] Copied 1067 files (10.6 MB) from volume Macintosh HD.
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd[7045] Starting post-backup thinning
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd[7045] No post-back up thinning needed: no expired backups exist
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd[7045] Backup completed successfully.
11/27/08 10:15:26 PM /System/Library/CoreServices/backupd[7045] Ejected Time Machine disk image.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd[7045] Ejected Time Machine network volume.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd[7045] Ejected Time Machine network volume.
Message was edited by: dhiren9

The indication that the backup completed successfully is the best evidence that it did. If you want something more explicit, you can proceed as below.
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.
Drag or copy — do not type — the following line into the Terminal window, then press return:
sudo tmutil compare
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
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.
Files that you’ve excluded from backup, or that are excluded automatically, are ignored.
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.

Oldest time machine backups are inaccessible

Hi everyone,
I'm running 10.6.1 and have had no problems with Time Machine until recently. My Time Machine has an Oldest Backup of July 28, 2009. It's Latest Backup was done today just an hour before this posting. My problem is, I can access all of my backups except for my oldest backups starting from July 28, 2009 and a few days after that. The most recent ones I can access are from October 4, 2009. The dates are listed on the Time Machine 'sidebar', where you can see dates for all of the backups you have. The problem is, my July backups are grey'd out. The ones that are available are a more vibrant gray with a highlight and those I can take action/view/restore from.
What are some possible things I can troubleshoot this problem with as I'd really like to get my hands on my oldest backups?
Just to further note, my Time Machine still has 185GB available on it. So it's not like it has run out of disk space and had to delete my oldest backup.
Thanks all.
Message was edited by: Steve Finkelstein

Steve Finkelstein wrote:
Thanks Pondini, tip #E2 did the trick. I had to option click TM in the menu bar and select a different disk. I didn't realize that the backups deviated from each other at that point in time. It makes sense because that's around when I installed Snow Leopard.
Appreciate the tip+answer!
Cool! That really shouldn't happen, but sometimes TM has a mind of it's own!
Glad it's sorted out, and thanks for the star!

Time Machine backups are LARGE

Practically every time TM is backing up, it is a LARGE backup, like 12.2 GB or 11.7GB. Then, sometimes it will be a 1.7 MB backup that takes 8 minutes going 1 KB/second or so.
Ant input would be appreciated.

I have been having the same problem with my backups. I have two 1 TB external HD's in addition to my 185 GB internal HD. I use one of the TB HD's to store alot of my media fies (along with other things). I use the second TB HD as my time machine volume (back's up my internal HD and the other TB HD.).I've been spending all day trying to figure out why my hourly backups were reaching sizes as large as 39 GB when I hadn't added any new data to my computer. I have been using PARALLELS all day and now I'm hoping that that is what is causing my hourly backups to be as large as they are. Does anyone have any suggestions as to what I should do if anything?

Upgraded to snow leopard and now all my time machine backups are gone

Could this be related to the upgrade? This backup is fine as I have nothing to recover, but I don't understand why time machine won't perform an incremental backup. There are 340GB on the disk with 160GB available. The error message I receive is "This backup is too large for the backup disk. The backup requires 275.15 GB but only 160.90 GB are available." Shouldn't back up just be making an incremental backup (erasing GBS?)

Christine Rios wrote:
Could this be related to the upgrade? This backup is fine as I have nothing to recover, but I don't understand why time machine won't perform an incremental backup. There are 340GB on the disk with 160GB available. The error message I receive is "This backup is too large for the backup disk. The backup requires 275.15 GB but only 160.90 GB are available." Shouldn't back up just be making an incremental backup (erasing GBS?)
Normally, yes. How did you do the upgrade? If you erased your HD, installed Snow Leopard and used +Setup Assistant, Migration Assistant,+ or just drag & drop to restore your data, everything on the disk is considered changed, so Time Machine must do a full backup.
The 275 GB figure includes about 20% for workspace, so the estimated size of the actual backup is about 230 GB.
If that's a full backup, see #D3 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum) for the common causes.
If it's not a full one, see #D4 there.

Time Machine Backups are stuck in my trash...

Similar Messages

Maybe you are looking for