Which disk did Time machine backup if running Mac OSX 10.6.8 on an external startup disk?

The original hard drive on my 2007 iMac was pretty full, so I was using an external hard drive as the startup disk while I got around to replacing the original hard drive. I could still see the original hard drive and its contents and it still had a bootable copy of OSX 10.6.8 on it, but I was starting up from the external drive running OSX 10.6.8. I recently attached another external drive and backed up with Time Machine. Now the original internal hard drive has crashed. I can no longer see it to even try to repair it. My question is, was that internal hard drive backed up with the Time Machine backup, or was only the external startup disk backed up? If the internal one was backed up, how can I retore it's contents to another drive? - Thanks

Sorry to hear.
Other possibilities...
Data Rescue...
http://www.prosofteng.com/products/data_rescue.php
(Has a Free Demo to see if it could or not, but you'll need another drive to recover to).
rccharles on file recovery...
"Stellar Phoenix Macintosh - Mac data recovery software, recovers data from damaged, deleted, or corrupted volumes and even from initialized disks."
They have a trial version, so I guess you can see if your data can be recovered...
http://www.stellarinfo.com/mac-data-recovery.htm
FileSalvage is an extremely powerful Macintosh application for exploring and recovering deleted files from a drive or volume. FileSalvage is designed to restore files that have:
    * been accidentally deleted.
    * become unreadable due to media faults.
    * been stored on a drive before it was re-initialized/formatted.
http://subrosasoft.com/OSXSoftware/index.php?main_page=product_info&products_id= 1

Similar Messages

I have a mid2009 MacBook Pro for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

I have a mid2009 MacBook Pro running Mavericks for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

no archive/ backup is perfect, HD clones can be set to make incremental additions, same as time machine however, though they are more time involved in doing so.
See the + and - of all data backup/ archives below and "spread it around".... or the "dont put your eggs all in one basket" philosophy.
Peace
Data Storage Platforms; their Drawbacks & Advantages
#1. Time Machine / Time Capsule
Drawbacks:
1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
6. Restoring from TM is quite time intensive.
7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
13. *Level-1 security of your vital data.
Advantages:
1. TM is very easy to use either in automatic mode or in 1-click backups.
2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
#2. HD archives
Drawbacks:
1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
Advantages:
1. Fills the gap left in a week or 2-week-old HD clone, as an example.
2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
4. Best-idealized 1st platform redundancy for data protection.
5. *Perfect primary tier and level-2 security of your vital data.
#3. HD clones (see below for full advantages / drawbacks)
Drawbacks:
1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
Advantages:
1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
3. HD clones are unconnected and isolated from recent corruption.
4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
7. *Level-2 security of your vital data.
HD cloning software options:
1. SuperDuper HD cloning software APP (free)
2. Carbon Copy Cloner APP (will copy the recovery partition as well)
3. Disk utility HD bootable clone.
#4. Online archives
Drawbacks:
1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
Advantages:
1. In case of house fire, etc. your data is safe.
2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
5. *Level-1.5 security of your vital data.
#5. DVD professional archival media
Drawbacks:
1. DVD single-layer disks are limited to 4.7Gigabytes of data.
2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
Advantages:
1. Archival DVD professional blank media is rated for in excess of 100+ years.
2. DVD is not subject to mechanical breakdown.
3. DVD archival media is not subject to ferromagnetic degradation.
4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
5. DVD media is once written and therefore free of data corruption if the write is correct.
6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
7. Best-idealized 4th platform redundancy for data protection.
8. *Level-3 (highest) security of your vital data.
[*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
#6. Cloud based storage
Drawbacks:
1. Cloud storage can only be quasi-possessed.
2. No genuine true security and privacy of data.
3. Should never be considered for vital data storage or especially long-term.
4. *Level-0 security of your vital data.
Advantages:
1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
2. Easy source for small-file data sharing.

When I get to the select disk page it says that the HD is uesd as time machine drive. How can I remove time machine backup from my Mac.

I am tring to installe OS X Mavericks. When I get to the select disk page it says that the HD is uesd as time machine drive. How can I remove time machine backup from my Mac.

Open up your Finder and click on Go on the top menu bar. Select Computer and then double click Macintosh HD. In here delete the backup folder. Might be called backups.backupdb.

Restoring a time machine backup from a Mac mini to a new Mac mini server

Hi,
I just replaced a faulty Mac mini with a Mac mini server. I have a time machine backup of my Mac mini and want to transfer it over to the Mac mini. How do I do this?

This is a bit of a guess... But I Imagine you would have to start with the workstation OS install DVD first, and go from there at the appropriate point. Any chance you have or could make a CCC backup instead? I am assuming you could boot a mini server from a backup of mini non-server. Then you could copy it over. This is probably worth a phone call to Apple TAC

Time machine backup keeps running, total rising

Hi all,
My Macbook Pro (late 11, osx 10.8.2, everything updated) has suddenly started having a roblem with time machine. I'm using an external harddisk (Western digital Passport, 500 Gb) to backup my 250 GB Internal SSD. It's been working fine for the 5 months I've had them both. Now it has suddenly developed a problem where the Time Machine backup looks like it will go on for an infinite amount of time:
When the backup starts, after teh "Preparing backup..." cycle, it starts off displaying a sensible amount of backup to run (e.g., "backing up 0 MB of 980 MB"). Then after hitting or getting close to that total, the target amount rises contantly to always be ahead of the backup amount, i.e., it will start:
backing up 1.2 GB of 1.7 GB
backing up 2.3 GB of 2.5 GB
backing up 4.6 GB of 4.8 GB
etc
The longest I've left this for is about 25 minutes and it has no signs of stopping. Is there a solution to this problem? I noticed some similar questions on the forum but from 2 years ago, and some links that were suggested as possible answers are now no longer working. Any help gratefully received!

I did find a solution which appears to be working, at least in my case. Here is what I discovered was happening on my Mac Pro:
On one of my internal hard drives, I had created 4 different folders, and those folders contained various sub-folders. Just for the sake of this discussion, We'll call them folders 1-4. When I checked Get Info on the HD as a whole, it told me 1.12 of 2.0 TB was used, which was accurate. When I checked folders 1-4, their totals all added up to 1.12 TB used. However, When I went into certain SUB-folders within folders 1-4, and added up their totals using the Get Info command, it did not equal the total HD space used when I checked the main folder as a whole.
In other words, if I had 3 sub-folders in the "Main" folder #2 - and folder #2, using Get Info, said it contained a total of 450 GB, when I add up the 3 sub-folders contained within folder #2, it would equal 750 GB.
These extra GB, located in only a couple of places on sub-folders of the HD, were confusing Time Machine. It would act as stated above... it would take the total of 1.12 TB for that drive, attempt to back it up, but when it reached that total, suddenly, OS X ML would realize there was more data in folder #2's sub-folder, and the numbers would continually rise until the external backup drive was full, thus creating an error on Time Machine's backup.
Now, I don't know why this happened. Apparently when I deleted certain files and emptied the trash, it didn't completely erase them. I've tried using "Secure Empty Trash," but with the large video files I use, the empty procedure freezes before it can finish. I cannot explain this phenomenon because I'm not well-versed on the inner-workings of OS X.
My solution was simple, albeit a pain. I went into the sub-folder, selected all the items inside (folders, documents, videos, audio, etc.) and moved them out of that sub-folder. Now, they are all floating freely in folder #2. Then, I deleted that sub-folder, emptied the trash, and then re-created that sub-folder with the same name. Finally, I moved all the items from that sub-folder back into the newly created one, and voila!!!! When I added up all the sub-folders totals via Get Info, they matched exactly what Get Info proclaimed for folder #2!
Again, don't know why this happened, but I was able to successfully back up everything, and have had no troubles in the week and a half since.
If any of this doesn't make sense, please feel free to ask questions. But this is how I solved the problem.

Time Machine backup created on Mac with a large hard disk. What happens when restore to MacBook Air with small SSD drive?

What if a Time Machine backup was created on a Mac with a large hard disk, e.g. 500GB iMac - and I buy a new MacBook Air with a small SSD hard disk e.g 128GB. What happens when I need to use the larger Time Machine file to set up the new MacBook Air? What happens to all those files that can't fit on the smaller SSD drive?

It is not the HD size, but rather the size of the data it contains. If you right-click your 500GB drive and select "Get Info" you can see how much is actually being used.
Naturally if you are using more space than the new drive has, then you have to make some choices about what you want to keep and what you want to keep archived.
I don't know what options are available but you may simply have to do a manual restore of files you want, in groups.

Issue trying to use old Mac Time Machine backup on new Mac

I've just got a new iMac 27" to replace my old 21" and am planning to restore files from the Time Machine backup I have. On the iMac 21" I used an external hard-drive connected to an Airport Extreme Base Station to back up using Time Machine. On the new Mac the external drive is connected directly to the USB port. The old machine is now about 10,000 miles away from me.
The issue I have is I cannot read the back-up from the old machine on the new.
During the first startup I tried to read from the Time Machine backup but the system told me I could not use it because it was from a different machine - it read all the back-up dates and let me chose, but did not allow to use it.
After startup was completed, I run a software update to make sure everything had the same version and tried Migration Assistant (with the HD still connected to the USB port), but the wheel keeps spinning not finding any disk.
I can read the .sparsebundle file on the external drive and I see it is intact. Disk Utility recognizes it and Status is Not mounted. When I try to open it with Disk Utility it says it is not mountable.
Any of you know how I can resolve this? I am thinking of a way of opening the file and reading it.
I really just need my music, my movies and my pictures, but I have 1.2T of that so it is not something I can download from the old Mac.
Thanks a lot in advance.

I've just got a new iMac 27" to replace my old 21" and am planning to restore files from the Time Machine backup I have. On the iMac 21" I used an external hard-drive connected to an Airport Extreme Base Station to back up using Time Machine. On the new Mac the external drive is connected directly to the USB port. The old machine is now about 10,000 miles away from me.
The issue I have is I cannot read the back-up from the old machine on the new.
During the first startup I tried to read from the Time Machine backup but the system told me I could not use it because it was from a different machine - it read all the back-up dates and let me chose, but did not allow to use it.
After startup was completed, I run a software update to make sure everything had the same version and tried Migration Assistant (with the HD still connected to the USB port), but the wheel keeps spinning not finding any disk.
I can read the .sparsebundle file on the external drive and I see it is intact. Disk Utility recognizes it and Status is Not mounted. When I try to open it with Disk Utility it says it is not mountable.
Any of you know how I can resolve this? I am thinking of a way of opening the file and reading it.
I really just need my music, my movies and my pictures, but I have 1.2T of that so it is not something I can download from the old Mac.
Thanks a lot in advance.

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.

Time Machine backup on new Mac - but too big?

Hi,
I am the current owner of a Macbook and i use 160GB of my harddrive. I am contemplating on buying a Macbook Air 11" with 128GB "HD", but I am hesitant, since I don't know how the computer would handle having to start up from a Time Machine-back up made from my Macbook, that would of course be larger than the Macbook Air has capacity for.
Is it even possible?

firemandan900 wrote:
I just had to replace my 13" Macbook Pro through warranty. When I first turned it on I selected to restore the computer from my time machine backup and after several hours it finished successfully with the exception of Ilife which on the restore had to be updated before it would open the restored databases. The other issue I am having is that timemachine is no longer working. I would prefer to have timemachine backup to the existing archive structure it created on the old machine but right now it just says it can not find the volume. Is there a way to keep using the existing backup
If there's room, TM can start a new set of backups for the new Mac on the same disk or Time Capsule. But it will make a new, full backup of the new Mac, so if your TM disk/partition isn't at well over twice the size of the data it's backing-up, your best bet will be to erase the drive with Disk Utility and let TM start over.
There's a downside to that, though. TM on the new Mac won't delete the oldest backups from the old Mac when it needs room for new backups.
Instead, it will delete the oldest backups from the new Mac, leaving the old backups "stranded." Without erasing the TM disk/partition, you'll have to delete the old backups one at a time, via the TM interface, which is quite tedious and time consuming. See the instructions in item #12 of the Frequently Asked Questions post at the top of this forum.
or do I need to delate the archives and start a new archive?
That's probably your best option.

External usb disc used for Time Machine backup disconnects when Mac has been into sleep mode

I use a 1Tb External usb disc used for Time Machine backup which works fine, but when the Mac goes into sleep mode & powers back on I get a message stating that you should always eject the Drive before removing.
Any suggestions on how to get around this problem would be welcome

Look at the root of your hard drive for a folder called Backups.backupdb.
Or, a sparse bundle disk image for one of mobile computers that might have tried to back up to your Mac.
If you have those, remove them and try again.

Copying from a Time Machine backup to a Mac with Tiger

I've got a Time Machine Backup of my MBP, which is running Leopard (obviously). I'd like to grab all of the files (recursively) from the latest TM backup of my "Documents" directory onto another Mac with Tiger.
From the command line (on the Tiger machine with the TM firewire backup drive connected), I've tried:
sudo cp -RL /Volumes/Daily/Backups.backupdb/My MacBook Pro/Latest/Macintosh HD/Users/sbrown/Documents/* ~/Documents
However, it does not follow the hard links. How can I get it to follow whatever links it needs to to give me a complete set of the files in the Documents folder?

Confirmed best practice (after hours with AppleCare)--will allow you to create a comprehensive backup of whatever you need from a former TM backup, without traversing aliases or needing to keep a Leopard install around after the initial step.
You DO need to have Leopard still installed, just once. Simply boot into Leopard, navigate to your backup volume and go to Latest--> in the Backup DB. This is your entire system as it most recently appeared. If you have enough hard drive space on your TM volume, you can copy every folder here to the root level of the same TM volume. This would ensure a complete, up-to-date and Tiger-visible backup at the root level. However, you can also just copy the folders you need--to the same root level of the TM backup--and the OS will break all the hardlinks and create normal (duplicate) files in the new location.
This is good because it bypasses your likely-small internal hard drive (which, if you're on a Powerbook, is a precious commodity). It just makes a dupe of your most recent backup. The other method (Show Original) won't let you get the entire drive state back easily. It requires manual lookup of every file you think you need, then a reboot into Leopard if you need another. This method lets you create a working archive.
Hope that helps...
Message was edited by: dmaterialized

Continue using existing Time Machine backup on new mac

I just had to replace my 13" Macbook Pro through warranty. When I first turned it on I selected to restore the computer from my time machine backup and after several hours it finished successfully with the exception of Ilife which on the restore had to be updated before it would open the restored databases. The other issue I am having is that timemachine is no longer working. I would prefer to have timemachine backup to the existing archive structure it created on the old machine but right now it just says it can not find the volume. Is there a way to keep using the existing backup or do I need to delate the archives and start a new archive?

firemandan900 wrote:
I just had to replace my 13" Macbook Pro through warranty. When I first turned it on I selected to restore the computer from my time machine backup and after several hours it finished successfully with the exception of Ilife which on the restore had to be updated before it would open the restored databases. The other issue I am having is that timemachine is no longer working. I would prefer to have timemachine backup to the existing archive structure it created on the old machine but right now it just says it can not find the volume. Is there a way to keep using the existing backup
If there's room, TM can start a new set of backups for the new Mac on the same disk or Time Capsule. But it will make a new, full backup of the new Mac, so if your TM disk/partition isn't at well over twice the size of the data it's backing-up, your best bet will be to erase the drive with Disk Utility and let TM start over.
There's a downside to that, though. TM on the new Mac won't delete the oldest backups from the old Mac when it needs room for new backups.
Instead, it will delete the oldest backups from the new Mac, leaving the old backups "stranded." Without erasing the TM disk/partition, you'll have to delete the old backups one at a time, via the TM interface, which is quite tedious and time consuming. See the instructions in item #12 of the Frequently Asked Questions post at the top of this forum.
or do I need to delate the archives and start a new archive?
That's probably your best option.

Can I have 2 Separate Time Machine backups on one Mac?

I have a Mac running Snow leopard which I keep connected to an external USB drive. That drive is set up to automatically back my machine through Time Machine and it works great.
I would like to also do a backup of my machine and all its files onto a portable USB drive that I can then take to the office (i.e. remove it from the house) for security purposes. Once every couple of weeks I would plan on bringing the portable USB drive back home, plugging it into the Mac, doing another Time Machine backup and then removing it again.
Can I have 2 separate Time Machine backups onto 2 separate hard drives (as described above) on a single Mac?

Well I tried it, and it worked.

How do i install time machine backup from old mac to newer one

Hi, I know how to set up a brand new imac with full info and settings from an old mac from a time machine backup on a portable drive, BUT.... this time i have a 2011 imac in my studio already in use that we want to be completly swapped with full info and settings/software etc from an older 2009 imac, which we may sell on.
I have backup up via time machine the older 2009 mac, but when i plug this into the 2011 imac how do i completly wipe it and set up with info from the time machine?? it was easy doing it on a factoryt new mac but not this.
thanks
lee

If I have understood you properly, you want to migrate the data from the 2009 iMac onto the 2011 iMac but keeping the existing files on it.
To do this, use Migration Assistant > http://support.apple.com/kb/HT4889 It will create a new user with the transferred files from the old iMac.
If you want to wipe the 2011 iMac and restore everything from the 2009 iMac, the most reliable way is erasing the hard drive, reinstalling OS X and restoring the backup. If you are using the same OS X version on both iMacs, you can restore the Time Machine backup without having to reinstall OS X, just starting from the Mac OS X DVD (or Recovery HD, if you have OS X Lion or Mountain Lion)

Time Machine backup requires significantly more space than size of hard drive + external

I can't seem to figure out what is going on here. I recently purchased a new Macbook Pro with a 1T SSD hard drive, upgrading from an older MB Pro with a 500 GB hard drive. In the past I've used Time Machine to back up my hard drive and an external hard drive with RAW format photos and video footage that totals 441.56 GB. My internal internal hard drive currently is 487 GB, and I've used a 1TB time machine back up without problem to date.
I used Time Machine to install on the new system and it worked flawlessly, except that the Time Machine backups wouldn't continue. Time Machine--even when left overnight--would get hung up on Preparing Files to Back Up. So, I reformatted the Time Machine disk (lost the old backups) and attempted to back up from scratch. I then got a message that I need 3.37 TB to complete my new Time Machine back up, though the total size of the back up on disk is ~930 GB. I've read that Time Machine needs 20% - 30% overhead on disk to work well, but I can't figure out why it would require 3x the back up size. I'm hesitant to purchase a new 4 TB external hard drive as I suspect this is a software issue. I've tried reformatting the disk twice more (three total), rebooting my computer, etc. but I keep getting the 3.37 TB message. I'm operating Mavericks OS 10.9.4.
I would be grateful for insight on this.
Best,
Alex

Hi Linc, thanks for taking a look at this problem. I just reinitiated a backup to make sure it's most up-to-date. Without the external hard drive, I was able to complete a simple backup. After plugging the external in again, here's the log I got:
8/6/14 11:34:03.228 PM com.apple.backupd[78806]: Starting automatic backup
8/6/14 11:34:03.660 PM com.apple.backupd[78806]: Backing up to /dev/disk2s2: /Volumes/Time Machine/Backups.backupdb
8/6/14 11:34:04.538 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78808]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:04.538 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:04.556 PM ReportCrash[78796]: Saved crash report for MessageCenter[78808] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233404_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:34:10.462 PM com.apple.backupd[78806]: Forcing deep traversal on source: "Media" (device: /dev/disk1s2 mount: '/Volumes/Media' fsUUID: BB6ACCE1-B004-3647-9721-0CE726FAA059 eventDBUUID: 0AC9DC0D-5BE3-4574-94C6-4B041C9C4A26)
8/6/14 11:34:10.469 PM com.apple.backupd[78806]: Deep event scan at path:/Users/Alex/Pictures/Aperture Library.aplibrary/Database/apdb reason:contains changes|must scan subdirs|fsevent|missed reservation|file event|
8/6/14 11:34:10.573 PM com.apple.backupd[78806]: Finished scan
8/6/14 11:34:10.573 PM com.apple.backupd[78806]: Not using file event preflight for Macintosh HD
8/6/14 11:34:14.674 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78820]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:14.674 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:14.693 PM ReportCrash[78796]: Saved crash report for MessageCenter[78820] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233414_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:34:24.815 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78821]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:24.815 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:24.835 PM ReportCrash[78796]: Saved crash report for MessageCenter[78821] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233424_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:34:34.954 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78822]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:34.954 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:34.978 PM ReportCrash[78796]: Saved crash report for MessageCenter[78822] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233434_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:34:45.091 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78823]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:45.091 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:45.109 PM ReportCrash[78796]: Saved crash report for MessageCenter[78823] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233445_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:34:55.119 PM ReportCrash[78825]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:34:55.242 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78824]) Job appears to have crashed: Bus error: 10
8/6/14 11:34:55.242 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:34:55.275 PM ReportCrash[78825]: Saved crash report for MessageCenter[78824] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233455_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:05.377 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78826]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:05.377 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:05.395 PM ReportCrash[78825]: Saved crash report for MessageCenter[78826] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233505_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:15.514 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78828]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:15.514 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:15.533 PM ReportCrash[78825]: Saved crash report for MessageCenter[78828] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233515_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:25.653 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78829]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:25.653 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:25.672 PM ReportCrash[78825]: Saved crash report for MessageCenter[78829] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233525_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:35.789 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78830]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:35.789 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:35.809 PM ReportCrash[78825]: Saved crash report for MessageCenter[78830] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233535_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:45.923 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78831]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:45.923 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:45.942 PM ReportCrash[78825]: Saved crash report for MessageCenter[78831] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233545_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:35:55.950 PM ReportCrash[78833]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:35:56.071 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78832]) Job appears to have crashed: Bus error: 10
8/6/14 11:35:56.071 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:35:56.105 PM ReportCrash[78833]: Saved crash report for MessageCenter[78832] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233556_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:06.210 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78834]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:06.210 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:06.229 PM ReportCrash[78833]: Saved crash report for MessageCenter[78834] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233606_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:10.023 PM WindowServer[109]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
8/6/14 11:36:10.135 PM WindowServer[109]: CGXMuxCapture: Starting
8/6/14 11:36:10.136 PM WindowServer[109]: CGXMuxCapture: Acquired
8/6/14 11:36:10.136 PM WindowServer[109]: Display 0x4280882 captured by conn 0xdf03
8/6/14 11:36:14.010 PM WindowServer[109]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280882 device: 0x7f8682f01ec0 isBackBuffered: 1 numComp: 3 numDisp: 3
8/6/14 11:36:16.346 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78836]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:16.346 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:16.365 PM ReportCrash[78833]: Saved crash report for MessageCenter[78836] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233616_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:19.883 PM WindowServer[109]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 10.86 seconds (server forcibly re-enabled them after 1.00 seconds)
8/6/14 11:36:20.172 PM com.apple.SecurityServer[15]: Killing auth hosts
8/6/14 11:36:20.172 PM com.apple.SecurityServer[15]: Session 100055 destroyed
8/6/14 11:36:20.213 PM WindowServer[109]: CGXMuxCapture: Released
8/6/14 11:36:20.213 PM WindowServer[109]: Display 0x4280882 released by conn 0xdf03
8/6/14 11:36:20.237 PM WindowServer[109]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280882 device: 0x7f8682f01ec0 isBackBuffered: 1 numComp: 3 numDisp: 3
8/6/14 11:36:26.343 PM com.apple.prefs.backup.remoteservice[78837]: assertion failed: 13E28: liblaunch.dylib + 25164 [A40A0C7B-3216-39B4-8AE0-B5D3BAF1DA8A]: 0x25
8/6/14 11:36:26.396 PM com.apple.prefs.backup.remoteservice[78837]: assertion failed: 13E28: liblaunch.dylib + 25164 [A40A0C7B-3216-39B4-8AE0-B5D3BAF1DA8A]: 0x25
8/6/14 11:36:26.512 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78838]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:26.512 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:26.536 PM ReportCrash[78833]: Saved crash report for MessageCenter[78838] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233626_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:26.614 PM com.apple.prefs.backup.remoteservice[78837]: Bogus event received by listener connection:
<error: 0x7fff74e8fb50> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff74e8fe60> { length = 18, contents = "Connection invalid" }
8/6/14 11:36:30.840 PM iTunes[637]: Entered:_AMMuxedDeviceDisconnected, mux-device:840
8/6/14 11:36:30.840 PM iTunes[637]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:840
8/6/14 11:36:30.841 PM iTunes[637]: tid:1aa47 - Mux ID not found in mapping dictionary
8/6/14 11:36:30.841 PM iTunes[637]: tid:1aa47 - Can't handle disconnect with invalid ecid
8/6/14 11:36:36.647 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78842]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:36.647 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:36.666 PM ReportCrash[78833]: Saved crash report for MessageCenter[78842] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233636_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:46.781 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78843]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:46.781 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:46.800 PM ReportCrash[78833]: Saved crash report for MessageCenter[78843] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233646_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:36:56.814 PM ReportCrash[78845]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:36:56.936 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78844]) Job appears to have crashed: Bus error: 10
8/6/14 11:36:56.936 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:36:56.997 PM ReportCrash[78845]: Saved crash report for MessageCenter[78844] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233656_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:07.081 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78846]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:07.081 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:07.099 PM ReportCrash[78845]: Saved crash report for MessageCenter[78846] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233707_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:17.224 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78847]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:17.224 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:17.243 PM ReportCrash[78845]: Saved crash report for MessageCenter[78847] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233717_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:27.361 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78849]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:27.361 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:27.379 PM ReportCrash[78845]: Saved crash report for MessageCenter[78849] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233727_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:35.193 PM com.apple.usbmuxd[40]: _SendAttachNotification Device fc:25:3f:70:c5:7c@fe80::fe25:3fff:fe70:c57c._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
8/6/14 11:37:37.496 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78851]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:37.496 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:37.515 PM ReportCrash[78845]: Saved crash report for MessageCenter[78851] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233737_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:47.636 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78852]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:47.636 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:47.656 PM ReportCrash[78845]: Saved crash report for MessageCenter[78852] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233747_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:37:57.665 PM ReportCrash[78855]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:37:57.785 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78854]) Job appears to have crashed: Bus error: 10
8/6/14 11:37:57.785 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:37:57.845 PM ReportCrash[78855]: Saved crash report for MessageCenter[78854] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233757_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:07.920 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78856]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:07.920 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:07.939 PM ReportCrash[78855]: Saved crash report for MessageCenter[78856] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233807_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:18.056 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78859]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:18.056 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:18.076 PM ReportCrash[78855]: Saved crash report for MessageCenter[78859] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233818_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:28.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=78861[GoogleSoftwareUp] final status 0x0, allowing (remove VALID) page
8/6/14 11:38:28.205 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78860]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:28.205 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:28.225 PM ReportCrash[78855]: Saved crash report for MessageCenter[78860] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233828_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:38.341 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78862]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:38.341 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:38.360 PM ReportCrash[78855]: Saved crash report for MessageCenter[78862] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233838_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:48.481 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78863]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:48.481 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:48.499 PM ReportCrash[78855]: Saved crash report for MessageCenter[78863] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233848_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:38:58.507 PM ReportCrash[78865]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:38:58.628 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78864]) Job appears to have crashed: Bus error: 10
8/6/14 11:38:58.628 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:38:58.664 PM ReportCrash[78865]: Saved crash report for MessageCenter[78864] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233858_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:08.768 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78866]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:08.768 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:08.787 PM ReportCrash[78865]: Saved crash report for MessageCenter[78866] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233908_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:18.907 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78868]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:18.907 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:18.926 PM ReportCrash[78865]: Saved crash report for MessageCenter[78868] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233918_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:29.043 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78869]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:29.043 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:29.063 PM ReportCrash[78865]: Saved crash report for MessageCenter[78869] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233929_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:33.045 PM com.apple.backupd[78806]: Deep event scan at path:/Volumes/Media reason:must scan subdirs|require scan|
8/6/14 11:39:33.046 PM com.apple.backupd[78806]: Finished scan
8/6/14 11:39:33.046 PM com.apple.backupd[78806]: Not using file event preflight for Media
8/6/14 11:39:35.803 PM com.apple.backupd[78806]: Found 70992 files (587.73 GB) needing backup
8/6/14 11:39:35.834 PM com.apple.backupd[78806]: 611.31 GB required (including padding), 518.88 GB available
8/6/14 11:39:35.834 PM com.apple.backupd[78806]: No expired backups exist - deleting oldest backups to make room
8/6/14 11:39:39.185 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78870]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:39.185 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:39.204 PM ReportCrash[78865]: Saved crash report for MessageCenter[78870] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233939_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:47.777 PM com.apple.backupd[78806]: Deleted backup /Volumes/Time Machine/Backups.backupdb/Alex Edmunds’s MacBook Pro/2014-08-06-041205 containing 29.2 MB; 518.92 GB now available, 611.31 GB required
8/6/14 11:39:47.777 PM com.apple.backupd[78806]: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
8/6/14 11:39:49.315 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78872]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:49.315 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:49.334 PM ReportCrash[78865]: Saved crash report for MessageCenter[78872] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233949_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:39:50.722 PM com.apple.backupd[78806]: Deleted backup /Volumes/Time Machine/Backups.backupdb/Alex Edmunds’s MacBook Pro/2014-08-06-050217 containing 16.4 MB; 518.93 GB now available, 611.31 GB required
8/6/14 11:39:50.722 PM com.apple.backupd[78806]: Removed 2 expired backups so far, more space is needed - deleting oldest backups to make room
8/6/14 11:39:54.321 PM com.apple.backupd[78806]: Deleted backup /Volumes/Time Machine/Backups.backupdb/Alex Edmunds’s MacBook Pro/2014-08-06-060415 containing 37.3 MB; 518.97 GB now available, 611.31 GB required
8/6/14 11:39:54.321 PM com.apple.backupd[78806]: Removed 3 expired backups so far, more space is needed - deleting oldest backups to make room
8/6/14 11:39:59.342 PM ReportCrash[78874]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
8/6/14 11:39:59.381 PM com.apple.backupd[78806]: Deleted backup /Volumes/Time Machine/Backups.backupdb/Alex Edmunds’s MacBook Pro/2014-08-06-070639 containing 108.3 MB; 519.09 GB now available, 611.31 GB required
8/6/14 11:39:59.381 PM com.apple.backupd[78806]: Removed 4 expired backups so far, more space is needed - deleting oldest backups to make room
8/6/14 11:39:59.467 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78873]) Job appears to have crashed: Bus error: 10
8/6/14 11:39:59.467 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:39:59.507 PM ReportCrash[78874]: Saved crash report for MessageCenter[78873] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-233959_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:40:02.467 PM com.apple.backupd[78806]: Deleted backup /Volumes/Time Machine/Backups.backupdb/Alex Edmunds’s MacBook Pro/2014-08-06-080909 containing 91.3 MB; 519.18 GB now available, 611.31 GB required
8/6/14 11:40:02.467 PM com.apple.backupd[78806]: Removed 5 expired backups so far, more space is needed - deleting oldest backups to make room
8/6/14 11:40:02.467 PM com.apple.backupd[78806]: Deleted 5 backups containing 282.4 MB total; 519.18 GB now available, 611.31 GB required
8/6/14 11:40:02.467 PM com.apple.backupd[78806]: Backup date range was shortened: oldest backup is now Aug 6, 2014
8/6/14 11:40:03.163 PM com.apple.backupd[78806]: Backup failed with error 7: Not enough available disk space on the target volume.
8/6/14 11:40:09.597 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78877]) Job appears to have crashed: Bus error: 10
8/6/14 11:40:09.597 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:40:09.616 PM ReportCrash[78874]: Saved crash report for MessageCenter[78877] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-234009_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:40:19.731 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78878]) Job appears to have crashed: Bus error: 10
8/6/14 11:40:19.731 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:40:19.749 PM ReportCrash[78874]: Saved crash report for MessageCenter[78878] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-234019_Alex-Edmundss-M acBook-Pro.crash
8/6/14 11:40:29.863 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist[78879]) Job appears to have crashed: Bus error: 10
8/6/14 11:40:29.863 PM com.apple.launchd[1]: (cn.com.zte.MessageCenter.plist) Throttling respawn: Will start in 10 seconds
8/6/14 11:40:29.882 PM ReportCrash[78874]: Saved crash report for MessageCenter[78879] version ??? to /Library/Logs/DiagnosticReports/MessageCenter_2014-08-06-234029_Alex-Edmundss-M acBook-Pro.crash

Which disk did Time machine backup if running Mac OSX 10.6.8 on an external startup disk?

Similar Messages

Maybe you are looking for