Tom,

We have done that as well but it requires coordination between myself and the
platform administrator.  They don't always take the time required for the extra
steps to get the ADSM backups marked inactive.


In the previous Memo, dated, 06-18-97 01:24:02 PM, tpittson @ HIMAIL.HCC.COM
("Pittson, Timothy ,HiServ/NA") @ MGICSMTP wrote:

Mary,
        What I've done in past, when a server or filespace has been eliminated
or 'retired',  is to take a final incremental backup after all of the
files have been migrated or moved from that server/filespace.  ADSM will
then mark the files inactive, assigning the appropriate retention period
for the last backup.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Mary Vollmer[SMTP:Mary_Vollmer AT MGIC DOT COM]
>Sent:  Wednesday, June 18, 1997 11:34 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: backup status after filesystem deletion
>
>I have found this to be a problem as well.  When we remove a
>server/filespace,
>all the
>backups for that server remain in the status they were in at the last backup.
>Since most of our backup retention after file deletion in 60 days, I am
>usually
>able to delete all backups for the server after a couple of months.  However,
>we do have instances of retention up to 28 years.  Although this retention is
>for a very limited group of files, I am unable to delete any backups in the
>file
>system that they reside in - all backups must be retained for the amount of
>time specified in the longest management class used.  There should be a way
>of
>marking inactive all backups in a file system and allow ADSM to delete the
>backups according the the management class specification.
>
>
>In the previous Memo, dated, 06-18-97 09:08:05 AM, storman @ US.IBM.COM
>(Andrew
>Raibeck) @ MGICSMTP wrote:
>
>In order for ADSM to expire the backup versions, it has to be able to do an
>incremental backup against the file system. At that time it will detect that
>the files have been deleted from the file system, and expire the backups.
>However, if the file system is not there, it can't run an incremental backup
>on
>it.
>
>ADSM does not know whether you've deleted the file system or simply
>dismounted
>it, so it does nothing to that file system's backup version.
>
>If you want to delete the entire filespace from ADSM storage, you can use the
>DELETE FILESPACE command.
>
>Andy Raibeck
>ADSM Level 2 Support
>
>---------------------- Forwarded by Andrew Raibeck/San Jose/IBM on 06-18-97
>05:52 AM ---------------------------
>
>        ADSM-L @ VM.MARIST.EDU
>        06-16-97 06:12 PM
>Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet
>
>To: ADSM-L @ VM.MARIST.EDU @ internet
>cc:
>Subject: backup status after filesystem deletion
>
>I discovered a problem (at least it's a problem to me) with ADSM on AIX.  If
>files in a filesystem have been backed up, then the filesystem gets deleted
>(including the mount point), the backups still show as active in ADSM.  This
>means they will never, ever go away.
>
>Is it supposed to work this way or is this a bug I should report?
>