Problem with Time Machine backup (Snow Leopard)

Hello everyone.
So today I was doing a backup and my external hard drive fell off the tabel and disconnected itself mid-back up. Now I am getting this error when I attempt to do the backup again,
"This backup is too large for the backup disk. The backup requires 349.79GB but only 319.30GB are available."
This is understandable, except for the fact that my HD on my MPB is only 320BG.
I tried look online and I read that I should try to reset Time machine by deleting the File, com.apple.TimeMachine.plist. I tried to look, but this file does not exist on my computer.
Does anyone have any ideas as how to fix this?
Any help would be greatly appreciated.
Thank you.

BDAqua wrote:
The great Pondini seems to be the resident TM master... I don't use it & consider it the worst Backup outside of no backup at all, but check this out...
http://web.me.com/pondini/Time_Machine/Troubleshooting.html
Hi,
Just for future reference, I've moved my site to http://pondini.org, since Apple is dropping web hosting in June.
Both sites are active now; after a few days, I'll put redirect notices on the old one, then leave it there until it goes "poof."

Similar Messages

Problem with Time Machine, running Snow Leopard

Hi all,
Last week I had a new hard drive fitted into my iMac 8,1, after which Snow Leopard was reloaded (10.6.3 from the disc, updated to 10.6.8), followed by the restoration of data via Time Machine from my external hard drive. Whilst my Mac is now running beautifully, I am having problems backing up with Time Machine.
When I run a backup, it prepares about 100,000 items, then starts to backup, usually about 650mb. It crawls along in kb until it gets to about 1mb, then jumps quickly to the end, but then it adds extra mb on the end. Then it suddenly starts again "preparing x items....." and off it goes again.
I have tried repairing the backup disc, and it appears to be ok. I even erased it and started again. Time Machine did a full backup (139gb) in about 2 hours, then immediately added another 640mb at the end - strange, but I do at least have a full backup from yesterday. But now, everytime I run backup, it looks for the same sort of figure (650-700mb) and then goes round in circles.
Any help would be very much appreciated!
Thanks, David

Hi Eric
Thank you for your reply. Here are the screenshots for each change:
Having prepared about 95,000 items, the backup of 612mb begins
14 minutes later a message appears
Another 3 minutes and another message. You will see from this screenshot that the backup figure has changed to 613.1mb
Another 30 seconds and it all begins again....
And finally, 7 more minutes pass, another 96,000 items are prepared, and another 604.8mb backup begins.
I might add, that between posting this morning, and your reply, I also went into disk utility, chose the top leve of the external drive, clicked on the partition tab, charged current to 1 partition, renamed the drive, erased it, and did a full back up of 139GB. After 137GB it started again, looked for 602mb, backed them up and finished the backup, which is why TM states that the last back up was at 18:16 today.
Thanks again
David

Backing up an encrypted drive with Time Machine under Snow Leopard

In a nutshell, my question is “Can I back up an encrypted drive using Time Machine under Snow Leopard, and if so, how do I access its data from a previous day?”
I have a 1Tb USB drive connected to my MacBook, which runs Snow Leopard. The drive is formatted as Mac OS Extended (Journaled). This drive is included in the drives that Time Machine backs up. I used Disk Utility to create an encrypted drive on the USB drive (998Gb), also formatted as Mac OS Extended (Journaled). The encrypted drive is not on TimeMachine’s list of excluded files/drives.
When I go into Time Machine, I can see the USB drive and the encrypted drive in the side bar. I can access the files on the encrypted drive as long as I’m looking at how it stands now. But if I move backward in time, the encrypted drive is grayed out and inaccessible. If I click on the USB drive, I get a window that tells me it is 75.9Gb in size, and nothing else is available to me.
When I open the back-up drive in Finder and navigate to Backups.backupdb > macbook name > some date and time, I see my MacBook’s hard drive and the USB drive. The encrypted drive is not shown. When I click on the USB drive, I see an entry for drivename.sparsebundle. When I click on that I’m prompted for the password for the encrypted drive. When I enter it, I get a warning telling me that the disk image could not be opened and that the encrypted drive has no mountable file systems.
Is my encrypted drive really be backed-up and if so, how do I access the backed-up data?

Having received a bunch of views but no replies over the last 5 days, I decided to venture into my local Apple store and ask this same question. The response I got from the geniuses was that you can't get a reliable back-up of an encrypted drive using Time Machine under Snow Leopard. So, my only alternative is to copy the encrypted drive's contents elsewhere, unencrypt the drive, and then copy the contents back. This is what I expected, but not what I wanted to hear.

Problem with Time Machine Backup or Maybe Not Time Machine

The problem manifests after a Time Machine backup.
I have an iMac 24-inch, Early 2008. iMac 8,1
Intel Core 2 Duo, 4GB RAM.
Last week I purchased two 4-Terabyte G-technology G-Drives. Each drive is equip with FireWire 800 and USB 3.0/2.0. In general use they seem to work fine on the iMac.
I designated one drive as a Time Machine Volume. This is where the problem happens.
Time Machine will do the initial backup just fine. Then it runs once per hour with no problem. Intermittently however, Time Machine will fail and report :
“Time Machine couldn’t complete the backup to “hard disk name”.
Unable to complete backup. An error occurred while creating the backup folder.”
Interestingly enough if I try to open a folder on the Time Machine volume using the Finder I get:
“The operation can’t be completed. An unexpected error occurred (error code -50).
If I try to eject the volume I get the irksome “Cannot eject volume because it’s currently in use by one or more programs.”
To resolve this I’ve tried everything, from the banal verifying permissions, to swapping the two G-Drives around, swapping out all the cables, etc.. When the error occurs I go into the shell and check with lsof and always find no software apparently holding or using that volume.
Very frustrating
I can force eject the volume, then remount the volume and things are back to normal. Same with restarting.
This happened under OS X Mountain Lion and is now happening under a clean install of Mavericks.
I thought that even though I don’t see any MDS related processes using the drive, it might be spotlight, so I told spotlight not to index the volume. Problem still happens.
I’ve found that one person had almost this exact same problem at:
https://discussions.apple.com/thread/4756742
His solution turned out to be replacing the G-Drive with another brand new G-Drive.
Unfortunately, I cannot return the drives to the Apple store because the boxes were tossed out. I also don’t relish trying to explain that the drives work just fine until some glitch that occurs either just before or just after a Time Machine backup.
Does anyone have any suggestions?

You can also contact G-Drive while the drives are under warranty (one year I believe).
I have the same problem using Time Machine with the 2T G-Drive and my MacBook Pro. G-Tech emailed me a Firmware Update Utility app and, when that didn't solve the error message problem, they sent me a replacement drive and new cables, twice. The problem persisted; I get one or two backups each day and then the error message. I also can't copy anything to the drive and have to force eject it, so G-Tech suggested I see how well it worked with the USB cable.
Time Machine works flawlessly with the USB cable and the G-Drive, so G-Tech suggested it is a problem with my Firewire 800 port. I worked with Apple Care over the phone, doing all the tests suggested in Eric's post - testing with Disk Utility, Time Machines interface with my User Accounts, the Operating System, then resetting Time Machine, etc. and then I took it to the Genius Bar so they could run the tests themselves. All looked like it should be fine (but they were using a 1T G-Drive and all testing was done within 30 minutes)...when I got home, after two good backups, I got the error message again.
Apple Care finally suggested I make a Genius Bar appointment and sit at the store working with my MacBook, the G-Drive and Time Machine running until I got the error message, to prove the only thing left that could possibly be the cause of the problem, is the port. I did this last Wednesday.
It is 9 days later and I got my computer back this afternoon...the logic board was replaced because the Firewire 800 port is attached to it...I got my first Time Machine back up at 5:34pm...and the error message again at 7:34pm.
The only solution, it seems, is to use the USB cable instead of Firewire. USB and Thunderbolt seem to be the direction Apple is taking, which is why so many people have been posting about this problem, here and elsewhere, with no real solutions from Apple. See this article: http://www.infoworld.com/t/mac-laptop/how-cope-the-end-of-firewire-205957
I hope the USB works for you too.

Problem with Time Machine backup

Hi all,
i've been really excited about Lion and managed to get it and install it in under 50 minutes!
It works great, even with my Office:Mac software, antivirus software and so on, fantastic considering other people have had issues.
The one issue I seem to have is Lion working with its own application! Namely Time Machine!
I have a 3Tb Western Digital My Book Live NAS which I bought a few weeks ago. I only use it for backing up my Macbook Pro and my Wifes Macbook and its been faultless with Time Machine, however when I try and continue running this with Lion I get an error saying;
The network backup disk does not support the required AFP features
From what I can find on the web this seems to be something to do with the NAS as apposed to Time Machine however I would have thought this would have been addressed before people like myself had the problem - After all i'm sure everyone will agree, back-ups are extremely important!
If anyone has any suggestions how I can fix this I would be greatful
Matt

HI all,
wow, thanks for all the fast replies, at least it seems i'm not the only one having these issues.
I contacted apple support about this and there suggestion was to connect the disc up to my laptop and run diagnostics on it, however as its a NAS I only have an ethernet connection so that makes it difficult to connect directly. As it is I also logged a call with Western Digital and they have come back to me with a similar comment that Alex Lui has made in this discussion, namely that it is going to be fixed but not until August time.
I've managed to sort out my back-ups all be it using Western Digitals WD Anywhere Backup software which does make me feel a little bit safer (even though its having to back up everything and says that will take approx 34 hours!)
I'd have hoped Apple would have seen this coming, especially as I would guess its not only Western Digital drives that have this incompatability, however I suppose they were up to their eyebrows with other stuff they had to sort out before they could release Lion.

Problem with Time Machine backup for multiple drives

Time Machine has the ability to exclude drives attached to the system via usb, firewire, etc. I have an external USB drive attached directly to my MacBook (not via a hub). I want to include this in my backup, so I removed it from the exclusions list under Option in the Time Machine preferences. Since I have done this, my backup to my 1TB Time Capsule stops at 128K. When I put this drive on the exclusions list or eject the drive, the backup is successful. I have tried backups over both Ethernet and Wi-Fi, and get the same results.
The files on the USB drive are important to me and I really need to be able to include them in my Time Machine backups. I would prefer not to have to get a second external drive to copy my files to as a backup. Any suggestions would be greatly appreciated.
Thank you
JDBTek

If the HFS+ USB HDD is connected directly to the MacBook, TM should be able to back it up. Sorry, I don't have any other suggestions.

Problems with Time Machine backup for two machines to one external drive

I have a brand new WD 500GB USB My Book external drive plugged into my Intel Mac Mini running 10.5.1 to use as a TM backup drive (TM reformatted it to HFS+ journaled). The Mini's connected by ethernet to the Airport Extreme. It works great. I setup my wife's MacBook Pro 17" Dual Core 2 w. 10.5.1 for TM using the Mac Mini's TM backup drive and it works fine (a little slower at 811.n wi-fi speeds, but OK). I have the Mac Mini setup in Energy Saver to shut down at night and restart in the morning. The morning after I setup my wife's MacBook Pro for TM I found a big black & white message (in half a dozen languages) on the Mac Mini saying start up failed and I need to reboot using the power button. I did and everything was cool. Now comes the problem, it's done it three days in a row so it looks like there is a problem with the TM setup. It didn't do this before I setup my wife's computer for TM.
Any thoughts on what is causing this? We've had minimal problems with Leopard setup (short of a brief hunt for an Airport Extreme Drive and a couple of network printers during initial setup).

1 mistake @ a time wrote:
I works fine over a network if the TM drive is attached to another Mac running Leopard. It won't work with an Airport drive (Apple deep sixed that feature in the final release).
We have an Airport Extreme base station, and we plan to add an Airport Express to boost the power to reach the second floor. We are ordering 4 iMacs, 20", plus I have the Macbook 13" that I have had for a few months.
We thought we could connect one large external drive via firewire cable to one of the iMacs and use it to back up all five computers via Time Machine.
Is that possible, or does everybody need their own external drive?
Thanks!
susan

Problem with Time Capsule backup

My Time Capsule is a first gen (500 GB), and I recently upgraded to Lion on my iMac. It seems like right around the time I upgraded that I started having problems with Time Machine backups. They will complete, but then the disk does not eject from my desktop. I am running the Time Capsule buddy widget, and here's the log file:
Starting standard backup
Network destination already mounted at: /Volumes/TimeCapsule
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/TimeCapsule/Stefano.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
100.0 MB required (including padding), 174.27 GB available
Copied 2353 files (2.0 MB) from volume Macintosh HD.
100.0 MB required (including padding), 174.27 GB available
Copied 1656 files (718 KB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb
Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb
Stopping backup to allow backup destination disk to be unmounted or ejected.
Backup failed because the destination disk was ejected or disconnected unexpectedly!
You can see at the end where I ejected the disk manually.

I finally resolved this. However, I had to erase the entire backup on my 3tb and start with a new backup. I connected via hardwire to make it go faster. No problems now.

Transfer time machine data (snow leopard) to new mb air (lion)

MB Pro died. How do I transfer external Time Machine backup (Snow Leopard) to new MB Air (Lion)?

Your best bet, by far, is to use Setup Assistant when your new Mac first starts up, to transfer your 3rd-party apps, user accounts, data, settings, etc. from the backups. See Using Setup Assistant on Lion for detailed instuctions.
If the backups are on a Time Capsule, get a USB-to-Ethernet connector, so you can do this via Ethernet -- it's 2-3 times faster, and much more reliable, than WIFIl.

Leopard doesn't mount the disk with time machine backup!

Hi friends. It's my first time in this forum, and I'm sorry by now for my poor english.
My problem: One week ago I had some problem with hard disk, but after a visit to an Apple center and after a replacement of my disk the problem was solved.
Now I want to restore all my file and my system preference from an external hard disk (USB LaCie 500GB) when have made a complete backup with time machine.
But Leopard doesn't mount the disk in finder or in Utility Disco. I see it only in System Profiler. I try with my old iBook with Tiger and it mount correctly the disk! It's amazing! Please Help me, I need my file on my iMac for work!
Thanks and merry Christmas!!!

Similar thing for me as well. I however haven't made a backup using Time Machine.
In preparation for Leopard, I reformatted my laptop's hard drive and installed Mac OS X 10.5.1 fresh. As soon as I plugged in my trusty 500GB external WD MyBook Pro (trying both Firewire 400 and 800 on my MacBook Pro 17"), I get the following alert:
"Disk Repair
The disk "500GB" was not repairable by this computer. It is being made available to you with limited functionality. you must back up your data and reformat the disk as soon as possible. OK"
Keep in mind, I run Disk Utility and "Repair Disk" and "Repair Permissions" religiously every week and have had no issues while running under Mac OS X 10.4.11. My other laptop running the 10.4.11 doesn't report any issues with the drive at all - only when I plug it into this one running 10.5.1.
Is there a firmware update for this drive? Is this Apple's issue? I have another LaCie Firewire drive and it works flawlessly even under 10.5.1.
Right now, I can't even use the drive as it's Read Only (due to the error).
In system logs:
Feb 9 19:02:59 Cam diskarbitrationd69: unable to repair /dev/disk4s3 (status code 0x00000008).
/dev/rdisk4s3: fsck_hfs run at Sat Feb 9 19:00:41 2008
/dev/rdisk4s3: ** /dev/rdisk4s3 (NO WRITE)
/dev/rdisk4s3: QUICKCHECK ONLY; FILESYSTEM DIRTY
/dev/rdisk4s3: fsck_hfs run at Sat Feb 9 19:00:41 2008
/dev/rdisk4s3: ** /dev/rdisk4s3
/dev/rdisk4s3: ** Checking Journaled HFS Plus volume.
/dev/rdisk4s3: ** Checking Extents Overflow file.
/dev/rdisk4s3: ** Checking Catalog file.
/dev/rdisk4s3: Incorrect number of file hard links
/dev/rdisk4s3: ** Checking multi-linked files.
/dev/rdisk4s3: ** Checking Catalog hierarchy.
/dev/rdisk4s3: ** Checking Extended Attributes file.
/dev/rdisk4s3: ** Checking volume bitmap.
/dev/rdisk4s3: ** Checking volume information.
/dev/rdisk4s3: ** Repairing volume.
/dev/rdisk4s3: ** The volume 500GB could not be repaired.
The drive is reported to be "Ok" when running Disk Repair on other machines not running Leopard. As a test, I just "upgraded" my wife's laptop to Leopard and now I have the same issue on that machine.
Help.

Can't force quit applications problem during Time Machine backups

I've run into a frustrating problem with Time Machine. I'm using an external 750gb USB hard drive as a backup disk with my Mac Mini; the connection is visa the Firewire 400 port.
When I'm doing anything that's CPU-intensive while a Time Machine is backing up, it is a 50-50 chance that one or more applications will crash. It is impossible to Force Quit them, which means that it is impossible to log out or shut down. The user is faced with a choice: Kill the whole system, and risk corrupting the system hard drive, or yank out the Time Machine disk's connector, and risk corrupting the Time Machine backup. Of course the latter is preferred, and that's what I've done. Thus far, I haven't seen any corruption on the Time Machine drive, fortunately, but in order to work with my system, I have had to disable Time Machine backups while I am working. (I reconnect the Time Machine drive overnight.)
I know from some Google searching that others are experiencing this problem. My question is, has anyone figured out why this is happening, or developed a workaround?
Regards,
Bryan

In the process of restoring my MacBookPro from an external TM drive as we speak. I can say with almost 100% certainty that force restarting (holding the power-button down until the book shuts off) will corrupt your start up disk to some extent.
My problem is that I was away from my network when TM tried to do an update. I'm not sure if TM was actually able to connect to my server but none the less I was on a verizon wireless card and so even a minor backup would have been slow.
I needed to shut the computer down and leave. I have had TM hang when trying to shut down and tried to tell it to stop the back-up (which it tries to do for hours on end and have had to force quit before... had to run disk first aid that time) So this time I figured Id leave the computer on (though unplugged) while I drove home.
I did not close the case until the screen went dark. Unfortunately, it had just gone to sleep (a half hour later) instead of shutting off but I did not know that at the time so I shut the case then.
When I plugged it in in the AM it was dark but not black... I could just see the screen and could see it was frozen. Force restart completely screwed my startup disk. Luckily I have a BU from the night before.
Maybe TM should also be linked to the location, and or connection you are using. So, if I am away from my LAN it will automatically turn off. I also wish I could set it to back up every x hours instead of every hour.
Good idea... just needs some work on the routines. (only an hour left on my restore now)

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

Another problem with Time Machine

This is the second time I have experienced the following problem with Time Machine. After 2 months of backups it gets to a point where backups fail and I cannot enter time machine. In each instance I have only used 110GB of the 500GB space.
Is there a better solution to fixing this problem than deleting the sparsebundle? That seems to be the only way to get it to back up again.

backup is failing again:
Oct 28 08:39:58 MBA /System/Library/CoreServices/backupd[8307]: Starting standard backup
Oct 28 08:40:02 MBA /System/Library/CoreServices/backupd[8307]: FSMatchAliasBulk returned 0 while resolving alias to backup target
Oct 28 08:40:07 MBA /System/Library/CoreServices/backupd[8307]: Backup failed with error: 19
Oct 28 09:22:57 MBA /System/Library/CoreServices/backupd[8464]: Starting standard backup
Oct 28 09:22:58 MBA /System/Library/CoreServices/backupd[8464]: Network mountpoint /Volumes/MPTC not owned by backupd... remounting
Oct 28 09:22:59 MBA /System/Library/CoreServices/backupd[8464]: Network volume mounted at: /Volumes/MPTC-1
Oct 28 09:22:59 MBA /System/Library/CoreServices/backupd[8464]: Backup requested due to disk attach
Oct 28 09:23:28 MBA /System/Library/CoreServices/backupd[8464]: Disk image /Volumes/MPTC-1/MBA_001f5bd2c764.sparsebundle mounted at: /Volumes/Backup of MBA
Oct 28 09:23:32 MBA /System/Library/CoreServices/backupd[8464]: Backing up to: /Volumes/Backup of MBA/Backups.backupdb
Oct 28 09:23:32 MBA /System/Library/CoreServices/backupd[8464]: Backup requested due to disk attach
Oct 28 09:25:44 MBA /System/Library/CoreServices/backupd[8464]: No pre-backup thinning needed: 242.1 MB requested (including padding), 351.94 GB available
Oct 28 09:41:34 MBA /System/Library/CoreServices/backupd[8464]: Copied 990 files (72.4 MB) from volume MacBook Air HD.
Oct 28 09:41:35 MBA /System/Library/CoreServices/backupd[8464]: No pre-backup thinning needed: 159.6 MB requested (including padding), 351.94 GB available
Oct 28 09:44:09 MBA /System/Library/CoreServices/backupd[8464]: Bulk setting Spotlight attributes failed.
Oct 28 09:46:13 MBA /System/Library/CoreServices/backupd[8464]: Copied 879 files (2.2 MB) from volume MacBook Air HD.
Oct 28 09:47:18 MBA /System/Library/CoreServices/backupd[8464]: Starting post-backup thinning
Oct 28 09:49:15 MBA /System/Library/CoreServices/backupd[8464]: Deleted backup /Volumes/Backup of MBA/Backups.backupdb/MBA/2008-10-27-090710: 351.94 GB now available
Oct 28 09:50:46 MBA /System/Library/CoreServices/backupd[8464]: Deleted backup /Volumes/Backup of MBA/Backups.backupdb/MBA/2008-10-27-061332: 351.94 GB now available
Oct 28 09:52:53 MBA /System/Library/CoreServices/backupd[8464]: Deleted backup /Volumes/Backup of MBA/Backups.backupdb/MBA/2008-10-27-050805: 351.94 GB now available
Oct 28 09:52:53 MBA /System/Library/CoreServices/backupd[8464]: Post-back up thinning complete: 3 expired backups removed
Oct 28 09:52:53 MBA /System/Library/CoreServices/backupd[8464]: Backup completed successfully.
Oct 28 09:53:11 MBA /System/Library/CoreServices/backupd[8464]: Attempt to eject diskimage failed with status: -47, dissenting pid: 0
Oct 28 10:23:16 MBA /System/Library/CoreServices/backupd[8603]: Starting standard backup
Oct 28 10:23:19 MBA /System/Library/CoreServices/backupd[8603]: Network volume mounted at: /Volumes/MPTC-1
Oct 28 10:23:27 MBA /System/Library/CoreServices/backupd[8603]: Disk image /Volumes/MPTC-1/MBA_001f5bd2c764.sparsebundle mounted at: /Volumes/Backup of MBA
Oct 28 10:23:27 MBA /System/Library/CoreServices/backupd[8603]: Backing up to: /Volumes/Backup of MBA/Backups.backupdb
Oct 28 10:23:28 MBA /System/Library/CoreServices/backupd[8603]: Error: (-50) Creating directory 2008-10-28-102328.inProgress
Oct 28 10:23:28 MBA /System/Library/CoreServices/backupd[8603]: Failed to make snapshot container.
Oct 28 10:23:33 MBA /System/Library/CoreServices/backupd[8603]: Backup failed with error: 2
Oct 28 10:23:33 MBA /System/Library/CoreServices/backupd[8603]: Attempt to eject diskimage failed with status: -47, dissenting pid: 0
Oct 28 11:23:16 MBA /System/Library/CoreServices/backupd[8729]: Starting standard backup
Oct 28 11:23:16 MBA /System/Library/CoreServices/backupd[8729]: Network volume mounted at: /Volumes/MPTC-1
Oct 28 11:23:20 MBA /System/Library/CoreServices/backupd[8729]: Disk image /Volumes/MPTC-1/MBA_001f5bd2c764.sparsebundle mounted at: /Volumes/Backup of MBA
Oct 28 11:23:20 MBA /System/Library/CoreServices/backupd[8729]: Backing up to: /Volumes/Backup of MBA/Backups.backupdb
Oct 28 11:23:21 MBA /System/Library/CoreServices/backupd[8729]: Error: (-50) Creating directory 2008-10-28-112321.inProgress
Oct 28 11:23:21 MBA /System/Library/CoreServices/backupd[8729]: Failed to make snapshot container.
Oct 28 11:23:26 MBA /System/Library/CoreServices/backupd[8729]: Backup failed with error: 2
Oct 28 11:23:26 MBA /System/Library/CoreServices/backupd[8729]: Attempt to eject diskimage failed with status: -47, dissenting pid: 0
Oct 28 11:24:05 MBA /System/Library/CoreServices/backupd[8729]: Stopping backupd to allow ejection of backup destination disk!
Oct 28 11:24:11 MBA /System/Library/CoreServices/backupd[8747]: Backup requested by user
Oct 28 11:24:11 MBA /System/Library/CoreServices/backupd[8747]: Starting standard backup
Oct 28 11:24:11 MBA /System/Library/CoreServices/backupd[8747]: Network volume mounted at: /Volumes/MPTC-1
Oct 28 11:24:12 MBA /System/Library/CoreServices/backupd[8747]: Disk image /Volumes/MPTC-1/MBA_001f5bd2c764.sparsebundle mounted at: /Volumes/Backup of MBA
Oct 28 11:24:12 MBA /System/Library/CoreServices/backupd[8747]: Backing up to: /Volumes/Backup of MBA/Backups.backupdb
Oct 28 11:24:12 MBA /System/Library/CoreServices/backupd[8747]: Error: (-50) Creating directory 2008-10-28-112412.inProgress
Oct 28 11:24:12 MBA /System/Library/CoreServices/backupd[8747]: Failed to make snapshot container.
Oct 28 11:24:17 MBA /System/Library/CoreServices/backupd[8747]: Backup failed with error: 2
Oct 28 11:24:17 MBA /System/Library/CoreServices/backupd[8747]: Attempt to eject diskimage failed with status: -47, dissenting pid: 0

HT1338 problems with time machine and parallels desktop, mac osx mountain lion 10.8

have a good day, i have been problems with time machine and parallels desktop, dont work in mac osx 10.8, i upgrate two mac´s (macbook air, imac), in the two machines shows problems, could you help me please.
two machines have good ram memory (macbook air 11.1 2010 early , imac 2009 late).
i am waiting for your help.
thanks.
Jesus.

Take a look here:
http://pondini.org/TM/Troubleshooting.html
Specifically, you'll probably want to try item #A5 on that page, but there's a lot of other info there that may be useful.

I am having problems with Time Machine and having enough space to finish my last back up.

I am having problems with Time Machine and having enough space to finish my last back up.

Take a look at this link, http://support.apple.com/kb/HT1427

Problem with Time Machine backup (Snow Leopard)

Similar Messages

Maybe you are looking for