Time Machine Backup - a lengthy process?

My iMac has a 250 GB HD. I also have a 400 GB USB2 External HD, and a 750 GB Firewire 400 HD. The latter has been purchased for live data with slightly faster access, eg video files etc and I am using the 400 GB now for back up purposes. I am currently running Time Machine for the first time, which is backing up some 282 GB of information to the USB2 HD. It is however very slow. At the current rate, it is writing at about 1 GB per hour, or in other words will take about 11 days or so to complete. This can't be right, does anyone have any ideas of where I am going wrong?

Thanks for the reply Peggy,
For whatever reason, Time Machine found a sudden turn of speed and completed the task manfully in less than a day.

Similar Messages

Why isn't my time machine backup updating a new drive correctly?

I bought a new larger hard drive and I am trying to use time machine (lion) to restore the new one and copy all my files. I made a Lion startup disk and use the disk utility to erase the new drive and then choose restore from time machine backup. The process runs great and then after about 3 hours it finishes and restarts the computer. Then the white screen with the grey apple and little spinner below it pop up and the spinner just spins forever.
Does anybody know what I am doing wrong? Thanks

It looks like it tries to start loading safe mode and the loading bar appears under the spinning lines under the apple but then the bar gets almost half full and just dissapears. I'm left with just that grey apple screen and the spinning lines again.
The only other startup option that seemed to get me somewhere other than the grey screen is when I hold the "option" key and choose from the hard drive or the dvd drive to boot. I can run from the dvd OS X disk that I made. Is there anything I can do there?

Restore Time Machine backup to Raid 0 (Striped set)?

I've been struggling with setting up my Mac mini (late 2012) server with a Striped RAID set and then restoring a Time Machine backup to the new RAID 0 volume. Here are the steps I have undertaken:
Bought a 3TB Airport Time Capsule and created a full restore of my existing Time Machine backups to it.
My Mac mini has dual 1TB hard drives. Pressed Command + R on bootup and entered recovery mode.
Using Disk Utility, I created a Striped RAID set by adding both my 1TB drives as slices to a new RAID set and clicked on Create.
After the RAID set was created, I exited Disk Utility.
Clicked on Restore from Time Machine Backup.
The process fails as it cannot create a Recovery Partition on a RAID set.
After much exploration, I think the problem can be resolved by attempting to Reinstall OS X on Step 5 and then attempting a Time Machine restore after the core OS is in place. Thoughts?

Additional Information
A Recovery partition cannot be created on RAID volumes. If your startup device is a RAID volume, you back up and reconfigure your computer to use a non-RAID boot volume. If needed, create a separate RAID volume for data which is not the target of the OS X installation. You can also create an external, bootable drive with a Recovery partition, as described above.
See this article if the following message appears during the install process:
"Install Failed: OS X could not be installed on your computer. OS X can't be installed on the disk because a recovery system can't be created. Visit www.apple.com/support/no-recovery to learn more"
From:
http://support.apple.com/kb/HT4649

TIme Machine backup grows too large during backup process

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

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

After upgrading my iPhone, I lost all my contacts..... and they were replaced with my wife's contacts even though she upgraded after I did. I did a time machine backup before I started the upgrade process, how do I get that saved data back to my phone?

After upgrading my iPhone, I lost all my contacts and they were replaced with my wife's contacts even though she upgraded after I did. I did a time machine backup before I started the upgrade process, how do I get that saved data back to my phone?

Hi bluegrandpanash,
Thanks for visiting Apple Support Communities.
If you backed up your iPhone to iCloud before updating the software, first try the steps under "Restore from an iCloud backup" in this article to recover your data:
iOS: Back up and restore your iOS device with iCloud or iTunes
http://support.apple.com/kb/HT1766
Best Regards,
Jeremy

In the installation process lion will not install as message reads MAC HD 904 gb available this disk is used for time machine backups .What is the next step

After downloading ,completing the lic agreement phase, the next step is where to install and automatically' MAC HD with 904 gb available this disk is used for time machine backups' is shown and installation is blocked .
Any body got any idea what to do next ?

Time machine needs its own partition to operate. So you are not going install a OSx Lion on that volume.
If there is enough room you may be able to partition the drive on the fly with DiskUtility
Are you saying you clean installed Lion and you are trying to move your user Data over with TM via the migration Assistant? Please explain.

2 iMacs upgraded to Mavericks, neither one is completing Time Machine backups. Never had this problem in previous OS versions. Reformated disc. Reinstalled as TM destination. Backup begins and then stops early in process.

I have two iMacs that I've upgraded to Mavericks 10.9.1.
Both started out OK but no longer allow Time Machine to complete backups.
The one I'm on now, older 24", has a fresh 500GB external HD for TM, reformated correctly.
Says backup size 147GB.
Get about 120 plus Mb into backup and stops.
No error messages, just stops and stays at the place where it stops.
Says calculating time remaining.
Left it on all day while away from my desk and returned home 10 hours later and still frozen at that state.
Newer iMac 27" fully loaded, 2TB HD as TM disc, same problem.
Backed up OK for the first few days, now frozen, with over 3/4 of the HD still available.
Reformat, reselect the TM disc, still will not complete a full backup.
Should I reinstall Mountain Lion until they get Mavericks working properly?
Are others experiencing the same problem?
Whassup?

Yes Eric. That is where the info came from. Since 9.2TB is impossible it must be due to how Time Machine handles the files in backups.backupdb. I have since done new Time Machine backups to the reformatted drive and I was hoping to copy at least few of the old backup files to the drive in the same file with the new ones but when I do that I get an error message that says backup files cannot be modified. It's very frustrating because I saved the old backups.backupdb to the desktop but it doesn't seem like I can do anything with it.

What happens if you Time-Machine backup an encrypted file-vault HD?

This is related to my previous post - but deserves special mention for those people who are using time-vault AND Time-Machine.
My question is this: If the backup of my Hard-drive is encrypted, and I then reinstall from backup, what will this situation likely produce?
This is what I have done. I also Archived and installed my Mac prior to installing from my Time-Machine backup.
I now have an error message that displays the following message at the login screen:
"Unable to log into the file-vault account "......." at this time. An error has occurred."
My password IS CORRECT. I have not changed it, and the log in window does accept my password, but it doesn't progress any further than the error message I gave above.
I'm wondering if the encryption process of file-vault is linked directly with the original installation I had of Mac OS-X before I Archived and installed.
Any thoughts/knowledge/Insight?? I want my old Mac back! (I don't recommend using file-vault). Any body else had this problem or can see what is happening to me here?
Thank you
Greg

I just did a backup, moved a folder with 600mb of images into a different folder, and did another backup. The free space on the backup drive dropped by the size of the folder's contents. The backup copied the files as I watched in System Preferences, and it looked like it was really copying the files to the external drive again. It looks like Time Machine isn't as smart as I hoped in this regard.
Still - I'd think the wasted space is only in the every-hour-for-the-last-24-hours bucket of Time Machine. I'm guessing the every hour backups are like a sliding window, where a backup that's 24 hours old drops out every hour rather than all the hourly backups getting wiped at midnight and starting over.
Regardless, only one version of the moved folder will eventually be stored as the daily backup for that day. I don't have proof, but that's what I think.
So, if you've moved a bunch of folders around or renamed them, the extra copies of the same exact files should drop off within 24 hours.
That's my interpretation, but I'm in no way positive!! The lengthy Ars review didn't offer an answer to this question.

Restoring time machine backup stuck at end

Hello!
I recently suffered a random filesystem failure and had to reinstall the OS. I was running 10.7, in fact, I turned on my MBP to install 10.7.1.
After a lengthy download, the installer prompted me to restore from a Time Machine backup, which I'm keeping since my last hardware HD failure. I chose to restore, and the installer detected my Time Capsule, loaded the backup, and started restoring.
I left it overnight and, come the following morning, the restore hadn't finished yet. Again, I left it while I was at work, and came back 8 hours later to find the screen in the exact same way I left it in the morning.
After some tests trying to restore the backup (including a failed back-to-Snow Leopard attempted recovery, couldn't connect to my TC), I figured I would reinstall Lion from scratch and use Console.app to check the progress using the system log when restoring using Migration Assistant.
My first surprise was when I tried to run Migration Assistant using the root user, which made Migration Assistant crash, so I had to create a second administrator user in order to restore my original administrator account.
After leaving it run its course, I started noticing that the Migration Assistant was trying to restart opendirectoryd, and that it was failing to start, citing error 71 "profile could not be found" (or opened, instead of found, I really don't remember and don't have the log here with me).
I then went into the terminal to check if the restored data was on disk, which it was, so, after a couple of attempts of launchd to restart opendirectoryd, I pulled the plug and shut the machine down cold (no shutdown process, just held the power button).
When the computer started up again (I have verbose boot mode on), it stalled at macx_swapon (again, or something like that, I don't remember), and didn't move in the whole hour and a half I let it sit there.
I tried booting single user mode, but the only thing I got to do was check if the restored data was there (which it was), and try to create my user (which I couldn't).
I've had success restoring backups from that Time Capsule but for another Mac.
Is there any way I can restore my computer back to the exact state of the Time Machine backup? FWIW, the TM backup is a data-only backup (i.e. doesn't have the OS with it), so a disk clone is not an option.
I really would like to avoid going the "fake manual restore" option of creating the same user, moving the files manually and so on, it's a PITA
Thanks in advance,
Nico

Sorry, can'thelp. But:
I trust TM only for rescuing individual files. I tried a full restoration of my Lion system, as a test, and everything was restored and seemed OK except half my Mail messages were missing. A few months ago, on OS 10.5.8, TM suddenly told me that it had deleted some files. The files deleted were all from Jan. 2010 to four weeks before! I know that it does this if the TM disc is getting full, but I had not created any large files in the preceding few hours. Also, the TM disc had loads of space left, yet when the message came, TM's GetInfo showed the disc nearly full!. I had to erase the disc and start again.
I don't find TM reliable. I make my backups in the form of bootable clones, scheduled every day in Carbon Copy Cloner.

10.5.6 - spotlight wants to index the Time Machine backup

Since I upgraded to 10.5.6, spotlight keeps trying to index the Time Machine backup. It won't let me add it to the privacy list - I get an "unknown error". Any ideas how to stop it doing that?
It seems that while spotlight's trying to index, Time Machine won't go any further than "preparing backup".

Spotlight does often seem to interfere with large TM backups.
Apparently it has to do with Spotlight busily indexing things that TM has just put on the drive, but maybe hasn't completely released or finished with. Exact cause unknown.
But it won't hurt to exclude your TM drive/partition from spotlight -- you'll find several threads in the Time Machine forum where this has helped greatly. After it's done, remove the exclusion if you want. Note that the TM disk may not get indexed until your next restart.
Also, download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. Then you'll get a bit more info on what it's doing.
If you see a message about a "deep traversal," when nothing seems to be happening, just be patient. This means TM must examine ever file and folder on your system to figure out what needs to be backed-up, so it will be a very lengthy process.

I'm having a hard time setting up my external hard from with my AirPort Extreme and Time Machine Backups.

I have been using a Mac Mini with an external hard and Time Machine. I bought an Airport Extreme and have had problem setting up the hard drive using the USB port on the Airport Extreme. I also just recently bought a Mac Book Air and hope to have both computers back up to the external hard drive using Time Machine and Airport Extreme. I have been using the optical drive from the Mac mini to load programs into the Mac Book Air. I think I'm just getting confused in Finder. I am just not seeing the hard drive. I ended up plugging the hard drive back into the Mac Mini and that is work fine again. How do I setting the external hard drive up to the AirPort Extreme and use for both computers? Or at least to start with the Mac mini.

It's critical to understand that Time Machine (TM) stores backups differently between local and network drives. That would mean the TM backup on your locally attached USB hard drive will not be directly useable when it is connected to the AirPort Extreme Base Station (AEBS). There is a way to copy a local version to a network version, but it is not fool-proof. When you do connect this drive and point TM to it, TM will start a brand new backup, leaving your existing backup as is.
If your current backup is critical to you, you may want to consider getting a second USB drive to attach to the Extreme and use your existing one as a backup ... or use TM's multi-backup process to backup to more than one destination drive alternatively.
So, at this point, you may want to make a decision on how you want to go forward to help provide a solution for you.
To directly answer your question, when you go to select a destination for a Time Machine backup, the drive(s) that show up under "Backup Disks" are those that TM already recognizes and has backed up to. Those listed under "Available Disks" are drives (either local or on the network) that TM can back up to.

Can't view time machine backups from old computer on new computer

My macbook pro laptop recently died and I am trying to access its time machine backup data through Finder on a different computer. In each one of my folders from different dates, however, the majority of the computer folders I would like to access (i.e. desktop, documents, dropbox, etc) have a little red "no" sign in the corner and prompt the following message when selected:
"The folder “FolderName” can’t be opened because you don’t have permission to see its contents"
How can I gain permission to see its contents? As the former user, I know whatever passwords are restricting these files, but I don't know how/where to go to give permission to these folders. I've tried going into Disk Utility and changing the permissions there, but to no avail, despite successful changing of the "Sharing & Permissions" to "Read & Write" for all listed accounts.
I'm currently trying to view this on an imac OSX 10.6.8. The dead MacBook pro ran OSX
thanks
kate

Hi Kate,
It sounds like you're running into an issue trying to recover that was on your previous Mac from a Time Machine backup. The article linked below will walk you through the process of recovering the data from your older Mac's Time Machine backup.
OS X: How to migrate data from another Mac using Mountain Lion and earlier
http://support.apple.com/kb/HT4889
Time Machine or other disk migration
If Migration Assistant isn't running on the target (new) Mac, open Migration Assistant (located in /Applications/Utilities/), select "From another Mac, PC, Time Machine backup, or other disk" then click Continue.
Connect your external hard drive if necessary.
Type in your admin password when prompted and click OK.
When the target Mac asks you for a migration method, select "From a Time Machine backup or other disk", then click Continue.
Select the Drive, Time Machine backup, or Time Capsule. If you select Time Capsule you will be prompted to enter the Time Capsule password. After entering the password, select the Time Machine backup.
Close all other applications on the source Mac, then click Continue to start the migration options.
The source Mac will ask you to select items to migrate.
You can customize your selection by clicking to open the disclosure triangles.
After you click Continue, the Migration Assistant will begin to transfer files to the target Mac. The amount of time that it takes for migration to complete depends on the amount of data being transferred and the speed of the network.
Note: To view documents that were migrated, choose Log Out from the Apple () menu, then login as the migrated user. The migrated documents will be located in the migrated user's home folder.
I hope this helps.
-Jason

Time Machine backup behavior erratic, now not working at all

[ Using Lion 10.7.2 on a Macbook Pro 15" with 2.53GHz Intel Core 2 Duo processor, 4GB RAM. ]
The Macbook is connected to our home LAN, and I have been using (since September) a Synology NAS drive on the network which is set up as the Time Machine backup drive. Most of the time for these past months it has been fine; some issues initially with connectivity which were finally solved by using a static IP address for the NAS.
Recently it did the first strange thing. It had been performing incremental backups as normal, when a message came up saying the backup was unreliable and it needed to carry out a complete new backup. Anyway - no drama - I took it up and plugged it into the router to speed up the transfer (around 200GB on the drive). It worked fine and thereafter it went back to doing incremental backups normally.
Yesterday morning I noticed it was apparently running and running without progress, clicking on the bar icon revealed that TM was "Preparing Backup"; this state continued for several hours. So I stopped the backup, restarted the machine, and then last night at 22h00 I restarted it - by 08h00 this morning, ten hours later, it was still "Preparing Backup", so clearly something is wrong.
The NAS drive is accessible, ie.
- The 'Time Machine Backups' icon for the drive has appeared on the desktop
' The 'Diskstation (Time Machine)' is available in Finder under 'shared'
So this seems to be something to with Lion and/or with Time Machine.
Considering the infrastructure environment has been stable for months, the IP address of the drive is static, there appear to be no network connectivity problems... I am at a loss as to why now this irritating behaviour and, more to the point, at the moment I cannot make the Mac backup. I would be happy to do another full backup but, really, should not be necessary since this only happened (due to the recently problem) a few weeks back - and anyway what's the point of automated incremental backup if (a) it doesn't work reliably and (b) every 2-3 weeks you have to manually perform a full backup anyway??!!
Thanks in advance
Alastair

Alastair Mac wrote:
thanks. unfortunately a locally attached drive isn't a option that will work well for me (too long to explain, but it just won't - personal logistics rather than technology issues).
Are you sure about that? I have a Time Capsule (2nd hand) but I've switched back to a locally attached disk with Lion. Lion's new mobile backups provide some measure of backups when not connected to the backup drive. It protects against accidental deletions, but not hardware failure. Plus, the new bootable recovery partition in Time Machine and encryption tip the balance back in favor of the local drive - for me at least.
1. does it make sense to you that, until yesterday, it was working fine and then quite suddenly it stopped working?
I will say that it isn't surprising. There are some changes in Lion that affect networked Time Machine devices. The early versions of Lion got pretty annoying. 10.7.2 seemed to be better. I had to erase my Time Machine drive a couple of times and do new backups when it decided it needed to keep rebuilding the Spotlight index. Unless you connect with Ethernet, the reindexing will never finish. In your case, I would expect a 3rd party, flaky open-source product to perform even worse.
2. in my specific situation (going around and around "preparing backup" without any progress even in 24hrs of preparing, what can i do to restart the backup process? even if it means doing a clean backup i.e. junking the old one, i would live with it as at present (touch wood) my hard drive is OK and i have no historical version recovery issues.
With Time Machine, the only quick and easy way to reset things is to erase the Time Machine volume.
3. did apple / synology reach a point in previous releases of OSX and DSM which was stable and DID work, despite the need to use Netatalk? in other words, if i soldier on patiently, is it likely this will eventually get solved? or will this be a perennial problem? in the end, if twice a year i have to intervene, it doesn't really matter PROVIDED the backup itself is intact should the HD finally die. of course, if i have to intervene every couple of days, i may as well do it all manually.
I can't really answer that. I used Netatalk briefly several years ago and it scrambled my files. It has certainly improved somewhat, but obviously isn't stable. The part that really annoys me is that the change that Apple introduced in Lion wasn't really new. Apple introduced a more secure version of the AFP protocol 9 years ago. In Lion, all they did was make that more secure protocol the default and disabled the older protocols. There are a number of hacks that have been posted (sometimes by me) about how to set a flag in Lion so that it will continue to use the older protocol.
Synology seems to have better Mac support that some NAS vendors. Still, there was no reason they had to wait so long to update their software. Developers have had access to Lion for almost a whole year.
I would expect that companies would be always trying to improve their products, but the evidence doesn't support that assumption. I don't like Netatalk's shady open source extortion practices, but then no one else has stepped up to fund a stable open-source implementation of AppleTalk. People tend to blame Apple but they published the new specifications a decade ago and no one bothered to read them. Why should they care?
Personally, I think backups are too important to rely on such flaky software. I really like Time Machine but it is pretty complicated. Apple is able to make it functional over a network, but just barely. If you are using a 3rd party NAS, my suggestion would be to use NFS instead and backup with Carbon Copy Cloner or SuperDuper!. Even if you want to continue to try using Time Machine, a Carbon Copy Cloner backup would be a good thing to have too.

Initial Time machine backup to Time capsule results in kernel panic

I recently purchased a Retina display MacBook Pro (running Lion at the time) and transferred the data from an external hard drive with my Time Machine backups from my previous MBP. I also bought a new Time Capsule.
The first time I tried to back up to the Time Capsule from the Retina MBP via an ethernet connection it got to 40GB of 140GB before it shut down from a kernel panic. Interestingly, the Time Machine backup was successful when I used the external hard drive I was previously using for my Time Machine backups (connected via USB).
I don't think there is an issue with the Time Capsule because Finder can locate the Time Capsule and I can copy and paste files from the Macintosh HD to the Time Capsule disk.
I've done the following steps in order to try and fix the problem:
1. Repair permissions
2. Verify and Repair Macintosh HD
3. Updated the operating system to Mountain Lion (at which point I successfully completed a Time Machine backup to the external hard drive I was using for Time machine backups but was unable to backup to the Time Capsule without the computer crashing from a kernel panic)
4. Used Airport Utility to erase the sparse disk image bundle that had been created on the Time Capsule then tried to back up via ethernet to the time capsule - kernel panic ensued at 40GB of 140GB
5. Used Disk Utility to erase Macintosh HD and re-installed Mountain Lion. Transferred data from the external hard drive Time Machine backup from step 3.
6. Erased the sparse disk image bundle on the Time Capsule again.
7. Tried to backup to the Time Capsule again via Ethernet - kernel panic.
For each of the attemtps to back up to the Time Capsule I've used a different ethernet cable (Cat 5 and 5e) and plugged it into a different ethernet port on the Time Capsule each time. I've also tried using both Thunderbolt ports on the MBP (with an Ethernet to Thunderbolt adaptor).
I'm out of ideas on how to trouble shoot this problem and would greatly appreciate any ideas!!
If anyone knows how to read error logs, here's the readout from one of the kernic panics:
Thu Aug 9 23:58:29 2012
panic(cpu 6 caller 0xffffff80002c4794): Kernel trap at 0xffffff80003c0da3, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000130, CR3: 0x0000000000100000, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0xffffff80ebcc0500, RCX: 0x000000000000000a, RDX: 0x0000000000004000
RSP: 0xffffff80f3bebd60, RBP: 0xffffff80f3bebef0, RSI: 0xffffff80008cd400, RDI: 0xffffff80ebcc0500
R8: 0xffffff80ebcce29c, R9: 0xffffff80f3bebc50, R10: 0xffffff80f1b73cb8, R11: 0x00000000001c3b08
R12: 0xffffff80ebcce200, R13: 0xffffff80ea22d000, R14: 0xffffff80ebca2400, R15: 0xffffff8013e85388
RFL: 0x0000000000010207, RIP: 0xffffff80003c0da3, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x0000000000000130, Error code: 0x0000000000000000, Faulting CPU: 0x6
Backtrace (CPU 6), Frame : Return Address
0xffffff80f3beba10 : 0xffffff8000220792
0xffffff80f3beba90 : 0xffffff80002c4794
0xffffff80f3bebc40 : 0xffffff80002da55d
0xffffff80f3bebc60 : 0xffffff80003c0da3
0xffffff80f3bebef0 : 0xffffff80003c269d
0xffffff80f3bebf10 : 0xffffff800036523f
0xffffff80f3bebf60 : 0xffffff8000343c9b
0xffffff80f3bebfb0 : 0xffffff8000820057
BSD process name corresponding to current thread: kernel_task
Mac OS version:
11E2620
Kernel version:
Darwin Kernel Version 11.4.2: Wed May 30 20:13:51 PDT 2012; root:xnu-1699.31.2~1/RELEASE_X86_64
Kernel UUID: 25EC645A-8793-3201-8D0A-23EA280EC755
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System uptime in nanoseconds: 824267354982
last loaded kext at 119110896089: com.lacie.driver.LaCie_RemoteComms          1.0.1 (addr 0xffffff7f807df000, size 12288)
last unloaded kext at 195930890039: com.lacie.driver.LaCie_RemoteComms          1.0.1 (addr 0xffffff7f807df000, size 8192)
loaded kexts:
com.intego.iokit.VirusBarrierX6Service          10.6.14
com.intego.iokit.VBX6NKE          1
com.intego.iokit.BehavioralKext          1
com.intego.kext.VirusBarrier.AppBarrierKPI          10.6.14
com.intego.kext.VirusBarrierKPI          10.6.14
com.oxsemi.driver.OxsemiDeviceType00          1.28.13
com.apple.filesystems.afpfs          9.8.1
com.apple.nke.asp_tcp          6.0.1
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AppleBluetoothMultitouch          70.12
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AGPM          100.12.69
com.apple.driver.ApplePlatformEnabler          2.0.5d3
com.apple.driver.X86PlatformShim          5.0.0d8
com.apple.driver.AppleHDA          2.2.3f13
com.apple.driver.AppleMikeyDriver          2.2.3f13
com.apple.driver.AppleUpstreamUserClient          3.5.9
com.apple.driver.AudioAUUC          1.59
com.apple.driver.AppleSMCPDRC          5.0.0d8
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.iokit.IOBluetoothSerialManager          4.0.7f2
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleSMCLMU          2.0.1d2
com.apple.GeForce          7.2.8
com.apple.driver.AudioIPCDriver          1.2.3
com.apple.driver.ApplePolicyControl          3.1.32
com.apple.driver.AppleMuxControl          3.1.32
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.driver.AppleIntelHD4000Graphics          7.2.8
com.apple.driver.AppleIntelFramebufferCapri          7.2.8
com.apple.driver.BroadcomUSBBluetoothHCIController          4.0.7f2
com.apple.driver.AppleUSBTCButtons          227.6
com.apple.driver.AppleUSBTCKeyboard          227.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          33
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.0.4
com.apple.driver.AppleSDXC          1.2.2
com.apple.driver.AppleUSBHub          5.0.8
com.apple.iokit.AppleBCM5701Ethernet          3.2.4b8
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AirPort.Brcm4331          560.7.21
com.apple.driver.AppleAHCIPort          2.3.0
com.apple.driver.AppleUSBEHCI          5.0.7
com.apple.driver.AppleUSBXHCI          1.0.7
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleACPIButtons          1.5
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.5
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          195.0.0
com.apple.nke.applicationfirewall          3.2.30
com.apple.security.quarantine          1.3
com.apple.security.TMSafetyNet          8
com.apple.driver.AppleIntelCPUPowerManagement          195.0.0
com.apple.security.SecureRemotePassword          1.0
com.apple.driver.AppleMultitouchDriver          231.4
com.apple.driver.IOBluetoothHIDDriver          4.0.7f2
com.apple.kext.triggers          1.0
com.apple.driver.DspFuncLib          2.2.3f13
com.apple.iokit.IOSurface          80.0.2
com.apple.iokit.IOSerialFamily          10.0.5
com.apple.iokit.IOAudioFamily          1.8.6fc18
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.AppleHDAController          2.2.3f13
com.apple.iokit.IOHDAFamily          2.2.3f13
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.AppleGraphicsControl          3.1.32
com.apple.driver.X86PlatformPlugin          5.1.1d6
com.apple.driver.AppleSMC          3.1.3d10
com.apple.driver.IOPlatformPluginFamily          5.1.1d6
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.nvidia.nvGK100hal          7.2.8
com.apple.NVDAResman          7.2.8
com.apple.iokit.IONDRVSupport          2.3.4
com.apple.iokit.IOGraphicsFamily          2.3.4
com.apple.driver.AppleUSBBluetoothHCIController          4.0.7f2
com.apple.iokit.IOBluetoothFamily          4.0.7f2
com.apple.driver.AppleUSBMultitouch          230.5
com.apple.iokit.IOUSBHIDDriver          5.0.0
com.apple.driver.AppleThunderboltDPInAdapter          1.8.4
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.4
com.apple.driver.AppleThunderboltPCIUpAdapter          1.2.5
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.5
com.apple.driver.AppleUSBMergeNub          5.0.7
com.apple.driver.AppleUSBComposite          5.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice          3.2.1
com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.1
com.apple.driver.AppleThunderboltNHI          1.6.0
com.apple.iokit.IOThunderboltFamily          2.0.3
com.apple.iokit.IOEthernetAVBController          1.0.1b1
com.apple.iokit.IOUSBUserClient          5.0.0
com.apple.iokit.IO80211Family          420.3
com.apple.iokit.IONetworkingFamily          2.1
com.apple.iokit.IOAHCIFamily          2.0.8
com.apple.iokit.IOUSBFamily          5.0.8
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.7.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          177.5
com.apple.kext.AppleMatch          1.0.0d1
com.apple.driver.DiskImages          331.7
com.apple.iokit.IOStorageFamily          1.7.2
com.apple.driver.AppleKeyStore          28.18
com.apple.driver.AppleACPIPlatform          1.5
com.apple.iokit.IOPCIFamily          2.7
com.apple.iokit.IOACPIFamily          1.4
Model: MacBookPro10,1, BootROM MBP101.00EE.B00, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.3f32
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.198.19.21)
Bluetooth: Version 4.0.7f2, 2 service, 18 devices, 1 incoming serial ports
Network Service: Thunderbolt Ethernet, Ethernet, en4
Network Service: Wi-Fi, AirPort, en0
PCI Card: Apple 57762-A0, sppci_ethernet, Thunderbolt@104,0,0
Serial ATA Device: APPLE SSD SM512E, 500.28 GB
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2512, 0x1d180000 / 3
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 4

Any or all of the following third-party system modifications may be contributing to your problem:
LaCie drive software
VirusBarrier
I suggest you uninstall them according to the developers' instructions, reboot, and see whether there's any improvement. If there is, you can experiment with putting them back, one at a time, to identify which one is at fault. "VirusBarrier" is harmful and should not be reinstalled in any case.
If there's no improvement after making the suggested changes, post again.

Can I upload a Time Machine backup (Passport) made on my computer to my husband's computer?

I'm afraid that my present Macbook is starting to have problems. I have an old Time Machine backup that I made on a Passport USB drive last year (using OS 10.6) so I can transfer the contents of my computer to my husband's Macbook (also OS 10.6). But when I connected the Passport, I got a message saying, "This backup was created on a different computer. If you reuse this backup it can no longer be used by the original computer."
I'm not sure what the implications of this are. I'm pretty sure I created the backup on my computer, but it might have been made on my husband's computer. In any case, I'd like to make a new one on my computer and upload it to my husband's as planned. Question:
1. Is there a way I can check to see which computer the backup was made on?
2. If it's an old backup of what's on my computer, is there a way I can update it, rather than go through the long process of creating a new backup? (The USB drive is 1 TB, so an original backup takes forever!)
3. If it's a backup of what's on my husband's computer, can I overwrite it ("Reuse Backup"?) and then upload it to his computer?
Thanks for any information out there!

1. Hook up the drive to your husband's computer. If you don't get the same error message, then it is likely a backup of his computer. If you don't get an error message when attached to your husband's computer, enter Time Machine and check the admin user name.
2. Depends on answer to first question. If it is your computer, start a backup.
3. You can have 2 backups on the same drive. If it is your husband's backup, just start a new one for your computer.

Time Machine Backup - a lengthy process?

Similar Messages

Maybe you are looking for