I realize I am a day late and a dollar short on this one but thought I would
put in my 2 cents anyway. What I experience with my systems is this. When I
update the primary pool to reclaim=100 once it completes the current
procedure the process ends. But if it is a copy pool reclamation that is
running it the process will continue to run until it reclaims all of the
tapes it "grabbed" when the reclamation was set to something lower than 100.
Therefore the process has to be canceled to end it any earlier. I realize
this is the same answer you have already received, just a different
explanation as to why.
Have a great day,
James Brents
> -----Original Message-----
> From: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>@PEUSA
> On
> Behalf Of Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM>
> Sent: Monday, August 05, 2002 2:35 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Space reclamation of copypool
>
> Thanks,
> I see what you're getting at (M. Sanchez), but I was hoping to avoid
> shellscripting for two reasons; I'm running onm Win2K, where "shell"
> scripting is hardly as good as in any Unix variant. Secondly, I was hoping
> there was a way through a TSM (internal) script, to get hold of the
> processnumber. I know I can get the processnumber by a query, but I don't
> know how to make it a variable.
>
> Luckily for me, the problem is partly solved because the only process
> running at a certain time is Space Reclamation, and this allows me to do a
> "can proc all", at that time, and space reclamation stops.
>
> Thanks all of you for good input.
>
> Rgds.
> Geirr G. Halvorsen
>
>
> -----Original Message-----
> From: Manuel Sanchez [mailto:manuel_j_sanchez AT YAHOO DOT COM]
> Sent: 2. august 2002 23:44
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Space reclamation of copypool
>
>
> Besides making rec=100, you have to cancel the
> process.
> Here is an example using a shell script:
>
> dsmadmc -id=your _id -pa=your_pa q pr | grep -i
> "space reclamation" > $tmpdir/process9
> if test -s $tmpdir/process
> then exec 5<$tmpdir/process
> read -r -u5 line
> proc=${line%%Space*}
> comma=`echo $proc | grep "," | wc -l`
> if [ $comma -eq 0 ] ; then
> process=$proc
> else
> process=${proc%%,*}${proc##*,}
> fi
> print $(date) "Cancelling TSM process $process
> on $server ..." >> $maste
> rdir/master.log
> dsmadmc -id=your _id -pa=your_pa cancel pr
> $process>>$tmpdir/end_space_reclaim.log
> else print $(date) "No space reclamation processes
> found on $server." >> $mas
> terdir/master.log
> continue
> fi
>
>
>
> --- Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM> wrote:
> > Hello everyone,
> > I have the following problem with Space Reclamation
> > of my copypool.
> > To start reclamation I have a script running UPDATE
> > STG COPYPOOL RECLAIM=50
> > Three hours later, I run another script to stop
> > reclamation - UPDATE STG
> > COPYPOOL RECLAIM=100
> > but reclamation never stops. This affects all of my
> > daily operations
> > (migration, backup stgp..) because the
> > reclamation process uses both drives.
> > Question is, why does space reclamation not stop
> > after updating?
> > Is there a way of canceling the process (by TSM
> > script)?
> >
> > Best regards
> > Geirr G. Halvorsen
>
>
> =====
> <P>Thanks,</P>
> <P>Manuel J Sanchez</P>
> <P>Senior UNIX SA</P>
> <P>Assurant Group</P>
> <P>(305) 252-7035 x32153</P>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
|
