The R&R forums are not intended for free technical support if you face issues. Veeam has a support department for that. Because of that, it’s not allowed to upload log files to the R&D Forum.

You can ask for technical advise or directly talk to veeams product manager there. And of course, If you want to post a technical issue, you can do that. But you have to post your case number for the product manager to have a reference of the issue.

————-

Back to your problem.

I will get soon some HPE Apollo appliances. If I face the same issue, i can report it back to you. I don‘t see any problems at the moment with a small Linux Hardened Repo Server (Ubuntu 20.04, 40TB), but I am not sure about the tmp partition. It‘s possible, that it is on the same partition as the root disk. Not a dedicated partition.

Well, I know that there is Veeam support and I’ve created a lot of cases there. But sometimes I got better feedback and hints in forum than from support and usually quicker. Maybe I should then post those questions at reddit where it’s ok to post technical problems.

Anyhow, I’ll create a ticket (probably more as those are different issues) on monday. I was a bit naive to believe Linux repositories would be less trouble than SMB shares ;)

Linux works fine, but I have learned that it needs more care as a simple SMB Share to work 100% flawlessly :)

The community pages here are a good place for this technical issues. You should be able to upload logs here. Someone will have an answer or the experience to comment on your issues :)

Is there documentation about Linux specific settings, other than https://www.veeam.com/kb2216?

We have dedicated Teams for managing the linux servers in my company. They install and configure for me the linux OS and hardware. I‘m happy that I hav
I only configure the part in your mentioned KB and the part where the xfs filesystem is created for cfs with reflink support.

I'm glad I don't have to do everything myself under Linux.

It’s the same here. But it’s not much that is in this KB. There are other KB’s for ssh settings etc, would be nice to have everything in one place.

I’ve found some KB’s and forum threads with more information regarding Linux repositories. I also reduced the concurrent tasks to 26 for each of the 2 volmes, as this looks more realistic. 

• added registry key on VBR server LinAgentFolder with /opt/veeam, changed permissions to 770 and Veeam owner  (https://forums.veeam.com/vmware-vsphere-f24/default-execute-directory-tmp-for-linux-servers-t65091.html)

• added registry key ConnectByIPsTimeoutSec with value 1200 (https://www.veeam.com/kb1976)

• added some sshd options to solve connection issues, as Veeam in V10 uses ssh/sftp tp copy the data mover to the servers. This changed in V11 and will be much easier (https://www.veeam.com/kb2985)

• ClientAliveInterval 30
  TCPKeepAlive yes
  ClientAliveCountMax 99999
  MaxSessions 200
  MaxStartups 100:30:200

   

• changed network interface buffers (https://forums.veeam.com/vmware-vsphere-f24/recommendation-for-linux-proxy-t65637.html#p405034)

• ethtool -G eno3 rx 2048 tx 2048

  ethtool -G eno4 rx 2048 tx 2048

  then added....

  ETHTOOL_OPTS="-G ${DEVICE} rx 2048 tx 2048"
  ... to /etc/sysconfig/network-scripts/ifcfg-bond0-port1 and /etc/sysconfig/network-scripts/ifcfg-bond0-port2

   

   

• created /etc/sysctl.d/99-mellanox.conf with some more tuning parameters (https://community.mellanox.com/s/article/linux-sysctl-tuning)

• 
  net.ipv4.tcp_timestamps=0
  net.ipv4.tcp_sack=1
  net.core.netdev_max_backlog=250000
  net.core.rmem_max=4194304
  net.core.wmem_max=4194304
  net.core.rmem_default=4194304
  net.core.wmem_default=4194304
  net.core.optmem_max=4194304
  net.ipv4.tcp_rmem=4096 87380 4194304
  net.ipv4.tcp_wmem=4096 65536 4194304
  net.ipv4.tcp_low_latency=1
  net.ipv4.tcp_adv_win_scale=1

If you have backups and copy jobs between 2 datacenter and lets say 3 servers at each dc, and you have server with 2 RAID volumes, would you use dedicated servers for backup and copy jobs or would you use one volume in each server for backup and the other for copy?

I see two scenarios:

3 Servers in DC1 —> Backup Jobs

3 Servers in DC2 —> Backup Copy Jobs

but only if all your workload is running in DC1. Consider a SOBR with the Raid Volumes included

—————-

If you have workload in both Datacenter, consider a mix of Backup Job and Backup Copy Job on each server.

Backup Job from Workload in DC1 on Raid Volumes in DC1, Copy Job to Raid Volumes in DC2

Backup Job from Workload in DC2 on Raid Volumes in DC2, Copy Job to Raid Volumes in DC1

But you don’t have a dedicated VBR server in this scenario…

Ok, in such a small environment this is perhaps a bit oversized.

We have workloads in both DC’s. It’s a stretched setup with mirrored IBM SVC volumes. We are backing up parts in one DC others in the second one. Then we copy the jobs from one side to the over so that we always have either the backup or the copy of a VM available if a DC is down.

We have one VBR server in a mgmt cluster, we are thinking about a cold standby VBR VB where we can import config backup if needed.