Maarten,
I know that. I was just saying the message about how many objects were
deleted only displays database backups deleted that were done via
server-to-server. In my case, I just do database backups to tape within my
server. Therefore, the message ANR0812I always shows 0 database backups
deleted -- because none of them was done via server-to-server operations.
My database backups get deleted based on the drmdbbackupexpiredays setting,
but this is not part of the count in the ANR0812I message. I believe the
explanation of the ANR0812I message answered the question asked.
Tina
> -----Original Message-----
> From: Maarten Doeswijk [SMTP:Maarten.Doeswijk AT MAIL.ING DOT NL]
> Sent: Monday, March 08, 1999 9:33 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Betr: Re: Betr: Expiration of DBBackup volumes
>
> Tina,
>
> The DRM module of ADSM uses the same technic of keeping track on de
> database backups using the volume history. Delete a database backup
> from the volume history and the used volume(s) are also removed from
> the QUERY DRMMEDIA list.
>
> Not only server-to-server (virtual volumes) are noted in the volume
> history, but all sequential media used bij ADSM.
>
> The DRM module, I think, uses the value set by the
> DRMDBBACKUPEXPIREDAYS parameter and passes the following command to
> ADSM:
>
> del volh t=dbb todate=today-(DRMDBBACKUPEXPIREDAYS).
>
> In one case the DRM module failed to remove the old database
> backup's.
> I got them out of the system by using the delete volume command.
>
>
> Regards,
> Maarten Doeswijk
>
>
> ____________________________ Antwoord-separator
> ________________________________
> Onderwerp: Re: Betr: Expiration of DBBackup volumes
> Auteur: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> in inet-1
> Datum: 8-3-99 7:40
>
>
> Martijn,
>
> I was confused by this at first too. If you look more closely at the help
> for the message, you'll see that it refers to volumes created using the
> server-to-server functions. Here's the help. The last sentence is the
> important one.
>
> Explanation: Server roll-off processing has completed. The number of
> client
> objects examined and deleted, based on management class policy, are
> displayed
> in the message. A total error count is also displayed. The number of DB
> backup
> volumes deleted is based on the value specified on the SET
> DRMDBBACKUPEXPIREDAYS. The number of recovery plan files deleted is based
> on
> the value specified on the SET DRMRPFEXPIREDAYS. Server roll-off
> processing
> deletes the DB backup volumes and recovery plan files only if DRM is
> licensed
> on the server and the volumes or plan files are created on the server to
> server
> virtual volumes.
>
>
> Tina
>
> > -----Original Message-----
> > From: Maarten Doeswijk [SMTP:Maarten.Doeswijk AT MAIL.ING DOT NL]
> > Sent: Monday, March 08, 1999 1:48 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Betr: Expiration of DBBackup volumes
> >
> > If you're using DRM, set the folowing DRM parameter:
> >
> > Syntax
> >
> > >>-Set DRMDBBackupexpiredays--numberofdaysbeforeexpiration-----><
> >
> > The number you fill in will also appear in the reuse delay
> parameter
> > of the copy storage pools that were marked as DRM pools.
> >
> >
> >
> > If you're not using DRM, the database volumes are being registered
> in
> > the volume history. To clear up database backups, use the delete
> > volhistory command:
> >
> > Syntax
> >
> > >>-DELete VOLHistory----TODate--=--date----+------------------+->
> > '-TOTime--=--time--'
> >
> > >-----Type--=--+-All-------+-----------------------------------><
> > +-DBBackup--+
> > +-DBDump----+
> > +-DBRpf-----+
> > +-EXPort----+
> > +-RPFile----+
> > +-STGNew----+
> > +-STGReuse--+
> > '-STGDelete-'
> >
> > To delete database volumes which are older than 5 days use the
> > following command:
> >
> > del volh tod=today-5 tot=00:00 t=dbb
> >
> > ADSM will ask if you sure and if you'll awnser yes than they are
> > gone.
> >
> > But be cautious using this command because the freed
> cartridges/tape
> > are marked as scratch (if they ever were) and can be overwritten.
> >
> >
> > Happy hunting,
> > Maarten Doeswijk
> >
> >
> > ____________________________ Antwoord-separator
> > ________________________________
> > Onderwerp: Expiration of DBBackup volumes
> > Auteur: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> in inet-1
> > Datum: 5-3-99 15:25
> >
> >
> > Hi,
> >
> > * We run ADSM 3.1.1.5 with the DRM feature enabled
> > * DRMDBBACKUPEXPIREDAYS is set to 7 (as is the REUSEDELAY for our
> > copypool)
> > * We make 2 full database backups each day
> > * We run EXPIRE INVENTORY every two days
> > * This is what the activity log says on expiration results:
> >
> > 02/23/1999 16:08:56 ANR0812I Inventory file expiration process
> 278
> > completed: examined 257751 objects, deleting 235150 backup objects,
> 21610
> > archive objects, and 0 DB backup volumes. 0 errors were encountered.
> > 02/25/1999 16:33:42 ANR0812I Inventory file expiration process
> 37
> > completed: examined 111878 objects, deleting 107877 backup objects, 2992
> > archive objects, and 0 DB backup volumes. 0 errors were encountered.
> > 02/27/1999 16:44:42 ANR0812I Inventory file expiration process
> 49
> > completed: examined 255067 objects, deleting 232308 backup objects,
> 21743
> > archive objects, and 0 DB backup volumes. 0 errors were encountered.
> > 03/01/1999 14:28:48 ANR0812I Inventory file expiration process
> 95
> > completed: examined 123685 objects, deleting 101128 backup objects,
> 21547
> > archive objects, and 0 DB backup volumes. 0 errors were encountered.
> > 03/04/1999 17:58:16 ANR0812I Inventory file expiration process
> 29
> > completed: examined 359107 objects, deleting 328765 backup objects,
> 29349
> > archive objects, and 0 DB backup volumes. 0 errors were encountered.
> >
> > What interests me is, that it always says "and 0 DB backup volumes". Do
> we
> > ever get any of our database volumes back from Offsite? My guts tell me
> it
> > should expire 4 DBBackup volumes every 2 days. Am I doing something
> wrong
> > /
> > missing something?
> >
> > Thanks for any comments!
> > Martijn.
|
