Recovery von NAS
Ich werde im RecoveryManager nach den Zugangsdaten für das NAS gefragt. Wenn ich die Anmeldeinfos eingebe, Benutzer und Passwort, wird der Verbindungstest als OK angezeigt. Wähle ich dann das betreffende Backup auf dem NAS aus wird mir mitgeteilt, das die Anmeldeinfos nicht vorhanden sind.
Was kann ich tun?
Es ist ATI 2016 Build 6581. Das Recoverymedium wurde mit dieser Version erstellt (CD) und gestartet mit diesem Medium über UEFI Boot.
PC FSC Lifebook A 544, i5-4200, WIN 10 64-Bit, aktueller Patchstand
Es ist ATI 2016 Build 6581. Das Recoverymedium wurde mit dieser Version erstellt (CD) und gestartet mit diesem Medium über UEFI Boot.
PC FSC Lifebook A 544, i5-4200, WIN 10 64-Bit, aktueller Patchstand
It is ATI 2016 build 6581. The Recovermedium was created with this version (CD) and started with this medium via UEFI boot. PC FSC Lifebook A 544, i5-4200, WIN 10 64-bit, current patch level
Cnemo, I would grab the previous 6571 rescue media (you can download the .iso from your account and burn to disc if you don't have it already) and test to see if the same behavior exists or not to help identify if it is a problem just with the new version, or in both.
Have you ever been able to connect to the NAS with your rescue media?
I've found that for my NAS, I must have an account/password set on the NAS - I cannot connect to public shares or the root of the NAS, it must be a specific folder and one where a user account and password has been setup already. On some NAS devices, you can just enter the username and password. On other NAS devices, you must enter the username as
NASDEVICENAME/Username
And, on some NAS devices, becuase the NAS uses UNIX/LINUX, you must make sure to enter usernames exactly as they were created on the NAS - they can be case sensitive.
Hi Bobbo,
danke für die schnelle Beantwortung. Leider komme ich erst jetzt dazu zu testen.
Test mit der Vorgängerversion 6571 (engl. Recoverydatei als ISO downgeloadet) führt zu anderem Ergebnis. Hier kann nach Eingabe der Anmeldedaten (Benutzer, Passwort) der Test nicht erfolgreich abgeschlossen werden.
Also ich kann mich im ATI 2016 nach Eingabe der Anmeldedaten mit dem NAS verbinden. Es ist übrigens ein Buffalo Linkstation LS-WXL/R1 mit einem3TB RAID . Das Backup wird ordentliche erledigt und auf dem NAS abgelegt. Also Zugriff ist kein Problem.
Beim Recovery finde ich das NAS auch problemlos über die Netzsuchfunktion und kann dann auf die Freigabe und weiter bis zum interessierenden Backupfile browsen.
Dort kommen dann die genannten Hinweise auf die Eingabe der Anmeldedaten. Nach Eingabe bringt der Test mit Build 6581 ein "OK", bei Benutzung des Build: 6571 "Keine Verbindung".
Was passiert, wenn ich die Widerherstellung starte, weiß ich nicht, da ich das alles nur als Test für den Ernstfall mache und davon ausgehe, dass es nach dem Start kein zurück mehr gibt.
Hi Bobbo,
danke für die schnelle Beantwortung. Leider komme ich erst jetzt dazu zu testen.
Test mit der Vorgängerversion 6571 (engl. Recoverydatei als ISO downgeloadet) führt zu anderem Ergebnis. Hier kann nach Eingabe der Anmeldedaten (Benutzer, Passwort) der Test nicht erfolgreich abgeschlossen werden.
Also ich kann mich im ATI 2016 nach Eingabe der Anmeldedaten mit dem NAS verbinden. Es ist übrigens ein Buffalo Linkstation LS-WXL/R1 mit einem3TB RAID . Das Backup wird ordentliche erledigt und auf dem NAS abgelegt. Also Zugriff ist kein Problem.
Beim Recovery finde ich das NAS auch problemlos über die Netzsuchfunktion und kann dann auf die Freigabe und weiter bis zum interessierenden Backupfile browsen.
Dort kommen dann die genannten Hinweise auf die Eingabe der Anmeldedaten. Nach Eingabe bringt der Test mit Build 6581 ein "OK", bei Benutzung des Build: 6571 "Keine Verbindung".
Was passiert, wenn ich die Widerherstellung starte, weiß ich nicht, da ich das alles nur als Test für den Ernstfall mache und davon ausgehe, dass es nach dem Start kein zurück mehr gibt.
H i Bobbo,
Thank you for the quick reply. Unfortunately, I am only now to test. Test with the previous version 6571 (English Recoverydatei as ISO downloaded) leads to different results.
The test can not be completed successfully after entering the login data (user, password).So I can connect in the ATI 2016 after entering the registration data with the NAS.
By the way, it is a Buffalo Linkstation LS-WXL / R1 with a 3TB RAID. The backup is done properly and stored on the NAS. So access is no problem. When the recovery I find the NAS also easily via the net search function and can then browse to the release and continue to the
interesting backup file.There then the mentioned references come to the input of the registration data. After entering, the test with Build 6581 brings an "OK",
when using the build: 6571 "No connection".What happens when I start the rebuild, I do not know, because I do it all as a test for the emergency and assume that there is no back after the start.
I'm using Google translate so sorry for losing a little bit in the translation process :)
It sounds like 2016 is working when connecting to the NAS from within Windows, but you're not having luck connecting to the NAS with the rescue media in build 6571 "no connection", but can in 6581? To clarify, is one version of the rescue media working, but not the other, or are neither of the versions actually connecting for you? If one is working, which version is connecting?
If one is working and can see the NAS and connect with credential and can navigate to the backup .tib files, you are in good shape for a recovery. If possible, you could test a recovery to a new/different drive. That way, you can verify that recovery works, but without compromising the original hard drive and the data on it. If you can do such a test, remove the original drive as a precaution, put the new/test drive in it's place and then recover to the test drive. Afer reocvery, make sure it boots and if it does, all is well. You can then remove the test drive and put the original back in it.
It is better to test a recovery in this manner now to make sure things work as expected, than to find yourself in a situation where you need to be able to recover, but find yourself unable to for one reason or another.
Hi Bobbo,
thanks again. I'm surprised about the google translation quality. I've never used that before. So let's try in english it's always a good training.
Summary: It's possible with both versions of the Recovery Manager (6571 & 6581) to search through the network and to navigate till the folderlevel where the backupfile is located. So I see the regarding file *.tib. That's possible without any seperate inputted credetials. Only then when I click the *.tib-file, I get the hint to input the credentials.
So, I agree that the one and only way is to do an full restore on a diffrent drive. I agree further that it is nessecary to do that, to be sure having an "real backup" in the case of cases. I will prepare that but I haven't enough time now. So the result will take a while. I will present my results here if they are available.
Hi Cnemo - thanks for that. Yeah, Google translate can be pretty robotic at times, but usually gets the point across, but sometimes it's harder to decipher when trying to get into the technical aspects. :)
As you're able to navigate to the backup file in both versions, I don't think this has anything to do with NAS authentication at all, anymore.
This actually sounds like you have set a password on the backup file itself and that is what is being prompted for. You can test this in Windows by navigating to the backup .TIB files and attempting to double click on one ot open it up, or by right clicking on it and under Acronis, select "mount" to try and mount it as a drive letter. If there is a password on the backup, you should be greeted with a password prompt and would need to enter the password to unlock it. You can also verify if there is a password on the backup by going into the Acronis application and editing the backup script >>> navigate to the "advanced" tab and look under Backup Protection.
Once a password has been set on a backup script/task, there's no changing it and no recovery option, so if there is one, hopefully you remember what it is!
Hi Bobbo,
thanks for that new interesting view.
But I cant remeber to set a password during backup and if I navigate down the path of a backupfile (*.tib) with the MS explorer using double clicks I am able to do that till the file level and can access and open the files. I did so down in to the user path to a pdf- document and opened it - no problems. So I'm sure there is no password and the request for entering one has to do with the connection to NAS. I have to test it in the way we discussed yesterday - I have to do a real restore.
Hi Bobbo,
today I did a restore. I did it only on a USB drive an I testet only the recovery of selected files from the full backup.
It works without errors. The only thing I had to do was to ignor the hint wich should force me to input username and password for the NAS :-). No Problems to acces the backupfile, no problems to navigate to files inside the backup.
So - a lot of fuss about nothing! Now I trust my backups and hope that I will never have to use them.
Thanks for your help.
Glad to hear it - that's the most important aspect for sure!
So, if I understand correctly, you're NAS is probably using a public/open share, but Acronis prompts for a password by default and just closing it seems to let it through after that. Good to know as my NAS has user accounts on it so I have not tried with a public share before.
Hi Bobbo,
a little bit different. It's not a public share. I use the admin account with a password. The credential is fixed in the drive mapping using the Windows procedure to connect to a network resource and it was nessecary to apply this when I selct this drive as the destination for the backup in the Acronis procedure.