ADSM-L

[no subject]

2015-10-04 17:32:29
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


--openmail-part-1142276a-00000001--
=========================================================================
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=