Topics started by Ralf
Hi,I’d be interested in getting feedback from people that are already using HPE Apollo’s or other high density servers with local storage as repository server. It seems that a lot of people are currently planning to use them.what is you setup? Number of servers? Number of disks? Which type and size of RAID? Number of VM’s / source data how is your performance? do you use them only as backup target or as copy source as well? which filesystem ReFS/XFS with blockcloning/reflink
Hi,I’m a bit confused about the difference of old Veeam forum and new community discussion board. I just posted in old forum, but as it’s not allowed to post log file content there, I’ll give it a try here too. I'm setting up our first Linux based backup repository based on Apollo 4510 server (Veeam 10). Now the jobs have different kind of errors. Before I open a case I wanted to know if those problems are known issues with an easy workaround. This all seems to be related to load, as it happens only when multiple backups are running. But there is not much CPU load and no errors in the usual linux logs.#1 at this time backup jobs were writing active fulls with 1,5GB/s over LAN to the server, CPU was 90% idle (52 cores). Nothing interesting in /var/log messages.[15.05.2021 15:19:27] <326> Error Failed to upload file D:\Veeam\Backup\VeeamAgent64 to /tmp/VeeamAgent0bc9a8bd-ebd8-44b8-a373-44510aefd89f[15.05.2021 15:19:27] <326> Error Failed to find terminal prompt: timeout occ
We are running 11a with IBM SVC storage integration and storage snapshots. On our Linux proxies there are regularly leftover multipath devices. In the case below the only mapped device at this time is the 5GB disk (mpatha, for testing). There is no backup running anymore, no 10 TB disk should be there. The amount of devices varies from host to host, some don’t have any leftovers. # multipath -lmpathsqu (3600507680c80802f3000000000037e70) dm-41 ##,##size=10T features='0' hwhandler='0' wp=rwmpathsqh (3600507680c80802f3000000000037e82) dm-15 ##,##size=10T features='0' hwhandler='0' wp=rwmpathsqt (3600507680c80802f3000000000037e77) dm-39 ##,##size=10T features='0' hwhandler='0' wp=rwmpathsqs (3600507680c80802f3000000000037e6b) dm-37 ##,##size=10T features='0' hwhandler='0' wp=rwmpathsqr (3600507680c80802f3000000000037e67) dm-35 ##,##size=10T features='0' hwhandler='0' wp=rwmpatha (3600507680c80802f30000000000274b6) dm-6 IBM,2145size=5.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=
We have a location in the US where our VBR server in DE seem to have some connection issues sometimes. Latency and packet loss I see in smokeping is not that high, even better than for most of our other remote locations. Still we see errors like below in out backup and offload jobs for 2-3 VMs out of 35 on a daily base. The IP is the local proxy there. Processing xxxx Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.31.132.113:2508 First job retry is successful most of the time. Anyhow, I’d like to get rid of those errors. Support suggested to change following regkeys to adjust.ConnectByIPsTimeoutSecAgentStartTimeoutSec But this did not change anything. I think we need settings for retries not timeouts. Any other ideas? Network team already checked everything and did not find anything. As I wrote, monitoring graphs also do not look too bad.
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.