pk1057

Hmm, you choose a different config then I. I have Job Mode Type Server, Managed By Backup Server Then under Computer the Ip of the container In Backup Mode check File Level with backup directly from live file system because we cannot install the snapshot kernel module under objects the path This leads for me to a working backup If it's still not working, you have to wait till the weekend so i have time to build a more up to date container

You say file backup from linux server and then you add the ip address and after this you have to choose the first point (IMHO server) as backup controller, not agent. In this way it works for me. CentOS 7 is supported

At first use only ip, remove dns name. At second did you setup user access as i did, and does he install the files ? Can you reach the container and log in via ssh ? /var/log/veeam and /var/log/veeam/config are directories so you have to do a ls and then there resides some files insider where you can cat.

Sorry for the delay, but my internet broke down yesterday. I made a clean install on a different unraid server and it works for me. First what i saw you used my dns name veeam-linux.fritz.box is this name really reachable for you ? At second my system installed nearly everything during setup of the server. I attached some pictures of the setup. After the server setup and the installation of the files you can control in the console of the container if it looks like the earlier screenshot and if the /opt folder is populated with some files from the veeam installation ls /opt/veeam/ should show transport upload and ls /opt/veeam/transport/ should show certs libattr.so.1 libfuse.so libuuid.so.1 vddk vddk_6_7 veeamagent veeamtransport libacl.so.1 libblkid.so.1 libNtfsLib.so scripts vddk_6_0 vddk_7_0 veeamimmureposvc VeeamTransportConfig The container is running in privileged mode ? and uses brX as network device ? You can ssh into the containers address with the user veeam-backup and the password ? what does the logfiles in /var/log/veeam and /var/og/veeam/config say ?

Sorry, veeam not unraid...

Well ok, i will investigate this evening. What unraid version did you use ?

At a frist try: Start the console on the container and type in yum update This should update the container the container on docker hub is currently 2 years old. After the update restart the container and try again.

Yes, thats all. For usb it depends , passthrough or shared folder. Or do you wanna Backup to an USB device ? This should bei possible via iscsi

The container gives Veeam access directly to the /mnt folder und you can use it also as a Backup target. I use Veeam and unraid together with an local TapeChanger. All my PCs have also the veeam Client installed for Automatic backup. For me, it is the most sophisticaded Network Backup solution.

Sorry No.

No, the container installs only a backup client/peer on your Unraid System. Veeam itself is a windows based application with plenty of features

What have you already done ? Installed the container, and setup a windows system with Veeam B&R Community edition ?

Hello, will there be any chance to support tap drives (st0) and changers ? Because i can't see these two devices in the overview lsscsi shows them: [9:0:0:0] tape HP Ultrium 5-SCSI Z63U /dev/st0 [9:0:0:1] mediumx TANDBERG StorageLoader 0495 - But your tool ignores them.

Ok, the AUR package guys used the following: https://aur.archlinux.org/packages/tbs-linux_media-git sed -i s/^obj-\$\(CONFIG_VIDEO_TDA1997X\)/\#obj-\$\(CONFIG_VIDEO_TDA1997X\)/g "$srcdir/media/drivers/media/i2c/Makefile" rm "$srcdir/media/drivers/media/rc/Makefile" rm "$srcdir/media/drivers/media/usb/tm6000/Makefile" rm "$srcdir/media_build/backports/rc-cec.patch" touch "$srcdir/media/drivers/media/rc/Makefile" touch "$srcdir/media/drivers/media/usb/tm6000/Makefile" touch "$srcdir/media_build/backports/rc-cec.patch" It seems always to boil down to the tm6000 driver The official linux wiki from tbs does also the sed replacements like the one in the thread. His only addition is the removal of the TM6000 (trident) driver section, so it seems a valid solution.

Hmm, it was possible for me to build the driver on a ubuntu 22.04 VM with the steps described in the thread. Someone else modifed the v4l config, which could also be a possibility or do we running on some unraid specific problem ? I'm not sure what's the proper way to build the drivers for unraid to support your efforts, i poked around but didn't find a documnetaion how to do this...