Time machine can never restore system - unacceptable!!

Question

Level 1

74 points

Time machine can never restore system - unacceptable!!

Why is it that time machine can never restore an entire system?!? This is ********. I bought all these mac machines so that at the time of failure I can restore the entire system. But it never works!!

I connected my backup disk and went into recovery HD. Choose restore from system. It starts the process and then quickly told me a error occured please reboot and try again. I called apple and gave them the log they said there's nothing they can do and the only thing I should do is use migration assistant. Except migration assistant always leave apps in a half broken state. What I wanted is a full byte by byte recovering. Do I really need to go back to tape backup? Why can't time machine do it's job?

Jun 12 22:34:27 localhost Unknown[310]: 2013-06-12 22:34:27.260 OS X Installer[356:707] NSSoftLinking - The Librarian framework's library couldn't be loaded from (null).

Jun 12 22:34:27 localhost Unknown[310]: 2013-06-12 22:34:27.261 OS X Installer[356:707] NSSoftLinking - The function 'LBCurrentProcessHasUbiquityContainer' can't be found in the Librarian framework.

Jun 12 22:34:27 localhost OSInstaller[356]: OS X Installer application started

Jun 12 22:34:27 localhost OSInstaller[356]: 1 display(s) found.

Jun 12 22:34:27 localhost OSInstaller[356]: Display[1] is NOT using OpenGL acceleration.

Jun 12 22:34:27 localhost OSInstaller[356]: @(#)PROGRAM:Install PROJECT:Install-729

Jun 12 22:34:27 localhost OSInstaller[356]: @(#)PROGRAM:OS X Installer PROJECT:OSInstaller-419

Jun 12 22:34:27 localhost OSInstaller[356]: Hardware: MacBookPro10,1 @ 2.30 GHz (x 8), 16384 MB RAM

Jun 12 22:34:27 localhost OSInstaller[356]: Running OS Build: Mac OS X 10.8 (12A269)

Jun 12 22:34:27 localhost OSInstaller[356]: Env: DYLD_NO_FIX_PREBINDING=1

Jun 12 22:34:27 localhost OSInstaller[356]: Env: __CF_USER_TEXT_ENCODING=0x0:0:0

Jun 12 22:34:27 localhost OSInstaller[356]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin

Jun 12 22:34:27 localhost OSInstaller[356]: Env: PWD=/

Jun 12 22:34:27 localhost OSInstaller[356]: Env: SHLVL=1

Jun 12 22:34:27 localhost OSInstaller[356]: Env: __OSINSTALL_ENVIRONMENT=1

Jun 12 22:34:27 localhost OSInstaller[356]: Env: CI_DEFAULT_OPENCL_USAGE=0

Jun 12 22:34:27 localhost OSInstaller[356]: Env: OS_INSTALL=1

Jun 12 22:34:27 localhost OSInstaller[356]: Env: _=/System/Installation/CDIS/LCA.app/Contents/MacOS/LCA

Jun 12 22:34:27 localhost OSInstaller[356]: Entering system restore mode

Jun 12 22:34:28 localhost Unknown[310]: 2013-06-12 22:34:28.455 OS X Installer[356:707] *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

Jun 12 22:34:28 localhost Unknown[310]: 2013-06-12 22:34:28.456 OS X Installer[356:707] *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

Jun 12 22:34:31 localhost OSInstaller[356]: Memory statistics for 'Select a Backup Source' pane:

Jun 12 22:34:31 localhost OSInstaller[356]: Physical Memory Allocation: 1107 MB wired, 11 MB trapped, 176 MB active, 140 MB inactive, 14950 MB free, 15266 MB usable, 16384 MB total

Jun 12 22:34:42 localhost Unknown[310]: 2013-06-12 22:34:42.540 Terminal[362:707] NSSoftLinking - The Librarian framework's library couldn't be loaded from (null).

Jun 12 22:34:42 localhost Unknown[310]: 2013-06-12 22:34:42.541 Terminal[362:707] NSSoftLinking - The function 'LBCurrentProcessHasUbiquityContainer' can't be found in the Librarian framework.

Jun 12 22:34:50 localhost Unknown[310]: 2013-06-12 22:34:50.816 Terminal[368:707] NSSoftLinking - The Librarian framework's library couldn't be loaded from (null).

Jun 12 22:34:50 localhost Unknown[310]: 2013-06-12 22:34:50.817 Terminal[368:707] NSSoftLinking - The function 'LBCurrentProcessHasUbiquityContainer' can't be found in the Librarian framework.

Jun 12 22:35:44 localhost OSInstaller[356]: Memory statistics for 'Select a Backup Source' pane:

Jun 12 22:35:44 localhost OSInstaller[356]: Physical Memory Allocation: 1161 MB wired, 8 MB trapped, 198 MB active, 149 MB inactive, 14868 MB free, 15215 MB usable, 16384 MB total

Jun 12 22:36:51 localhost OSInstaller[356]: Memory statistics for 'Select a Backup Source' pane:

Jun 12 22:36:51 localhost OSInstaller[356]: Physical Memory Allocation: 1178 MB wired, 10 MB trapped, 209 MB active, 149 MB inactive, 14838 MB free, 15196 MB usable, 16384 MB total

Jun 12 22:36:52 localhost Unknown[310]: 2013-06-12 22:36:52.025 OS X Installer[356:707] *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

Jun 12 22:36:52 localhost Unknown[310]: 2013-06-12 22:36:52.025 OS X Installer[356:707] *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

Jun 12 22:37:05 localhost OSInstaller[356]: Memory statistics for 'Select a Backup' pane:

Jun 12 22:37:05 localhost OSInstaller[356]: Physical Memory Allocation: 1185 MB wired, 9 MB trapped, 210 MB active, 149 MB inactive, 14831 MB free, 15190 MB usable, 16384 MB total

Jun 12 22:37:10 localhost OSInstaller[356]: Using cached backup size 205517094912

Jun 12 22:37:10 localhost OSInstaller[356]: Memory statistics for 'Select a Destination' pane:

Jun 12 22:37:10 localhost OSInstaller[356]: Physical Memory Allocation: 1186 MB wired, 7 MB trapped, 210 MB active, 149 MB inactive, 14832 MB free, 15191 MB usable, 16384 MB total

Jun 12 22:37:15 localhost OSInstaller[356]: Preventing machine sleep.

Jun 12 22:37:15 localhost OSInstaller[356]: Memory statistics for 'Restoring' pane:

Jun 12 22:37:15 localhost OSInstaller[356]: Physical Memory Allocation: 1201 MB wired, 11 MB trapped, 210 MB active, 150 MB inactive, 14812 MB free, 15172 MB usable, 16384 MB total

Jun 12 22:37:15 localhost OSInstaller[356]: [RESTORE] erasing disk 'Macintosh HD'

Jun 12 22:37:15 localhost OSInstaller[356]: [RESTORE] erase started

Jun 12 22:37:17 localhost OSInstaller[356]: [RESTORE] erase completed

Jun 12 22:37:18 localhost OSInstaller[356]: Physical memory statistics immediately before turning on virtual memory backing store:

Jun 12 22:37:18 localhost OSInstaller[356]: Physical Memory Allocation: 1204 MB wired, 9 MB trapped, 218 MB active, 150 MB inactive, 14803 MB free, 15171 MB usable, 16384 MB total

Jun 12 22:37:18 localhost OSInstaller[356]: Activated virtual memory backing store at mount point '/Volumes/Macintosh HD'

Jun 12 22:37:18 localhost OSInstaller[356]: [RESTORE] started vm on target disk.

Jun 12 22:37:18 localhost OSInstaller[356]: [RESTORE] System already has a recovery system.

Jun 12 22:37:18 localhost OSInstaller[356]: [RESTORE] ensuring permissions on /Volumes/Macintosh HD

Jun 12 22:37:18 localhost OSInstaller[356]: [RESTORE] restoring from: /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD

Jun 12 22:37:18 localhost OSInstaller[356]: [RESTORE] restoring to: /Volumes/Macintosh HD

Jun 12 22:37:19 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DS_Store to /Volumes/Macintosh HD

Jun 12 22:37:19 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100 to /Volumes/Macintosh HD

Jun 12 22:37:40 localhost OSInstaller[356]: (Nop) Error -36 ioErr while copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/101 to (null)

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] Restore operation was brought down successfully.

Jun 12 22:37:40 localhost Unknown[310]: 2013-06-12 22:37:40.468 OS X Installer[356:9713] NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on void _NSAlertWarnUnsafeBackgroundThreadUsage() to debug. This will be logged only once. This may break in the future.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs to /Volumes/Macintosh HD/.DocumentRevisions-V100

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage to /Volumes/Macintosh HD/.DocumentRevisions-V100/.cs

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0 to /Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0 to /Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0 to /Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/100 to /Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] failed to copy file '/Volumes/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/100', critical, failing.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] Error enumerating directory: file://localhost/Volumes/Time%20Machine%20Backups/Backups.backupdb/Gary%E2%80%9 9s%20Retina%20Macbook%20Pro/2013-06-11-095816/Macintosh%20HD/.DocumentRevisions- V100/.cs/ChunkStorage/0/0/0/100

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] _NodeOperation() failed with exit code -43.

Jun 12 22:37:40 localhost OSInstaller[356]: [RESTORE] Restore operation was brought down successfully.

Posted on Jun 19, 2013 8:05 AM

Reply

Answer 1

a brody

Level 10

82,841 points

Jun 19, 2013 8:47 AM in response to aapl.crox

To give Time Machine the full working order, having a backup drive at least twice as big as the original drive is generally a good idea. Secondly, if your Time Machine backup was done on an earlier model running an earlier operating system than what came with the computer, you may run into issues that way. Migration Assistant is better equipted to handle older operating systems, and even it has difficulty with old PowerPC software that was left behind on from pre-2006 trying to migrate to an Intel Mac. It works a lot better PowerPC to PowerPC or Intel to Intel. Tape backup takes too long. I recommend clone backing up what you always need, and only keep your archival information in a two separate partitions that themselves are cloned to each other.

Reply

Answer 2

aapl.crox Author

Level 1

74 points

Jun 19, 2013 11:37 AM in response to a brody

I'm restoring 10.8 on this macbook and that's exactly what it came with. I was not aware of the twice as big requirement, if that's the case why didn't they warn me. I also don't think this failure is a result of lack of space?

Reply

Answer 3

a brody

Level 10

82,841 points

Jun 19, 2013 11:39 AM in response to aapl.crox

Why didn't they? Cause it may not be as generally well known as some other issues. I've found it through trial and error.

Reply

Answer 4

ds store

Level 7

30,705 points

Jun 19, 2013 11:56 AM in response to aapl.crox

What I wanted is a full byte by byte recovering.

Then you want a bootable clone.

Most commonly used backup methods

Reply

Answer 5

Pondini

Level 8

38,863 points

Jun 19, 2013 5:51 PM in response to aapl.crox

aapl.crox wrote:

. . .

Jun 12 22:37:40 localhost OSInstaller[356]: (Nop) Error -36 ioErr while copying /Volumes/Time Machine Backups/Backups.backupdb/Gary’s Retina Macbook Pro/2013-06-11-095816/Macintosh HD/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/101 to (null)

There's a corrupted file in the Versions database, causing an I/O error. Probably corrupted on your system, and copied to the backups.

You might be able to restore an earlier backup, if the damage was recent.

Or, erase the HD, install a fresh copy of OSX, and use Setup Assistant when it starts up to transfer your stuff. See Using Setup Assistant on Mountain Lion or Lion for the gory details.

I'm not sure how to avoid that folder; try selecting only your user accounts; that should get all the home folders and permissions transferred properly.

Then start the similar Migration Assistant app and transfer only Applications. I suspect that will work.

Last, use Migration Assistant again, selecting only the Other files and folders on <computer name> <disk name>. I suspect that may fail. If it does, and there's other stuff at the top level you want, use the Time Machine browser (the "Star Wars" display) to restore it.

Reply

Answer 6

aapl.crox Author

Level 1

74 points

Jun 22, 2013 11:01 PM in response to Pondini

Actually Pondini, I got around that error by plugging the drive directly to the macbook instead of mounting it over the network. But not I'm bumped into another error (I had my hopes up just for a sec bu at 30% it halted again....sigh...time machine...).

In the installer log, it says error copying the Library folder to the destination drive. Is there any workaround for this? I can tell it's gone past the Applications folder from the log..now I just need to fight past the Library folder...

Reply

Answer 7

Jun 23, 2013 1:10 AM in response to aapl.crox

For a full system restore, Time Machine can be lacking and

problematic. The best use of Time Machine is for incremental

recovery, i.e. an OS update that didn't work, an app update

that is not up to par, or a simple "oops, why did I delete that"

recovery. Basically used to roll back to some past point in

time.

For a full system backup and replacement, a clone is really the

only way to go. It will be faster and less problematic with the

added benefit that you can immediately reboot to the clone

if need be and deal with the problem later.

Reply

Answer 8

Pondini

Level 8

38,863 points

Jun 23, 2013 4:42 AM in response to aapl.crox

aapl.crox wrote:

Actually Pondini, I got around that error by plugging the drive directly to the macbook instead of mounting it over the network.

That's odd -- it shouldn't matter.

In the installer log, it says error copying the Library folder to the destination drive. Is there any workaround for this? I can tell it's gone past the Applications folder from the log..now I just need to fight past the Library folder...

Same advice as before: either try an earlier backup, or erase the drive, install OSX, use Setup Assistant on first boot to transfer your user accounts and data, but not Applications (or Settings).

Then try Applications only via Migration Assistant.

You can also transfer Computer Settings only via a separate run of Migration Assistant.

Depending on where the damage in /Library is, one of those may fail.

If Migration Assistant won't transfer the apps because of the problem in /Library, you'll have to copy them from the backups manually, via the Finder, but some will have to be reinstalled from the original discs or downloaded again, and most serial numbers/purchase keys re-entered.

Reply

Answer 9

aapl.crox Author

Level 1

74 points

Jun 23, 2013 10:20 AM in response to Pondini

I did migration assistant and it went through just fine (however with half the apps settings broken of course, typical migration assistant). So any ideas why the restore won't go through?

I've tried the earliest revision of the backup (9 months ago, the first backup) and it still failed. It's just so ridiculous.

Reply

Answer 10

Pondini

Level 8

38,863 points

Jun 23, 2013 10:40 AM in response to aapl.crox

There's one corrupted file we know of (from the message), and apparently at least one other as well. That pretty much guarantees problems of one sort or another, no matter what backup app you use. And, just as ALL hardware fails, sooner or later, NO app, even a backup app, is perfect.

But it's always prudent to keep secondary backups. See the green box in Time Machine - Frequently Asked Question #27 for some suggestions.

Reply

Answer 11

Feb 23, 2014 9:30 PM in response to aapl.crox

Hi aapl.crox

I got this error too. I agree it is unacceptable to backup successfully but then fail to restore.

I backed up using the version of Time Machine from mavericks and then when my hard drive failed tried to restore it after booting using my original Snow Leopard DVD.

I think Apple have changed the format of the backup so that it fails when attempting to restore a backup created from a more recent version of OSX.

Anyway after cursing Apple for a while I came across someone suggesting to use the Command-R recovery to do something else.

I rebooted using the Command-R and was then able to restore my time machine backup successfully and avoid the Error - 36 error that we both received.

This is probably too late for you but may help some poor sod in the future.

Cheers

Clint.

Reply

Answer 12

Dec 25, 2015 3:59 PM in response to Sydney Clint

I have the same problem!

Its impossible to restore from a time machine backup. It feels stupid to have invest so much time to do backups trough time machine. Apple should not deceive it's customers!

And on top of that I get some different errors with some of the backups "There is not enough space on the computer to install this backup". What the heck??? I it's the very same computer.

Should not have trusted apple!

Reply

Answer 13

a brody

Level 10

82,841 points

Dec 26, 2015 12:41 PM in response to Zorzorzor

Hi Zorzorzor,

If you don't have a solution, or an inquiry that could lead to one for the thread initiator, it is wise to start a new thread, so people can help you.

Welcome to Apple Support Communities.

Some facts some people may not be aware of with Time Machine:

1. As an archival software, it needs twice the storage on the backup drive as the original, or more when configuring.

2. The archival feature of it operates recursively based on Time. As such you will get monthly, weekly, daily, hourly backups to the point where space allows it.

3. When space runs out, it deletes the most frequently made backup first.

4. It does not create a bootable backup. If your system restore drive partition gets corrupt, you'll have to find another means to restore your system.

5. Related to #4, you'll want to read this tip: What should I do if I find a used machine without the original CDs?

6. It occupies processing space when making a backup, and like all backups works best when you are not doing any production with the computer.

Turning off the automatic backup, will optimize the performance of your computer, and putting it in the menubar using its System Preference, will allow you to manually turn on an additional backup via the menubar icon for it. Manually making a Time Machine backup, gives you the opportunity to copy the folder made by your previous backups to another destination to avoid the deletion in #3 from being problematic. Remember, once data does not exist on the original, it is only a matter of time before your Time Machine backup gets rid of it. Better to safely archive it elsewhere when you have the opportunity to.

As long as you keep these things in mind, Time Machine is a great tool. If you do not keep them in mind, then you can run into unexpected problems.

Reply