Re: archive retaining dirs differently from files?
1999-01-06 04:34:08
Subject: |
Re: archive retaining dirs differently from files? |
From: |
"Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM> |
Date: |
Wed, 6 Jan 1999 10:34:08 +0100 |
We have exactly the same problem, forcing us to regularly and manually
delete old archives packages, containing only directories as the files have
been normaly expired!
Thanks,
Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com
> -----Original Message-----
> From: Bruce Elrick [SMTP:belrick AT HOME DOT COM]
> Sent: Wednesday, 6. January 1999 04:51
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: archive retaining dirs differently from files?
>
> Has anyone experienced the following?
>
> We do daily archives of Oracle database and control files (cold) using
> -archmc=21days where that mgmtclass obviously has an archive copy group
> with a 21 day retention. Once per month we archive the whole system
> (don't get me started about ADSM's treatment of symbolic links) using
> -archmc=400days. This works well, for the most part.
>
> I both cases we use the -desc option:
> -desc="Daily Oracle Cold Archive 1999/01/05" or
> -desc="Monthly Full System Archive 1999/01/06"
> Where, as you can see, the description carries a date stamp. This is
> really handy with the way version 3 presents archives in the GUI
> grouping by description.
>
> However, we noticed that archives older than 21 days weren't
> disappearing when we look at them using the client GUI. Or rather, the
> directories weren't expiring, while the files were!
>
> We do set dirmc in the options file so that we control which management
> class directories get bound to. I've been burned by large NT restores
> where the extended attributes of directories are stored in the storage
> pool which is dictated by the mgmtclass with the longest retention; the
> client restores all the directories going through a whole set of tapes,
> then restores the files going through the same set, taking twice as long
> as it should. Nowadays I set dirmc to have a destination stgpool that
> is a disk pool that does not flush to tape.
>
> I thought that perhaps the dirmc was causing the archives of the
> directories to be retained for a different retention. However, when I
> read the docs (options.doc on unix clients) on dirmc, it specifically
> states the dirmc has no effect on archives of directories. It says that
> archives of directory objects are bound to the mgmtclass with the
> longest retention. I suppose that makes sense when you are using the
> include list to bind archive files to various mgmtclasses, but who does
> that? Usually if you want archives of different classes of files to be
> retained for different lengths, you archive them separately with
> different -archmc options. As well, the language does not make it clear
> whether or not archmc should override this binding of directory archive
> objects to the mgmtclass with longest retention or not.
>
> Could someone from ADSMland clarify the latter? Does the -archmc option
> overide the default behaviour of archives of directories being bound to
> mgmtclasses with the longest archive retention?
> I hope so. If so, what could be my problem with archive files expiring
> but not directories?
>
> Thanks...
> Bruce
|
|
|