Skip to main content

Restore from other machine backup

Thread needs solution

I had a desktop crash in a nonrecoverable state and I had to replace it. I now want to restore from the previous machine to my current machine and I cannot seem to. If I go the the backups in Windows explorer and double click the I get an error that I either don't have permissions or the backup is corrupt. I do not see anything that would allow me to import the backups into Acronis. All of the FAQs appear to just cover bare metal restores and not machine replacement. 

HAs anyone an idea as to how to do this? 

0 Users found this helpful

Andrew, welcome to the Acronis user community.

Hopefully the backup is OK.

Migrating to a new system is essentially the same process as a bear metal restore. You need to ensure that Windows is activated on the new machine before commencing (which you have presumably done). What you need to do is to create Windows RE recovery media (called simple method in the recovery media builder). This will ensure that all necessary drivers for your new hardware are included. When booting the recovery media, make sure you select UEFI version of the recovery media as the new PC is most likely to boot in UEFI mode rather than BIOS mode.

Try this and report back if it does not work.

Ian

Sorry I was away for a few weeks and just got back to this. If I use the BMR option will I be able to recover a single file or group of files or will it completely overwrite the files and OS? 

Andrew, if you do a bare metal recovery then you will wipe the target disk drive and restore back the OS and applications etc as they existed on the original system at the time the backup image was created.

If you have moved to a new computer with a new clean install of Windows and applications, then you would probably be best advised to just recover your user files and data from the old machine backup.  You can do this using different methods but perhaps the simplest, assuming you have installed Acronis on the new system, is to double-click on the backup file (.tib or .tibx) in Explorer and then use normal Copy & Paste controls to grab your user data.

Note: I would recommend making a full backup of the working new system before attempting any recovery of any data stored in any system folders such as AppData just in case you 'break' something with the restore!  You should not attempt to recover installed programs or registry files etc!

See KB 65547: Acronis True Image 2021: how to restore files from a backup (Windows) and scroll down the page to 'How to restore files in File Explorer' which you should find easier to use if only wanting to recover some files, allowing you to use normal Copy & Paste commands.

Andrew, can you confirm what version of Acronis was used to create the backup files, what type of files they are, i.e. are they .tib or .tibx files?  Are you using the same version or a later version of Acronis when trying to open these files?

These were made with the same version of Acronis as I am using them to open them. The files are TIBX files. 

Have these tibx files been renamed, moved or any associated files deleted, i.e. any 12kb metadata files that may have been present?

Can the files be validated?

Andrew,

See if this helps

Add existing backup to backup list

@enchantech I just tried the import and go a similar error the error said to go to 

https://kb.acronis.com/errorcode/
Event code: 0x01010005+0x01010005+0x01E50015+0x01E5001A+0x0004000D which revealed nothing. 

 

@Steve Smith How do I verify the backup since Acronis does not know about it?

Right-click on the tibx file in Explorer will bring up a context menu with an option for Acronis then within that menu option are options for Validate and Mount (for disk backups only).

That fails also. I think all five of those backups are corrupt and I will not be able to recover the files I was looking for. Hard to believe that the backups have all been bad but, I guess so. 

Andrew,

Error code 0x01010005 likely means that the backup failed to be added to the backup list.  This suggests that you have two backups that contain the same index in the same folder.  If you have copied other backups from another location to the same folder you are working with here, that could be causing the issue.  If this applies try removing the copied backups into a different folder and then try opening the backup.

Error code 0x0004000D suggest that your backups may be on a network attached device like an NAS.  If this is the case are you asked to provide credentials when you attempt to open the backup?  If yes and you do so does this error occur after that?  If yes then please verify that there are only ASCII characters in your username and password. If characters other than ASCII are used in credentials this error code can be produced.

Have you removed any backups from this backup folder and if you have what did you use to do so?  If you used anything other than the applications built in clean up function then you will get these corrupted backup errors.

 

Enchantech,

So I did use the same folder for backups from the original machine and the new machine. They were on a NAS but not copied there nor renamed. I copied them to a new folder on a local machine and retried the import and verification and got the same issue. 

 

So no issues with credentials, duplicate index, and naming. Now there five backups in the folder with the last one being made closest to the the computer crash. There are major time gaps and I am not sure if I had cleaned up the folder but if I did I would have used the application to do it. I am a backup engineer in the company I work for and I am well aware that to alter anything outside of the application creates major issues.  

Andrew, what type of backup are you using here with the files listed in your image above?  Is it a Differential backup (which seems likely looking at file sizes for files 1 to 3, but not for file 4)?

Normally I would expect the first file to shrink to just 12KB for an incremental scheme unless your retention settings are large but that wouldn't explain why the first backup is nearly twice the size of the subsequent 3 files.

If you know which backup files belong to the new machine I recommend that you create a new folder on your NAS then move those backups to that new folder.  At that point use the Add existing backup on the latest of those backups and see if you still get the error.

Steve Smith wrote:

Andrew, what type of backup are you using here with the files listed in your image above?  Is it a Differential backup (which seems likely looking at file sizes for files 1 to 3, but not for file 4)?

Normally I would expect the first file to shrink to just 12KB for an incremental scheme unless your retention settings are large but that wouldn't explain why the first backup is nearly twice the size of the subsequent 3 files.

Steve,

This is an incremental scheme. Perhaps that is why it is determined to be corrupt.  

Enchantech wrote:

If you know which backup files belong to the new machine I recommend that you create a new folder on your NAS then move those backups to that new folder.  At that point use the Add existing backup on the latest of those backups and see if you still get the error.

Enchantech,

I did that and I still go the same error.  

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Andrew Madsen wrote:
Enchantech wrote:

If you know which backup files belong to the new machine I recommend that you create a new folder on your NAS then move those backups to that new folder.  At that point use the Add existing backup on the latest of those backups and see if you still get the error.

Enchantech,

I did that and I still go the same error.  

Hello Andrew.

I would like to advise you to contact our support line with a detailed description of the current issue. Such errors may report corrupt backups and would require further investigation.

Please follow the link to open a new case: https://kb.acronis.com/content/8153

Thanks in advance!