ADSM-L

Re: Questions...

1999-02-01 09:57:57
Subject: Re: Questions...
From: Andy Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 1 Feb 1999 06:57:57 -0800
With regard to using the EXCLUDE statement, this will still
cause the data to be retained per the copygroup attributes.
But I suspect that Don wants to get rid of these copies
immediately (or maybe not, but I thought I would bring this
up, anyway).

There is no command for handling this situation, but a fairly
simple technique can be applied.

***********
* WARNING *
***********
PLEASE BE CAREFUL USING THIS TECHIQUE, AS IT *WILL* CAUSE DATA
TO BE IRREVOCABLY DELETED. I do not recommend this for everyday
use, but only in cases where you have large amounts of storage
being wasted.

Create a management class with a backup copygroup that has
attributes VERDELETED=0, RETEXTRA=0, RETONLY=0. For example:

   DEF MG STANDARD STANDARD DELETE

   DEF CO STANDARD STANDARD DELETE VERD=0 RETE=0 RETO=0
          FREQ=9999 DEST=BACKUPPOOL

   ACT PO STANDARD STANDARD

Then code an INCLUDE statement in your DSM.OPT file that binds
the Lotus Notes files to this new management class:

   INCLUDE E:\NOTES\DATA\...\*.NSF DELETE

(You can code these as needed, depending on where they are
located. Alternatively you can say,
"INCLUDE *:\...\*.NSF DELETE" to cover all *.NSF files
anywhere on any disk. But just in case someone happens to
name non-Notes files with *.NSF, you might want to use the
specific Notes directory name.)

The next time an incremental backup runs, all existing backup
versions of the *.NSF files will be rebound to the DELETE
management class. I included FREQ=9999 in the copygroup
definition to avoid backing up any Notes files that might have
changed since the last time they were incrementally backed up.
Note that if no active version of a *.NSF file currently
exists, a backup will be made anyway.

Once the incremental backup runs and the *.NSF files are
rebound, change the INCLUDE statement(s) you coded above
to EXCLUDE, and remove the management class name at the end
of the statement. Thus the INCLUDE example I gave above now
becomes:

   EXCLUDE E:\NOTES\DATA\...\*.NSF

Now run another incremental backup. The active versions of the
*.NSF files will be made inactive. The next time inventory
expiration runs, any backup versions of the *.NSF files should
be deleted from ADSM storage.

Once you have done this, I recommend deleting the management
class in order to prevent accidental use:

   DEL MG STANDARD STANDARD DELETE

   ACT PO STANDARD STANDARD

Hope this helps,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

When you create the exclude statement in the options file, the excluded
files will be deleted, so you don't need to do anything special to get rid
of the data.  It will be gone the next time an incremental backup is run.

Your second question.  I would create a disk storage pool and make the
existing tape pool the next storage pool for this disk pool.  Then set up a
schedule to migrate data from the disk pool to the tape pool once per day.
 I'm assuming you want to have your data safely on tape as well as on disk.
 By doing this, you will always have the most recent data in the disk
storage pool and the previous day's backups will be on tape.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
www.storsol.com
lipp AT storsol DOT com
(719)531-5926

<Prev in Thread] Current Thread [Next in Thread>