Error backing up QNAP SMB shares after P20201202

[kwinsor]

Hi All,

I was backing up by QNAP 6-bay NAS in my home lab using Veeam with my NFR Pro Partner key. Everything was working great until I applied the latest update which is 10.0.1.4854 P20201202. After the update, my backup fails with the following error: 2020-12-12 11:09:32 AM :: Error: Agent: Failed to process method {MessageChannel.EstablishConnectionByRoles}: Unsupported NAS protocol version. Message version: 20, Required version: 9

I cannot see to figure out why. Anyone who may have information on this error message please let me know.

Thanks.

[Dima P.]

Hello Kent,

Is that SMB or NFS? Any chance that the protocol version has been changed on the source after the patch? Thanks!

[Dima P.]

Hello Kent,

Discussed with RnD folks, the issue might be related to Veeam B&R update as well. Can you please raise a support case and let our support team check your upgrade logs? Thank you!

[kwinsor]

Hi,

Noting changed with the source after the patch. I am backing up SMB share. I can open a case for sure. It is a lab and using NFR key though so I hope I can get support for it.

Thanks.

[kwinsor]

Hi,

I opened Case #04545067 and attached logs. Thank you.

[Dima P.]

Thanks for sharing, passed to the QA team.

[jvlad]

Having similar issue but the message version and required version are backwards.
Am at the latest version of veeam.

Failed to enumerate NAS backup metadata files Details: Agent: Failed to process method {MessageChannel.EstablishConnectionByRoles}: Unsupported NAS protocol version. Message version: 9, Required version: 20

Any update on your ticket from veeam support.

[Dima P.]

Jason,

Based on the case investigation results it looks like an upgrade glitch (the file proxy version is not updated), can you please raise a support case as well and share it with me? Thanks!

[jmc]

hello,

i have the same problem now. when rescan or import backups i get the same message. also here the latest version of veeam. is there a solution?

jeff

[PetrM]

Hi Jeff,

Can you please open a support request and share case ID with us?

Thanks!

[kwinsor]

I got nowhere with support on this issue. We went through Veeam data mover file version checks and removal of Veeam components on the proxies and repo to no avail. In the setup logs of the patch deployment, the logs indicated that the setup did not succeed but the installer at the time said it did succeed.
In the end, because this was a lab, I nuked the entire Veeam installation. I rebuilt with the December patch and a hardened Ubuntu repo and my NAS SMB share share backups now work fine. Obviously, this drastic measure would not be possible in a production environment which is concerning that something like this could happen.

[PetrM]

Hi Kent,

Please keep in mind that you always have a possibility to escalate a support case if you feel that it's not on the right track.

Thanks!