ADSM-L

Re: [ADSM-L] Ang: Re: Linux backup won't run

2010-11-10 11:16:58
Subject: Re: [ADSM-L] Ang: Re: Linux backup won't run
From: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 10 Nov 2010 11:13:37 -0500
Thanks David reply,

yes, I can ping the client from the TSM server, The stanza for the TCPServeraddress dsm.sys is a hostname ie >>> company.ncc.oa.cc and the TcpClientAddress is a IP address (numeric)

yes I have tried using IP addresses instead of DNS hostnames didn't change results. Haven't tried the traceroute from client to server and vice versa.

We think??? We may have found the problem (we will see if tonights backup will work)

Even though SELINUX was  disabled,  iptables were being loaded.

Again, There was a another Linux server set up for backup at the same time with exactly same type of dsm.opt, dsm.sys and client level and there is no problem with that

Thanks again

On 11/9/2010 3:37 PM, Daniel Sparrman wrote:
Sorry for my intrusion in the discussion ;)

I'm trying to figure out why the TSM server would be located on the outside of the 
firewall while the client is on the inside? Usually, the server is located on the 
inside, and can therefore contact the client, while the client is located on the 
outside (or in a DMZ) and cant contact the server due to ports not being open from 
untrust/dmz>  trust.

I might be entirely wrong here, but this looks more like a DNS issue. Can you 
ping the client from the TSM server? You can obviously not do a DNS lookup of 
the TSM server from the client.

The stanza for TCPServeraddress in your opt-file, is that an IP adress or a 
hostname? (it just says XXXX.XXX.XXX.XXX as far as I can see below). And what 
about TcpClientAddress?

Have you tried using IP adresses instead of DNS hostnames? And if so, have you 
tried doing a traceroute from client to server and vice versa?

If i'm not entirely mistaken, a scheduled backup (when using prompt) is still 
initiated (from a TCP perspective) from the client. That means a) Server 
contacts client to start backup b) Client initiates backup. If the client cant 
resolve the server, you will get missed, or if the server cant resolve the 
client, you'd get the error below.

Best Regards

Daniel Sparrman

-----"ADSM: Dist Stor Manager"<ADSM-L AT VM.MARIST DOT EDU>  skrev: -----


Till: ADSM-L AT VM.MARIST DOT EDU
Från: David E Ehresman<deehre01 AT LOUISVILLE DOT EDU>
Sänt av: "ADSM: Dist Stor Manager"<ADSM-L AT VM.MARIST DOT EDU>
Datum: 11/09/2010 21:48
Ärende: Re: Linux backup won't run

We use port 1502.  You just need to pick one that is not being used by
other applications.

Timothy Hughes<Timothy.Hughes AT OIT.STATE.NJ DOT US>  11/9/2010 3:39 PM

David, ok

I looked at the WEBports option is there a special way to figure out
what ports to use?

Thanks
Tim

On 11/9/2010 3:25 PM, David E Ehresman wrote:
Right.  That means the client can contact the tsm server.  It does
not
mean that the tsm server can contact the client on the appropriate
port.

Timothy Hughes<Timothy.Hughes AT OIT.STATE.NJ DOT US>   11/9/2010 3:09 PM

David Thanks for your response,

I was told though there is no firewall however, I will look at the
Webports option to try.

btw- I forget to mention we can do manual backups


Tim

On 11/9/2010 2:44 PM, David E Ehresman wrote:
TSM is trying to contact the server on port 4325

11/08/10 00:02:13 ANR2716E Schedule prompter was not able to
contact
client
svbser1 using type 1 (xx.xx.xx 4325. (SESSION: 2865)

I've seen this when a firewall was active between TSM and the
client.
It that case you need to use a WEBPorts option in the client so
there
is
a fixed port being used and then open that port in the firewall.

Timothy Hughes<Timothy.Hughes AT OIT.STATE.NJ DOT US>    11/9/2010 2:27
PM
Hi All,

We have a linux client (5.5.2.7) that was currently backing up that
has
stopped for some reason, when I start the cad it looks like its
ready
to
backup however it misses its backup each night. Has anyone else had
similar issues with a linux backup

[root@svbser1]# tail dsmsched.log

11/09/2010 11:13:18 Next operation scheduled:
11/09/2010 11:13:18
------------------------------------------------------------
11/09/2010 11:13:18 Schedule Name: MIDNIGHT
11/09/2010 11:13:18 Action: Incremental
11/09/2010 11:13:18 Objects:
11/09/2010 11:13:18 Options:
11/09/2010 11:13:18 Server Window Start: 00:00:01 on 11/10/2010
11/09/2010 11:13:18
------------------------------------------------------------
11/09/2010 11:13:18 Scheduler has been stopped.

nothing in the dsmerror.log that would show the cause


[root@svbser1]# tail dsmerror.log
11/05/2010 09:47:24 ANS1141W Unknown command - ls
11/05/2010 14:57:50 ANS1141W Unknown command - exit
11/05/2010 14:57:52 ANS1141W Unknown command - \quit
11/05/2010 14:57:53 ANS1141W Unknown command - exit


Nothing in the dsmsched.log it just shows it ready for the next
backup
but it never backs up

tail -100 dsmsched.log

11/04/2010 09:05:14 --- SCHEDULEREC QUERY BEGIN
11/04/2010 09:05:14 --- SCHEDULEREC QUERY END
11/04/2010 09:05:14 Next operation scheduled:
11/04/2010 09:05:14
------------------------------------------------------------
11/04/2010 09:05:14 Schedule Name: MIDNIGHT
11/04/2010 09:05:14 Action: Incremental
11/04/2010 09:05:14 Objects:
11/04/2010 09:05:14 Options:
11/04/2010 09:05:14 Server Window Start: 00:00:01 on 11/05/2010
11/04/2010 09:05:14
------------------------------------------------------------
11/04/2010 09:05:14 Scheduler has been stopped.


11/05/2010 13:54:12 Server Version 6, Release 1, Level 4.2
11/05/2010 13:54:12 Server date/time: 11/05/2010 13:54:12 Last
access:
11/05/2010 13:53:12

11/05/2010 13:54:12 --- SCHEDULEREC QUERY BEGIN
11/05/2010 13:54:12 --- SCHEDULEREC QUERY END
11/05/2010 13:54:12 Next operation scheduled:
11/05/2010 13:54:12
------------------------------------------------------------
11/05/2010 13:54:12 Schedule Name: MIDNIGHT
11/05/2010 13:54:12 Action: Incremental
11/05/2010 13:54:12 Objects:
11/05/2010 13:54:12 Options:
11/05/2010 13:54:12 Server Window Start: 00:00:01 on 11/06/2010
11/05/2010 13:54:12
------------------------------------------------------------
11/05/2010 13:54:12 Scheduler has been stopped.


11/06/2010 20:52:27 Server Version 6, Release 1, Level 4.2
11/06/2010 20:52:27 Server date/time: 11/06/2010 20:52:27 Last
access:
11/06/2010 20:51:26

11/06/2010 20:52:27 --- SCHEDULEREC QUERY BEGIN
11/06/2010 20:52:27 --- SCHEDULEREC QUERY END
11/06/2010 20:52:27 Next operation scheduled:
11/06/2010 20:52:27
------------------------------------------------------------
11/06/2010 20:52:27 Schedule Name: MIDNIGHT
11/06/2010 20:52:27 Action: Incremental
11/06/2010 20:52:27 Objects:
11/06/2010 20:52:27 Options:
11/06/2010 20:52:27 Server Window Start: 00:00:01 on 11/07/2010
11/06/2010 20:52:27
------------------------------------------------------------
11/06/2010 20:52:27 Scheduler has been stopped.


11/07/2010 08:51:21 Server Version 6, Release 1, Level 4.2
11/07/2010 08:51:21 Server date/time: 11/07/2010 08:51:21 Last
access:
11/07/2010 08:50:20

11/07/2010 08:51:21 --- SCHEDULEREC QUERY BEGIN
11/07/2010 08:51:21 --- SCHEDULEREC QUERY END
11/07/2010 08:51:21 Next operation scheduled:
11/07/2010 08:51:21
------------------------------------------------------------
11/07/2010 08:51:21 Schedule Name: MIDNIGHT
11/07/2010 08:51:21 Action: Incremental
11/07/2010 08:51:21 Objects:
11/07/2010 08:51:21 Options:
11/07/2010 08:51:21 Server Window Start: 00:00:01 on 11/08/2010
11/07/2010 08:51:21
------------------------------------------------------------
11/07/2010 08:51:21 Scheduler has been stopped.

1
11/09/2010 11:13:18 Server Version 6, Release 1, Level 4.2
11/09/2010 11:13:18 Server date/time: 11/09/2010 11:13:17 Last
access:
11/09/2010 11:12:17

11/09/2010 11:13:18 --- SCHEDULEREC QUERY BEGIN
11/09/2010 11:13:18 --- SCHEDULEREC QUERY END
11/09/2010 11:13:18 Next operation scheduled:
11/09/2010 11:13:18
------------------------------------------------------------
11/09/2010 11:13:18 Schedule Name: MIDNIGHT
11/09/2010 11:13:18 Action: Incremental
11/09/2010 11:13:18 Objects:
11/09/2010 11:13:18 Options:
11/09/2010 11:13:18 Server Window Start: 00:00:01 on 11/10/2010
11/09/2010 11:13:18
------------------------------------------------------------
11/09/2010 11:13:18 Scheduler has been stopped.


TSM server log shows

11/08/10 00:02:13 ANR2716E Schedule prompter was not able to
contact
client
svbser1 using type 1 (xx.xx.xx 4325. (SESSION: 2865)


dsm.opt file

SErvername xxxx
COMMmethod TCPip
TCPPort 1500
TCPServeraddress xxxx.xxx.xxxx.xx.xx
Nodename xxxxxx
Passwordaccess generate
TCPclientaddress xx.xx.xx.xx
Httpport 1581
*Exclude.backup /.../core
Exclude.backup /tmp/.../*
*Exclude.dir /.netscape/cache
Include /.../dsmwebcl.log special
Include /.../dsmsched.log special
tcpw 64
tcpb 32
Resourceutilization 4
ERRORLOGname /opt/tivoli/tsm/client/ba/bin/dsmerror.log
SCHEDLOGName /opt/tivoli/tsm/client/ba/bin/dsmsched.log
Errorlogretention 14
Schedlogretention 7
Schedmode prompted
LARGECOMmbuffers YES
MANAGEDSERVICES WEBCLIENT SCHEDULE

I did find out one thing I am unable to ping our TSM Server from
the
client

root@svbser1 bin]# ping tsmserver.xxx.xxx.xx
ping: unknown host tsmserver.xxx.xxx.xx
[root@svbser1 bin]# ping tsmserver.xxx.xxx.xx
ping: unknown host tsmserver.xxx.xxx.xx
[root@svbser1 bin]# ping tsmserver.xxx.xxx.xx
ping: unknown host tsmserver.xxxx.xxx.xx
[root@svbser1]#


F.Y.I - there is no firewall and selinux is disabled

However, I can ping our TSM from the other linux server using the
same
client and os it's backing of successfully.

[root@svbser2]# ping tsmserver.xxx.xxx.xx
PING tsmserver.xxx.xxx.xx (22.22.22.22) 56(84) bytes of data.
64 bytes from tsmserver.xxx.xxx.xx (22.22.22.22): icmp_seq=1
ttl=252
time=0.336 ms
64 bytes from tsmserver.xxx.xxx.xx (22.22.22.22): icmp_seq=2
ttl=252
time=0.352 ms
64 bytes from tsmserver.xxx.xxx.xx (22.22.22.22): icmp_seq=3
ttl=252
time=0.273 ms
64 bytes from tsmserver.xxx.xxx.xx (22.22.22.22): icmp_seq=4
ttl=252
time=0.312 ms



Thanks for any help, comments in advance!