John,
 
The export of just 15 nodes was tested earlier on. It contained the larger 
nodes already. At that time, the TSM server just was slowly (high CPU 
consumption and a lot of disk I/O which is normal of course). It worked fine.
 
The export of all of the nodes at the same time causes an immediate crash of 
the TSM server. I did not mean to do the export at once but did not notice that 
the parallel/serial commands would not work as the exports are started in the 
background.
 
 
So I changed the script to work in groups of 15 nodes. The export of the nodes 
in groups of 15 caused a new crash when the last group export was started. A 
few of the earlier exports were still running at that time, the nodes in the 
latest group export were rather small nodes.
 
A support call was logged of course.  The question is what causes the TSM 
server crash. Except the PK_EXCEPTION and PK_THREAD messages in the application 
log, nothing else is found.
 
Just have to wait for some new from the labs at this time. And will contact 
them tomorrow again.
 
regards,
Kurt

________________________________

Van: ADSM: Dist Stor Manager namens John Monahan
Verzonden: ma 2/27/2006 20:15
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: [ADSM-L] export nodes causes TSM server crash



Let me see if I understand you correctly.  The export works fine when only
15 nodes are running, but after 2 hours when the second set of 15 nodes
kicks in (while some from the first group of 15 are stilli running)  that
is when your server crashes?  Or does your server crash with only 15 nodes
running an export?


______________________________
John Monahan
Consultant Infrastructure Solutions Group
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com




Kurt Beyers <Kurt.Beyers AT DOLMEN DOT BE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/27/2006 05:35 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
export nodes causes TSM server crash






Hello everybody,

I've got a TSM server 5.3.2.2 running on Windows2003 Enterprise Edition
SP1 (7 GB RAM, Xeon 3,2 GHz CPU) that has about 100 TSM clients defined.

Each month an export of each TSM node with the active backup data will be
taken to disk (DS4100 with SATA disks of 250 GB). The disk storage pool
that contains the backups is on the DS4100 too.

I've scheduled the export of the TSM nodes past weekend with a few
scripts.

I first tried to launch just one script that took the export in blocks of
15 nodes using the PARALLEL and SERIAL commands. However as the export is
started in the background, all of the 75 exporst were started immediately.
This causes a TSM server crash. After restarting the TSM server, no error
logs are found in the activity log. Except that no more than 16 commands
can be started in one PARALLEL statement. The last normal message about
the export is written in the log and then the next message are when the
server is started again.

I've split up then the export myself in a script where the export of 15
nodes was started and 4 administrative schedules were defined that
triggered the export of 15 additional nodes every 2 hours later on. The
TSM server crashed once more.

Is this a know feature when the export of a lot of nodes is started? Am I
overseeing some parameters here? Can the export be started in a better way
using TSM scripting?

An export server instead of an 'export node' for each TSM node is not an
option as then the impot of one node would take too much time.

thanks in advance,

Kurt