Error message "invalid password" with import backup in 9.5.4

[sam.lowry]

Hi,

We are testing the new 9.5.4 B&R, and we have a strange behavior : when we import an encrypted VBM file we obtain the message "invalid password". This message does not appear if we import the same file in a B&R v 9.5.0.
We don't have this message when we import the VBK file...
We have opened a case at Veeam Support : 03521723
Does anybody has ever seen this problem ?
thank you,

[PTide]

Hi,

Did you move your VBR installation to another machine by any chance? If so, then the behaviour that you see is expected and is described in this article (including solutions). Otherwise please keep working with the support engineer.

Thanks!

[sam.lowry]

Hi, no it wasn't moved. I am just trying to import a veeam backup "vbm" file from an external hard drive into a Veeam B&R which has just been upgraded on a Windows 2016 VM Server. We did not have this message with the previous version on the same VM... But as i said we don't have the error message when we import the vbk file, so it can be resolved like that... I was just wondering if someone else has already seen the message...

[AlphaKilo]

Hello. we have exactly the same problem here.

V9.5.4 - Import of an encrypted file (* .vbm) and the error message "Invalid password"
The result of the support case would interest me

Thanks in advance

[veremin]

Unfortunately, the case is in French, so even if there is a solution, we cannot provide you with it, but have you checked the KB article above?

Anyway, you'd better create your own ticket to get the issue solved.

Thanks!

[foggy]

This behavior doesn't look expected, so I also encourage you to open a case for investigation.

[mikame]

I have been using BackupCopy to USB for offline backups from production VM's and few times a year I bring this USB to another Veeam testing system/installation to test if I can restore all VM's from USB. For some reason one Job is giving me this, the other jobs are not. I even recreated it from scratch, the password is 100% right. The test system Veeam version has the latest update 4b, the "production" veeam has Update 4a, perhaps this affects to.

Anything new/solutions on this one for the one's who had the same prob?

[veremin]

The causes might vary dramatically, so, while obvious the best recommendation still is to open a support case. Thanks!

[GACcc]

Hello sam.lowry

I dont know if you still have this issue but I had a similar problem, after the update, it seems that special characters in the password were removed.
Try the same pw but removing the special characters.

Best
C

[sam.lowry]

Hi, yes i still have this issue. We can get around with opening the "vbk" file which has never refused the password. So we are not in a "no way" but i think this is not normal...
And there is no special characters in the PW...

Regards,