> ----------
> From:         Joyce Woods[SMTP:Joyce.Woods AT ITPMS DOT COM]
> Sent:         Monday, April 17, 2000 5:13 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Archive questions !!
>
> Hi Everyone!!
>
> This is my first time attempting to archive some Unix directories.  I have
> set
> up an archive copy group and we submit the directories to be archive.  And
> I
> receieve the error message "ANS5007W  The policy set does not contain any
> archive copy groups.  Unable to continue with archive."  Yuck !!!  Any
> ideas.
>
> Thanks,
> Joyce
>
> Joyce,
> here is something I dug up from the ADSM reference. I have not set up an
> archive copy group myself, but here is some info. It may or may not step
> you in the right direction. Good Luck!
> Kye Burns
> krburns AT firstam DOT com
>
> Archive
>
> When a user requests the archiving of a file or a group of files, ADSM
> performs the following steps to determine eligibility:
>       Checks the files against the user's include-exclude list to see if
> any management classes are specified:
>                       *       ADSM uses the default management class for
> files that are not bound to a management class.
>                       *       If no include-exclude list exists, ADSM uses
> the default management class unless the user specifies another management
> class. See the user's publication for the appropriate client for details.
>       Checks the management class for each file to be archived.
>                       *       If the management class contains an archive
> copy group and the serialization requirement is met, the file is archived.
> Serialization specifies how files are handled if they are modified while
> being archived and what ADSM does if modification occurs.
>                       *       If the management class does not contain an
> archive copy group, the file is not archived.
> Automatic Migration from a Client Node
>
> A file is eligible for automatic migration from a client node if it meets
> all of the following criteria:
>       *       It resides on a node on which the root user has added and
> activated hierarchical storage management. It must also reside in a local
> file system to which the root user has added space management, and not in
> the root (/) or /tmp file system.
>       *       It is not excluded from migration in the include-exclude
> list.
>       *       It meets management class requirements for migration:
>                       *       The file is not a character special file, a
> block special file, a FIFO special file (that is, a named pipe file) or a
> directory.
>                       *       The file is assigned to a management class
> that calls for space management.
>                       *       The management class calls for automatic
> migration after a specified number of days, and that time has elapsed.
>                       *       A backup version of the file exists if the
> management class requires it.
>                       *       The file is larger than the stub file that
> would replace it (plus one byte) or the file system block size, whichever
> is larger.
>
>