Henrik,
 
Too many servers over LAN/WAN are in the picture to take a monthly archive in 
just a weekend.
 
And because there are also many TDP backups, the export was chosen instead of 
the backupset (only possible for a TSM BA client). The export could be taken 
relative to a certain data too.
 
A PMR has been opened at TSM support too of course.
 
regards,
Kurt

________________________________

From: ADSM: Dist Stor Manager on behalf of Henrik Wahlstedt
Sent: Mon 2/27/2006 13:57
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] export nodes causes TSM server crash



Hi,

You confuse me, what are you trying to achieve?

Monthly exports could easily be replaced with archives or backup sets.


//Henrik

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kurt Beyers
Sent: den 27 februari 2006 12:35
To: ADSM-L AT VM.MARIST DOT EDU
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


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.