• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Slow Export to Server


Active Newcomer
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, 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 ?

Uwe Koch


ADSM.ORG Moderator
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


TSM noob with 10 years expirience
ADSM.ORG Moderator
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.
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?


Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 16.7%
  • Keep using TSM for Spectrum Protect.

    Votes: 31 57.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 16.7%
  • Other (please comement)

    Votes: 5 9.3%

Forum statistics

Latest member