1.  The backup stg command is incremental so it will only add files that
haven't been copied to that copy pool yet.
2. There are no drm listings, unless you create them yourself via the q drm
command and send the output to a printer.
3.  I have a script that does my "disaster backups".  It issues a backup stg
for each storage pool, then issues the backup db command, then issues the
"mov drm * wherest=mo" (this changes their status to not-mountable), then
issues a "q drm * wherest=notmo" and writes that to a file that gets printed
(the tape pull list), then issues "mov drm * wherest=notmo tost=vault", then
issues "prepare plan" and both prints the recovery plan and writes it to a
diskette.

> -----Original Message-----
> From: Amerman, Anthony S. [SMTP:ASAmerman AT LEGGMASON DOT COM]
> Sent: Thursday, August 06, 1998 3:11 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Backup Storage pool question.
>
> Hi ADSM'ers
> I'm kinda confused about the DRM q drmedia and the move drmedia
> functions, and maybe you can help me.
> I'm currently doing a backup stg <primary> <copy>, but because of the
> size it never quite gets done
> so I guess I have a few questions:
> 1. Does the backup stgpool command pick up where it left off last or
> does it try and do a full backup everytime I restart? (This is the
> correct command to use right?)
> 2. Do the DRMedia listings get automatically updated to what needs to go
> offsite or do I have to do queries like
> "q vol access=readwrite stgpool=copypool status=full" to determine which
> ones go off to the vault?
> 3. Is there a solid way to do this that can be automated?
>
> I'm using V2 (yes I'm actually going to upgrade in the next week) but I
> have to get this sorted out in the meantime.
>
> Thank in Advance.
>
> Shane Amerman
>
> Anthony Shane Amerman
> Legg Mason, Corporate Technology
> UNIX Systems Engineer
> 410-454-3081 25th Floor