Skip to main content

Recovering in place - Files and Folders

Thread needs solution

In the past when recovering files from a "Files and folders" backup I've always used Windows Explorer to access the backed up data.  But today I needed to recover a file from an FTP backup so I decided to do the recovery from within ATI.  I knew that doing a recovery of a full partition - or at least the C: drive - required a reboot after ATI messed around with boot records.  I did not expect this for a folder recovery.  Is that typical, or does it depend on the specific file or folder?  In this case it was the \Users\ files for a user that was not logged on. 

0 Users found this helpful

Was it an entire user profile, or just specific data files?  I haven't seen a file/folder backup require a reboot, but have never tried to recover an entire user profile this way and suspect the reboot may be required if it is trying to restore the full user profile. 

Also, what was on the disk where the files were being recovered to?  Mine are usually just data drives (no OS on them) so have never experienced any reboot needed for file/folder recovery.  However, it seems like if an OS is detected on the destination drive, True Image wants to reboot because of possibly "locked" hibernation files from Windows Fastboot/Fast start.

Basically, if just recovering data files/folders from a profile and if the destination disk does not have an OS on it, no, I have not heard of a reboot being required.  Most MVP's and frequent forum users will agree that we don't recommend continuing with recoveries that require a reboot because of the potential for bootloader modifications that can make the OS unbootable if it fails to revert correctly.  In those cases, it's better to cancel, and use rescue media to start the recovery instead as that avoids any potential changes to the main OS bootloader.

And sorry, I just re-read and see you were recovering from FTP... yeah, really strange for needing a reboot unless it was the full user profile you were trying to recover and you were trying to restore it to the regular users directory in Windows.

It's almost impossible to do any recovery from remote (eFTP, NAS, network share) if the recovery starts in Windows and needs a reboot as the connection will be severed and the temporary rescue media will need credentials to access the remote location again.  

In some cases, it may be better to copy the .tib backups to a local external hard drive first, then do a recovery.  And if possible, try to recover to a temp location first (like another spare external drive that doesn't have an OS on it).  Once recovered, you can copy it to the final destination or use xcopy or robocopy or something like that.  If it's any "data" that is fully integrated into the OS (windows system folders, application folders, full user profiles), you have to treat it like raw data and not try to merge it with the OS directly... you'll have missing/broken registry keys, services, etc. otherwise.

The recovery was for an entire user profile.  And the \Users\ directory is on my C: drive along with the OS.  (I didn't even know major directories like that could be moved.)

I absolutely do not want to do recoveries that require a reboot.  If I have to recover this again I'll do it from a recovery medium.  Or maybe I'll FTP the needed .tib files to a local drive and see if Explorer can access the backup files.