> I can't manually delete by filespace at the end of the default retention
period because we have some
> backups that must be retained for 7 years.
There have been some good, inovative solutions suggested, but I have to
question the original premise. Aren't all of the files being moved to the new
machine? If so, then why can't you delete the file spaces, since you will now
have a good backup of the files on their new server. There is no diference in
the files. If you still can't, can the files that must be identified be
brought forward and then archived for appropriate periods.
The solutions proposed actually do scratch the files, based on what you have
as a management class definition, so they might be extra effort to do the same
thing as a delete file space.
Since this is an election year, just thought I'd add my $.02 to keep in the
spirit of the primaries.
Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: FW: Backup file cleanup
02-11-96 12:22 PM
We're going to be running into the same situation very soon... I came up
with the following 2 options...
1) Bring up a 'minimal' Novell server (Novell and ADSM installed) with the
same name as the server your Novell administrators got rid of. Run an
incremental backup... this'll mark most of the files inactive which could
'clean up' most of the older active backup versions. You could then either
keep the data on the ADSM server or Export it and delete it from ADSM to
reclaim the database space.
2) Set up a special management class to deal with the 'last' backup of the
server. Update the DSM.OPT file on the server to assign this management
class to all the files, then run the final incremental backup. This could be
used to reduce the number of versions of backups being maintained, extend
the retention for inactive files, etc. This wouldn't work if they already
got rid of the server as in your case but I'm leaning towards this method
when the situation arises here.
Good luck !!!!
Tim Pittson
pittson1 AT bwmail1.hcc DOT com
----------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Backup file cleanup
Date: Friday, February 09, 1996 1:48PM
Our Novell administrators are in the process of re-organizing all their
servers. They have created new server names and copied data from 1 or more
old
servers to the new servers. When they are done copying the data, our users
become active on the new server and the old server, although still intact,
is
'turned off'. After the last backup of these servers, many of the of the
ADSM
backup versions were in active status. I removed these old servers from the
backup schedule but would also like ADSM to maintain the backup versions
stored
for these old servers according to the management class specifications (most
of
them can be deleted since the files are now active on the new servers).
This
isn't going to happen because there is nothing to change the status of the
active backups to inactive. The only thing I saw that might help me is the
RENAME NODE command but the description doesn't state that the backups will
be
bound to this new name. It also doesn't state whether or not a node can be
renamed to a node name that already exists. I can't manually delete by
filespace at the end of the default retention period because we have some
backups that must be retained for 7 years. Does anyone have any ideas on
how
I
can get this data cleaned up and still keep my long retention data? Thanks
in
advance for your responses.
|
