For a long time, Veeam has been telling its users to not use "low-end NAS boxes" (eg, Synology, QNAP, Thecus) as backup repositories for Backup & Replication (VBR), even though these Linux-based devices should be compatible if they have "x86" architecture (as opposed to ARM).
The reality is that none of these devices use "bog standard" Linux distributions, and due to their appliance-based nature, have some significant limitations on what can be done to their custom distributions.
However, there are many folks—both as home users or within small/budget-limited businesses—who are willing to "take their lumps" and give these things a shot as repositories.
I am one of them, particularly for my home "lab" environment. I've written about this use case (in particular, the headaches) a couple of times in this blog [1, 2], and this post joins them, addressing yet another fix/workaround that I've had to implement.
Installing Veeam Data Mover service Error: Failed to invoke command /opt/veeam/transport/veeamtransport --install 6162: /opt/veeam/transport/veeamtransport: error while loading shared libraries: libacl.so.1: cannot open shared object file: No such file or directoryFailed to invoke command /opt/veeam/transport/veeamtransport --install 6162: opt/veeam/transport/veeamtransport: error while loading shared libraries: libacl.so.1: cannot open shared object file: No such file or directory
After failing to find a fix after some Linux-related searches, I discovered a thread on the Veeam Community Forum that addressed this exact issue .
- Download the latest ACL library from Debian source mirrors. The one I used—and the one in the Forum thread—is http://ftp.debian.org/debian/pool/main/a/acl/libacl1_2.2.53-10_amd64.deb
- Unpack the .deb file using 7zip
- Upload the data.tar file to your Synology box. Feel free to rename the file to retain your sanity; I did.
- Extract the tarball to the root directory using the "-C /" argument:
tar xvf data.tar -C /
- If you are using a non-root account to do this work, you'll need to use "sudo" to write to the root. You will also need to adjust owner/permissions on the extracted directories & files:
sudo tar xvf data.tar -C /
sudo chown -R root:root /usr/lib/x86_64-linux-gnu
sudo chmod -R 755 /usr/lib/x86_64-linux-gnu
- Create soft links for these files in the boxes filesystem:
sudo ln -sf /usr/lib/x86_64-linux-gnu/libacl.so.1 /usr/lib/libacl.so.1
sudo ln -sf /usr/lib/x86_64-linux-gnu/libacl.so.1.1.2253 /usr/lib/libacl.so.1.1.2253
- Last, get rid of any previous "debris" from failed transport installations
sudo rm -R /opt/veeam
- Select the "Backup Infrastructure" node in the VBR console
- Select the Linux node under Managed Servers
- Right-click on the Synology box being updated and select "Properties..." from the popup menu.
- Click [Next >] until the only option is [Finish]. On the way, you should see that the Synology is correctly identified as a compatible Linux box, and the new Data Mover transport service is successfully installed.