OK, now it really isn't duplicate files that the client can see...
these are all internal to adsm entries !
when adsm archives a file it was thought wise to archive the directory under
which it resides for all that misc junk found there (permissions, etc...)
what was done was to archive the directory under the longest retention
archive management class which existed within the domain for that client.
If you archived a million files from a single directory, that directory was
also archived (in the longest retention  mgmtclass) a million times !
If your longest retention archive mgmt was say 10 years but you archived
those files daily with a 7 day retention, things get ugly real fast...
the files that get cleaned up are not seen by the client... no query archive
from the client will show them...
you will notice on the accounting records when you archive a single file
there will be 2 items archived...
If you use a "show archive" debug command you can see these entries but you
can't do a delete archive from the client ('cause the client just isn't
allowed to see them, which goes back to that adsm internal thing...)

So where "removing duplicate archived files" is being used freely here to
describe things... NO client files are being removed...
if you have requested an archive of a file 50 times a day and the file never
changes... you will still have all those different archived versions
('cause actually they are not duplicates... they are individually requested
archives)
Only the internal overhead archives are removed.

Just thought I'd mention this...

later,
    Dwight

> ----------
> From:         ANGEL BUGARIN[SMTP:ANGEL.BUGARIN AT MAIL.SPRINT DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Wednesday, March 15, 2000 12:29 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Database growing too fast !!!
>
> Hi!
>
> I'm happy to know there's a command to remove duplicated
> archive files.
>
> Wouldn't it be better if there was a parameter to include
> with the "dsmc arc...." command so that it will not archive
> same files?  Or is there one already?
>
> This way you don't have to run the CLEAN ARCHDIR command
> every so often.
>
> Am I making sense at all?
>
> TIA,
> Angel
>
>
>    -----Original Message-----
>    From:       richard.cowen [SMTP:richard.cowen AT VTMEDNET DOT ORG]
>    Sent:       Wednesday, March 15, 2000 7:47 AM
>    To:         ADSM-L
>    Cc:         richard.cowen
>    Subject:    Re: Database growing too fast !!!
>
>    >In addition to all the other suggestions -- there is a hole in ADSM
>    3.x that
>    >seems to have been fixed (properly) with 3.2.1.50 where excssive
>    entries
>    >were kept in the ADSM database for directories that were archived. I
>    saw
>    >about a 30% drop in database size when I moved from 3.1.2.20 to
>    3.2.1.50.
>    >
>    >If you do a lot of archiving, you may want to look at upgrading . .
>    .
>    >
>
>    and there is a new command at 3.1.2.42:
>
>     CLEAN ARCHDIR
>
>    see the readme.
>    Syntax:
>    CLEAN ARCHDIRectories:  starts duplicate archive directory re-
>      moval for all nodes or a list of nodes, or resumes a cleanup
>      job that was canceled.
>
>      ---- CLEAN ARCHDIRectories ---------------------------------------
>                                  |             |  |                  |
>                                  +-nodeList----+  +-Format=Standard| |
>                                  |             |           Detailed--+
>                                  +-JOBid=jobId-+
>
>    --------------------
>       |
>       +-FIX=No|Yes ----
>
>      where:
>        nodeList is a comma separated list of node names
>        jobId is a resumable cleanup job
>        if nodeList or JOBid= are not specified, a new job that
>          cleans all nodes is assumed
>        The Standard Format of the command is the default and prevents
>        messages for each duplicate directory from being issued. If
>        Detailed is specified, messages are issued.
>        FIX=no   every archive directory entry for the nodeList or
>                 all nodes will be displayed.  This is the default.
>           =yes  duplicate directories will be removed
>
>    Query ARCHDIRClean:  the standard format of the command lists
>      information about a job.  The detailed format additonally
>      lists information for each node associated with a job.
>
>      ---- Query ARCHDIRClean --------------------------------------
>                                |       |  |                  |
>                                +-jobId-+  +-Format=Standard| |
>                                                    Detailed--+
>
>    CANcel ARCHDIRClean:  removes an archive cleanup job from the
>      server.
>
>      ---- CANcel ARCHDIRClean ---- jobId --------------------------
>
>
>    OTHER CHANGES:
>
>    Changes have also been made that remove archive directories when
>    they are eligible for expiration and not referenced, and the
>    same performance enhancement introduced in v3.1 for backup and
>    archive has been implemented for expiration and filespace dele-
>    tion.  In addition, the client will not bind archive directories
>    to the management class with the longest retention, and it will
>    not continue to archive duplicate directories (available from
>    client ptf 3.1.0.7).
>
>    ARCHIVE USAGE NOTES/TIPS:
>
>     - the cleanup utility may be run multiple times for the same
>       node.  If no duplicates are found, nothing is removed.
>
>     - description is one field that defines a unique archive
>       directory:  it is a factor that determines the number of
>       archive directory entries in the database.  Customers that
>       use the archive function extensively should consider
>       including the description field with each archive request,
>       especially when the default value is not appropriate to
>       to their needs.
>    --
>    Richard
>
>