Slow performance to Immutable storage

[andreas2012]

Hi,

Case #05825435

We have implemented a new BackupCopy-Job Repo, Immutable storage server running RHEL 9, xfs configured and with a 10Gbit Fiber card.
When we use this repo, we only get around 90-100MB/s, so to me it seems like its stuck on 1Gbit.
I have looked at the Linux configuration, and cannot see why it should not go any faster.
I have talked to the network guys, and they do not see any problems either, so I guess there must be something in the Linux config ?


Settings for eno1:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseSR/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10000baseSR/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Auto-negotiation: off
Port: FIBRE
PHYAD: 0
Transceiver: internal
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

[root@localhost sysctl.d]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 68:05:ca:d9:78:14 brd ff:ff:ff:ff:ff:ff
altname enp11s0f0
inet 10.11.3.3/28 brd 10.11.3.15 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 68:05:ca:d9:78:15 brd ff:ff:ff:ff:ff:ff
altname enp11s0f1

Any suggestions ?

Thanks for reply
/R
Andy

[PetrM]

Hi Andreas,

I guess the best action plan is to continue working on it with our support team. Also, you may review the job statistics to find the "bottleneck" and research a bit deeper the problematic data processing stage.

Thanks!

[bct44]

Hello Andreas,

I'm not sure rhel 9 is supported yet but i can make some suggestions:
- What kinds of raid are you using? Storage(HDD, SSD, NVME)? Did you set up raid cache on controllers?
- When running your jobs with an active full, how is your throughput and bottleneck? Does your read is rather than write?
- Have you tried to run some tests like fio or stressdisk on the fs used for the backup repo? What is the result?

[karsten123]

RHEL 9 is not supported for linux hardened repository.
Backup traffic for copies goes from data mover of the source repository to the target.
What system do you have as primary landing zone for your backups?
Please check all swichtes between the repository.