Mark

In principle I agree.  In fact I almost always agree with your advice, Mark.
 However, I have seen times (and I'm sure you have as well) where a move
data or reclamation is using two drives and it seems to be hung.  When you
do a q proc you are reminded that the process has been issued a cancel
command, but the darn thing just won't go away and I need the drives.
Sorry, but this is one of those things that just cries out to be fixed.
Surely they can come up with a way of killing the process and keeping the
integrity.  When I eventually give up and turn the server off, it always
seems to recover ok and audit volumes of the volumes in use don't seem to
have any problems.

Just another pet peeve.

JT

From: "Stapleton, Mark" <stapleto AT BERBEE DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: BACKUP STGPOOL
Date: Sun, 9 Mar 2003 14:00:16 -0600

From: James Taylor [mailto:jimtsm AT HOTMAIL DOT COM]
> Is there still no way to enter a command in that will cancel
> a process immediately.  For years we have had to put up with
> this problem.

It's called rollback, James. In order for TSM to maintain integrity
between the state of the backup system and the database, TSM has to
reach a point in a process that it can rollback from before that process
can be safely cancelled. If you stop a process *immediately*, before the
process can reach a safe checkpoint, you're gonna be in for loads of
trouble down the line.

--
Mark Stapleton (mark.stapleton AT berbee DOT com)

_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?page=features/virus