version 9.0.10007 can not connect QNAP TS-809U

- Log in to post comments

Если будут какие нибудь неофициальные или тестовые версии хотелось бы потестировать...
- Log in to post comments

Перед выпуском новой версии для большинства продуктов мы запускаем Бета компанию. О ней будет объявлено в письменной нотификации текущим пользователям (независимо от статуса контракта на техподдержку) + будет "приклеенный" пост в данной ветке форума.
- Log in to post comments

Hi to all, i have the exact problem described ! Qnap 4.1 and Acronis VM protect 9.10007, please i need the fix for my qnap with NFS. Can you send me the link via private message?
.
- Log in to post comments

Hi Stefano,
I have updated the original post in this thread so that link to hotfix build is more visible (it's also present in the thread above).
======EDIT=======
Acronis comment:
We're now preparing a public KB article with the link to the build (finally got an approval for publishing it, so there is no need to send private messages to everyone):
Please find the below FTP link where the builds with QNAP fix are uploaded (pick up the build locale you require):
NOTE: if you run into any issues with this new build you would still need to contact our support team for assistance.
======EDIT=======
Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager
- Log in to post comments

Hello Vasily,
I have a problem thats look like nearly the described one.
I courrently use Acronis Backup and Recovery 11.5 (39029) (universal license).
And the error occurs if I will recover it as a virtual machine (vmware) on a ESX(i) host.
The backup is stored on a QNAP TS-870-U-RP FW:4.1.2 (2015/01/26).
Best regards,
Börly Molitor
Code: 10.551.532(0x00A100EC)
LineInfo: 0xB320396ADFE3E67;
Module: disk_bundle_tape_off_glx_pic_39029
Message: Failed to resolve the path to the backup in archive 'arl:/AAAA6753-9F1E-4FC1-A033-38B75B75190D/FFB2E337-B73A-4EB7-BFD0-D93350603BCE/1E8AFAAC-3631-4491-A8AD-9F43B29E711A/4FAE68B9-A681-4E97-A3C0-8D3F9FD1DE1E'.
Code: 4.194.944(0x00400280)
LineInfo: 0xA1D3981537C68767;
Module: disk_bundle_tape_off_glx_pic_39029
Message: Failed to open the metadata directory.
Code: 5.832.764(0x0059003C)
LineInfo: 0x28EDBBF5D246C445;
Module: nfs_supp_glx_pic_39029
Message: Failed to mount the NFS share. ('143.21.88.36:/backup')
Code: 5.832.765(0x0059003D)
LineInfo: 0xCAA935157D7E71E3;
Module: nfs_supp_glx_pic_39029
Message: A non-zero exit code has been returned while mounting the NFS share. ('nolock,soft,vers=3', 32)
Code: 5.832.765(0x0059003D)
LineInfo: 0xCAA935157D7E71E3;
Module: nfs_supp_glx_pic_39029
Message: A non-zero exit code has been returned while mounting the NFS share. ('nolock,tcp,soft,vers=3', 32)
Code: 5.832.765(0x0059003D)
LineInfo: 0xCAA935157D7E71E3;
Module: nfs_supp_glx_pic_39029
Message: A non-zero exit code has been returned while mounting the NFS share. ('nolock,soft', 32)
Code: 5.832.765(0x0059003D)
LineInfo: 0xCAA935157D7E71E3;
Module: nfs_supp_glx_pic_39029
Message: A non-zero exit code has been returned while mounting the NFS share. ('nolock,tcp,soft', 32)
- Log in to post comments

Hi All,
I solve it :)
I quick workaround, change the 'Root-Squash' settings auf no.
regards,
Börly Molitor
- Log in to post comments