• 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.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    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.

Poor performance backup

aleman07

Newcomer
Joined
May 22, 2019
Messages
1
Reaction score
0
Points
0
Hi,

I have a poor backup performance with many nodes, the network department told me that all is Ok, but I have slowly backups with this error....

Node: Windows Server 2012 R2. API TDP DB2 v7.1.2
Server: ISP v 8.1.13

06/03/2022 06:02:21 ANS0361I DIAG: sessSendVerb: Error sending Verb, rc: -50
06/03/2022 06:26:27 ANS0361I DIAG: cuConfirm: Received rc: -50 trying to receive ConfirmResp verb
 

Trident

TSM/Storge dude
ADSM.ORG Moderator
Joined
Apr 2, 2007
Messages
555
Reaction score
64
Points
0
Location
Oslo, Norway
Website
www.basefarm.no
Hi,
If you get these rc50 during backup, have a look at the serverside actlog to see if any weird things are happening there.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,780
Reaction score
625
Points
0
Location
Canada
Website
www.ibm.com
The RC 50 means that there was a communication error that caused the socket to be dropped.

From an application perspective, the network starts as soon as it hits the TCPIP stack on the source system until it leaves the TCPIP stack on the target system. Most network departments start with the network cable on the back on the machine. The OS logs on the SP client and the SP server machines may provide you with some clues if the issue is on either machine.

You could do a simple test for the network, on the Windows machine, do a ping test to the SP server:
Code:
ping -n 200 -l 65500 {SP_ip_address}
- n 200 means it will do 200 pings
-l 65500 means it will use the maximum buffer size of 65500 bytes

If some of the requests time out, it means it took more than 4 seconds for the round trip. It should come back in the tens of milliseconds on a local network.
 

Advertise at ADSM.ORG

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

DigitalOcean $100 Credit

Support ADSM.ORG and get DigitalOcean FREE credit. DigitalOcean currently offer a $100, 60-day Free Credit for new accounts. Sign-up here:

DigitalOcean Referral Badge

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: 22 19.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 58.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.5%
  • Other (please comement)

    Votes: 9 8.1%

Forum statistics

Threads
31,816
Messages
134,838
Members
21,786
Latest member
marwo
Top