Unable to restore backup from USB (password incorrect).
OK Acronis boffins, here is another one for you.
We are trying different restore scenarios and the one we are attempting today is restoring a backup of our main SQL server to similar hardware from a USB drive.
The scenario is thus - over the weekend we run a backup job which backed up the full server to a USB drive. This completed with no troubles at all. I made sureI could see the files from the console and everything worked as expected.
So, trying to restore the server using the boot disk we get to the part where we select the image on the USB drive to restore from, type in our password (the backups are encrypted) wait a few seconds and we are taken back to the Access Credentials box. We cannot get any further than that. I even attached the drive to one of our servers that have the Acronis agent on it and could browse the archive with no problems after typing in the password.
Is this a known bug? Any ideas?
Thanks, Mark

- Se connecter pour poster des commentaires

OK, the problem is MUCH bigger than we initially thought. However the other issues are for another post.
So as mentioned previously, we can backup with no problems. We are able to access the files contacined in the encrypted archive using the Management Console and Windows Explorer (after successfully entering our password), browse files, copy files out of the TIB file, everything seems fine. But as mentioned when trying to restore the server from the boot disk we cannot get past the password. So unfortunatley we cannot restore our server from backup (USB). So today I created a brand new job, backup is being saved to our usual place (NAS) but in a completely different folder, encrypted with password. Backup successful, I can browse the TIB file both in the console and via windows explorer. So we booted off the disk and tried to restore the server to our lab server - yet again it cannot get past the password screen!!! (I am now trying ANOTHER backup job without a password - I will let you know how I get on)..
Anyway, I am thinking - since the last agent update, should there be an updated BOOT DISK image? I have downloaded and I am using the one that downloads via the console - I am assuming that is up to date?
Bottom line is, I cannot access any server backups via the boot disk, no matter where I save them to. The archives are fine becuase I can browse them and extract data from them - but totally unable to restore complete servers. I've not tried restoring to a VVM yet as I dont have the equipment available to test this (it is being used elsewhere currently).
- Se connecter pour poster des commentaires

UPDATE - I have just fininshed the backup of the server WITHOUT encryption.. I am running a restore from the boot disk and this time it allows me to progress to actually restoring the data (the job is currently running so fingers crossed) - however whilst a short term workaround we cannot restore any of our old backups from the bootdisk. Something has gone wrong since the last update.
Don't get me wrong, this isn't fixed as I am having to recreate all of our Server OS backup jobs and schedule them to run as soon as possible so we have working backups of a type. File areas, SQL and Exchange Databases restored via the console remain unaffected.
Is this a bootdisk/acronis12v3 mismatch issue?
Sorry to drop this on you on a Friday afternoon :)
- Se connecter pour poster des commentaires

Mark,
Have you tried running the Acronis Bootable Media Builder (it's installed by default along with Acronis Backup 12) and re-creating the media after the product update? The behavior you describe indeed might be related to media build inconsistency.
Just in case here's a trial version (allows recovery only) of the media of proper (latest 3689) build: http://dl2.acronis.com/u/AcronisBackup12/Boot_media.iso
Thank you.
- Se connecter pour poster des commentaires

"Anyway, I am thinking - since the last agent update, should there be an updated BOOT DISK image? I have downloaded and I am using the one that downloads via the console - I am assuming that is up to date?"
I did write this in my update... However I will try another one "just in case"...
- Se connecter pour poster des commentaires

Just checked - yes I am using the most up to date boot disk.
BUT - for arguments sake I downloaded the one from the link you gave me and I am still getting the same problem. :)
- Se connecter pour poster des commentaires

Hi Mark,
I've just tried reproducing the issue, but was unable to - probably the symptoms in your case are somewhat different. Please see attached screen shots. What I did is created backup of entire machine saving it to a network share. The archive encryption was enabled with default AES256 algorithm and upon recovery via bootable media I got prompt for password and it was accepted with no problems. Both backup and recovery was performed using 3689 build (I've used bootable media from the link above). Can you please attach some screen shots illustrating the behavior you get? Right now I can only guess that the problem is related either to particular machine which is booted from the bootable media (somehow hardware-related) or to some specific symbols in the password (less probable).
Thank you.
Fichier attaché | Taille |
---|---|
407001-137362.png | 280.22 Ko |
407001-137365.png | 348.94 Ko |
- Se connecter pour poster des commentaires

OK, so we have tried restoring to totally different hardware but the same error occurs - continually asking for a password, even though we KNOW we are entering the correct password as we browse the archive via the management console and windows explooer (via the TIB file)..
Did you require any log files from us to assist?
- Se connecter pour poster des commentaires

Mark,
If you have re-created the media + tried accessing backup via different protocols (local/network) and the problem is still reproduced this may only mean that the issue is related to the actual backup archives themselves: probably an issue with some symbols in the password or something else. In order to continue with the investigation we'll need to reproduce the issue locally in our QA lab and to get there, we'll need some sample backup from your environment with which the problem can be reproduced. The place for uploading the backup archive files can be obtained from our support team via submitting a support request. It's hardly possible to address such issues in a forum thread I'm afraid.
Thank you.
- Se connecter pour poster des commentaires

No worries - I'll be in contact.
FWIW, the password contains no special symbols, just uppercase, lower case and a numbers.
- Se connecter pour poster des commentaires