eversys wrote:The Veeam server is directly attached to the autoloader with a PCI Express SAS card. Local files on the Veeam server are being directly backed up to the autoloader. The server also has 2 local NICs along with a 4 port NIC, all ports attached to different switches. However, the files are being processed locally and not over the network. We have another job defined, which backs up a seperate VMware host - here of course, the NICs and switches would play a part.
We are not aware of any other processes or I/O intensive operations at time of the backup - starts late evening.
Any further ideas?
Maybe create a file copy job as a test? Pick a VBK of sufficient size and see if you can get greater than 8Mb/s. If not then perhaps there is something wrong between the SAS card and the Tape drive. Try different SAS Cables or shut everything down, boot tape drive and after it initializes then boot the server to see if that clears the issue. You might also run a tool such as IOMeter against your storage target to see what kind of IOPS you can get. I get ~150MB/s to 800MB/s with 16 x 4TB drives in RAID6 on a 730XD depending on the block size and IO randomness of the test. Maybe you have a degraded RAID set that is causing the problem? If you are running RAID5 and you lost one of your drives, if that is a 1TB or larger drive it can take a few days to restore parity depending on your hardware config.
Interested to know what is the source of the degradation once you locate it.