Slow Export to Server

[uwekoch]

For a migration project we have to transfer archive data from the old outdated TSM server to a new one.
The old server is running on AIX 7.1 with TSM 6.2.3.100, using 3592-4 drives.
The new server is running on Redhat 7.4 with Spectrum Protect 8.1.2 and a large disk subsystem as data storage.

The network between both servers allows a SCP file copy with about 50 Mb/s, but the TSM export to server runs with about 8 Mb/s only. This speed occurs after the database part of the export and after the mount of the tapes. So it is the current speed from 3592 tape through AIX, network and RedHat to the disk subsystem. All parts have been checked individually. The bottleneck must be between the 2 TSM servers. With this speed it would take more than half a year to transfer all data.

Any hints about tuning the transfer to at least the network speed ?

Regards
Uwe Koch

 

[marclant]

It's not that easy to identify the bottleneck. The transfer could also be slow if it's slow reading the data from the source media, or slow writing the data to the target media. Or if the database response time is slow on the source, target or both.

For the network tuning part, you could try using a different TCPWindowsize on the source and target. Default is 64K. Try 128, then 256, then 512. Alternatively, you could try 0 and let the OS set the TCPWindowsize

 

[Trident]

Hi,
TCPWindowsize to 0 is my best offer, on both systems. Verify that both systems support rfc 1323. You could also try replicating data from source to target, that part may give multiple sessions. You should in that case patch it up abit firstly. 6.3.6.x or even better to 7.1.

 

[sergio.morales]

I am going to assume you have server-to-server communication set up? Are you certain that the HLADDRESS is set up to use the fastest interfaces on both sides?

sERGE