"Computer is currently not reachable" errors for OES2 server

Here you can write your Problems with Backups.

Moderator: sepma

Post Reply
ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

"Computer is currently not reachable" errors for OES2 server

Post by ian » June 25th, 2013, 4:09 am

Since upgrading from 3.6 to 4.2.1.41, I've been getting "Computer is currently not reachable" errors for random targets on our OES2 server and/or netware servers that use the OES2 server as the data mover. This didn't happen with SESAM 3.6, so it seems to be an issue with 4.2.

The error occur for different targets randomly each day, but only targets that are on or accessed via that OES2 server. That server is a virtual server - interestingly, other VMs on the same host don't seem to have any issues being backed up.

The error messages in the log show the following:
c hamfp01v_OUT 23:53-01:34 F 3 RemovableDskPool UNIX computer hamfp01v.hamcoll.sa.edu.au is currently not reachable. (E020-HOSTS Computer hamfp01v.hamcoll.sa.edu.au is currently not reachable: Error: RCMD hamfp01v.hamcoll.sa.edu.au: Error during sbc -h)
c hamilton_CONT_USERS 23:53-09:12 F 3 RemovableDskPool NETWARE computer hamilton is currently not reachable. (E020-HOSTS Computer hamfp01v.hamcoll.sa.edu.au is currently not reachable: Error: RCMD hamfp01v.hamcoll.sa.edu.au: Error during sbc -h)

If I restart the backup job, it will complete successfully, so I assume that when SESAM tries to contact the server (with a ping?), the server is too busy with other concurrent backup streams to respond in time and so SESAM decides that the server is unreachable and stops that job without actually starting to backup any data.

The server is using version 4.2.1.4 on SLES 11SP2 and the OES2 SP2 client is using sesam-novell-client-4.2.1-40.SuSE.

Can you suggest any fix for this issue - or if not, a workaround such as making SESAM re-try the initial connection if it doesn't get a response the first time, increasing the time it waits for a response or limiting the number of concurrent backups through that host (hamfp01v) so it it can respond faster?

Cheers,
Ian

cliogp
Posts: 37
Joined: January 18th, 2006, 6:51 pm
Location: Waakirchen
Contact:

Re: "Computer is currently not reachable" errors for OES2 se

Post by cliogp » June 26th, 2013, 8:37 am

Hi Ian,

when a sesam backup starts, the process try to connect to the client or the datamover on port 11301 (control port). This is hard coded, a kind of "keep alive".
The solution for your issue is, use a datamover with more resources or use more then one datamover server.

Clio

Post Reply