Case 00887227
==================================================
Hello guys,
I am trying to set up a new backup repository with a Qnap TS-653 Pro-8G NAS. This model has an Intel Celeron quad-core processor and 8GB RAM, so my goal is to run the datamover/Linux integration package on it in order for us to obtain the highest transferspeeds and offloading file merging to the NAS.
Everything seems fine, except the fact that the repository size and free space are not displaying correctly.
Since the BusyBox implementation of Linux on the QNAP does not support the -x command, first of all I modified the 'mount.pm' script that issues the "df" command with the -x option. I initially removed the "-x vmfs" argument from line 72, but the error was still popping up. After reviewing the WmiServer.BackupSrv log from C:\ProgramData\Veeam\Backup, I also removed the invalid "-- P" option from the same line and the error went away. Now repository size and free space are populated inside the Veeam B&R GUI, however the results returned (340,3 MB) do not reflect the actual repository capacity (7,2 TB):
==================================================

==================================================
By request of the engineer I also checked the full list of Perl modules that must be installed on the Linux server to make sure that everything is OK in the environment. All required Perl modules are installed except the 'threads' module.
I don’t want to bother the engineer with an issue that is clearly not related to Veeam but has more to do with a Linux-based storage device that is not running plain vanilla Linux operating system.
Instead my intent is to also reach out to the community and see if anyone has successfully set up a Qnap NAS running the datamover/Linux integration package on it.
Any suggestions and thoughts will be greatly appreciated.
Thanks and Regards,
Massimiliano