We set our admin schedules for the desired window of activity;  eg, set
migration values low to activate the disk-to-tape migration process at 8am,
then set them high at noon, to deactivate.

You can (effectively) "query process" (via admin select cmd), to determine
what processes are running, from your server script... for example,

upd script offsite_backups ' select * from processes where -'
upd script offsite_backups " upper(process)='SPACE RECLAMATION'"
upd script offsite_backups ' if (rc_ok) goto reschedule'
        .
        .
        .
upd script offsite_backups ' reschedule:'
upd script offsite_backups ' del sch retry_offsite_backups type=a'
upd script offsite_backups ' def sch retry_offsite_backups t=a cmd="run
offsite_backups -'
upd script offsite_backups ' " active=yes startt=NOW+0:20 peru=o'



Don France

Technical Architect, P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037




> -----Original Message-----
> From: Sam Sheppard [mailto:SHS AT SDDPC.SANNET DOT GOV]
> Sent: Tuesday, January 04, 2000 10:05 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Disk Storage Migration
>
>
> ---------------------------- Top of message
> ----------------------------
> >>--> 01-04-00  10:00  S.SHEPPARD     (SHS)    Disk Storage
> Migration Is
>
> My experience has been that that's the way it always worked.  However,
> migration works on either a filespace or nodename at a time, I can't
> remember which.  So, if you have one filespace taking up 80% of your
> pool, you would see it migrated down to 20% no matter what the
> low threshold was set to.
>
> Sam Sheppard
> San Diego Data Processing Corp.
> --------------------------------------------------------------
> ---------`
>
>
> ---------------------------- Top of message
> ----------------------------
> >>--> 01-04-00  09:48  ..NETMAIL     (001)     Disk Storage
> Migration Is
> Date: Tue, 4 Jan 2000 12:36:31 -0500
> From: "Scott Fluegge" <sfluegge AT VENATORGROUP DOT COM>
> Subject: Disk Storage Migration Issue
> To: ADSM-L AT VM.MARIST DOT EDU
> _________________________________Top_of_Message_______________
> __________________
>
> Hello all...
>
> I have just discovered that Migration no longer worked the
> way it used to.  Once
> upon a time I was able to set the storage pools high and low
> values to 0,
> migration would start, then after maybe 20 seconds I would
> reset the values to
> 90 and 70.  Migration would continue to run until it reached
> the pre-set value
> of 0, not 70.  Now when I run it, if I reset the values
> before it finishes, the
> process assumes the new values and will end prematurely!
>
> Have others found this to be true?  Is this by design or
> accident?  And lastly,
> how do I automate the migration process if I need to watch it
> complete before I
> can update the values?
>
> Thanks for you input...
>
> Scott
>
> --------------------------------------------------------------
> ---------`
>