Talk to the person who manages the firewall.

It is common for firewall software to have its own "idletimeout" value.
If a session goes quiet for a time, the firewall terminates the session.

And it is not uncommon for TSM backups to exceed the firewall timeout
value - can happen easily if TSM spends a long time searching
directories before sending data, or if waiting on a response from
Oracle, etc..  

In my experience, it results in the errors you saw - the firewall closes
the session, TSM reopens it - the backup eventually completes OK, but
takes forever.

Ask them to check the firewall, turn off their timeout (or change it to
something very very large), and test running a backup.  If that clears
up your problem, then you can play around with the timeout value until
you find something that will work most of the time.

Good luck!
Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)




-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Geert De Pecker
Sent: Tuesday, October 26, 2004 3:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Client connection severed


I keep getting the "session is lost" errors with a certain box.

I already changed the maxsessions, maxschedule, idletimeout, but no
changes. The errors keep coming.

Only specials about this box is the fact that it has large files (oracle
database) and that it is behind a firewall. I assume
the big files (2 and 4 gb) are making the problem here.

Any hints where I can look next?

Thanks,

Geert

Server side:

10/26/04   03:15:01      ANR0480W Session 4563 for node AILDB (WinNT)
terminated -
                          connection with client severed.
10/26/04   03:26:22      ANR0480W Session 4566 for node AILDB (WinNT)
terminated -
                          connection with client severed.
10/26/04   03:45:54      ANR0480W Session 4567 for node AILDB (WinNT)
terminated -
                          connection with client severed.
10/26/04   04:15:49      ANR0480W Session 4568 for node AILDB (WinNT)
terminated -
                          connection with client severed.

Client side dsmerror.log

26-10-2004 03:17:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:17:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:17:23 ANS1810E TSM session has been reestablished.
26-10-2004 03:41:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:41:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:41:23 ANS1810E TSM session has been reestablished.
26-10-2004 04:11:03 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 04:11:03 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 04:11:18 ANS1810E TSM session has been reestablished.
26-10-2004 04:43:58 ANS1809W Session is lost; initializing session
reopen
procedure.

Client side dsmsched.log

26-10-2004 03:07:58 --- SCHEDULEREC OBJECT BEGIN BACKUP_INC_AIL
26-10-2004
03:00:00
26-10-2004 03:17:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:17:23 ... successful
26-10-2004 03:41:08 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 03:41:23 ... successful
26-10-2004 04:11:03 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 04:11:18 ... successful
26-10-2004 04:43:58 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 04:44:13 ... successful
26-10-2004 05:11:36 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 05:11:51 ... successful
26-10-2004 05:17:11 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 05:17:26 ... successful
26-10-2004 05:32:41 ANS1809W Session is lost; initializing session
reopen
procedure.
26-10-2004 05:32:56 ... successful
26-10-2004 05:35:47 --- SCHEDULEREC STATUS BEGIN
26-10-2004 05:35:47 Total number of objects inspected:   78,805