Nope. The files are actually marked as INACTIVE by the client running the
backup.
When the backup starts, the first thing that happens (on a normal
incremental backup) is the server sends down the list of what got backed up
last time, so the client can compare with what it finds in the file
system/directory now. Files that no longer exist are marked inactive. So
if you can't run a backup on the filesystem, those files will never go
inactive.
What we do is run a script periodically to produce a list of all the
filespaces that haven't been backed up in 6 months, and also have the script
generate the appropriate DELETE FILESPACE commands which we can run after
doing a sanity check on the list. And we make THAT part of our SOP.
Hope that helps...
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
-----Original Message-----
From: MC Matt Cooper (2838) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 2:13 PM
To: [EMAIL PROTECTED]
Subject: how to EXPIRE UNIX files from unmounted/deleted file system
Hello all,
In my seemingly never ending quest to get my tape retention clean, I
have come across a UNIX CLIENT problem. There were some file systems that
were created for doing a temporary move/copy procedures. While the File
system existed, it was backed up. Now I have a tape that is 5 months old
and has a bunch of data on it that worthless but does not want to change to
a status of INACTIVE. I know I could take the tape and scratch it with a
DISCARD DATA option, but I want to do this in a clean way and make it a part
of the Stand Operating Procedure. Does anyone know the proper change to put
into the include/exclude list so this UNIX client will have these files
marked INACTIVE?
Matt
