TiH fails during backup validation.
I got a new computer, Win10 OS. I wanted to get an "as received" image for disaster recovery purposes. I had created a boot disk for Acronis True Image Home 2019 which had worked previously on the laptop (also Win10) I used as a test bed just to see if it works for me. I plugged an external hard drive into the computer, a 2 TB Western Digital "My Book" formatted in NTFS, booted to the rescue disk and set up a backup--full backup, no encryption, noof the SSD on which the computer OS is installed. The backup appeared to run fine but when it hit the validation portion I get the following error:
Failed to open backup D:\AcronisBackups\9205_all_200601_full_b1_s1_v1.tib. Make sure the backup location is accessible and contains all versions of the backup.
The "_b1_s1_v1" was not part of the file name I had created for the backup. Acronis apparently appended that to the name on its own.
I've tried to save the log file but when I connect the drive to another machine any attempt to copy, move, or open the log file gets an "access is denied". Other files on that drive open fine. Nothing created by Acronis 2019, however, does.
The computer (a Dell) used F12 to access the boot menu during startup. First two options Windows Boot Manager (the default) and the optical drive also using UEFI. I used the second to boot to the Acronis disk.
I opened the log in the environment, right clicked on it and selected the option to save giving it a filename with a .txt extension. Any attempt to access that text file gives me an "access denied" error.
After the validate, which I had set to automatically run at the end of the backup, had failed, I tried to validate separately. That gave me the same error.
David, the log should normally be saved using the default name which is the date/time of the backup .log
Please try another validate of the backup .tib file from the installed version of ATI which should work.
Moved the external drive over to the computer on which Acronis was installed. Tried to validate (browse to file, right click, hover over "Acronis" until option pops up, then click "validate"). Got the following error:
Failed to add the backup to the backup list. The backup may be locked or corrupted. Also, make sure the folder contains the last volume of the backup, and does not contain a renamed copy of the same backup.
More details:
More information about this error and solutions may be available online in the Acronis Knowledge Base.
To access the online resource manually, enter the event code at: https://kb.acronis.com/errorcode/
Event code: 0x01010005+0x01010005+0x00040014+0x0000FFF0+0x80070005
Clicked 'Knowledge Base" button which got me:
There is no information about this error available now. You can use the links below to search for any additional information that might be available.
David, sorry but not looking too good at this point. What happens if you double-click on the .tib file? Does it open to show the contents and if so, can you browse randomly through the contents?
When I double click on it, it asks for a user name and password. I have no idea what to enter because I didn't set any when making the backup.
David, ATI doesn't assign any user name & password credentials to backup files at all in my experience.
If you opt to encrypt the backup before it is created, then a password would be required to open the file later but again, there is no user name involved.
The only time when a user name & password is normally asked for, is when connecting to files which are stored on another computer or NAS device, in which the credentials are those needed for the remote location, not your own PC.
This is an external drive which I have physically moved to the computer on which Acronis is installed. I get the same prompt for login when I attempt to access any Acronis files created with Acronis 2019. I can access files created with the old Version 11 that I have (but can't use on recent computers with SSD's--it does not seem to recognize them). Other files, I'm able to open fine.
David, do you have ATI 2019 installed on this computer you are using, or is it an older version?
Acronis True Image 2019 Build 17750
David, all I can suggest is to try again with making a new backup of your new computer.
Check that you are using the same BIOS boot mode for the ATI rescue media as is used by the installed Windows OS, and if any issues are encountered, try again to save the log to a place where it can be accessed later (keeping the .log file type).
After consulting with a colleague, here's what seems to be working. Don't ask me why it works but it appears to do so:
- While still in Windows, create a folder on the backup destination drive to contain the backup file. It must be a completely empty folder, no other folders or files in it.
- Boot to the Acronis Boot disk. (Linux Based)
- Back up the drive with the backup file location set to the folder created above.
- File is now accessible and validates.
And from within Windows on the system from which I installed True Image 2019, I can browse the backup file and see contents.
David, good that you have found a method that works for you here though I am as puzzled as you must be as to why you have to jump through those hoops!
Personally I very rarely use any of the older deprecated Linux based rescue media other than for ancient hardware with unsupported non-PAE processors, and have never seen these issues when using the WinPE media from any of the recent versions (2016 thru to 2020).
Actually, turns out I was mistaken about it being Linux based media. The computer I have True Image installed on is an older WXP desktop (for...reasons we need not go into here). On the XP machine I have been unable to download the ADK's required for building WinPE restore media. When I attempt to do so, I first get a prompt that .NET has to be installed. That downloads, then the installer cycles back to downloading the .NET again in an endless loop. I cannot proceed beyond that. I was, however, able to create Linux based boot media on that computer.
However, on checking my notes, I was reminded that I had briefly installed it as a trial on my personal laptop, a Win10 machine. I made the WindowsPE boot media using that, and that's the disk I've been using.
So, it was Windows based boot media, not Linux to which all the above applies.