Hi Craig,

Thanks for your reply.   I did get one response - I replied directly to
him.   The solution was to make a separate mgmt class/copy group with
shrdynamic, and specify that for certain problem log files in the
inclexcl file.   My normal copy groups use shrstatic.

--
Gene Mangum
Gene Mangum
University of Michigan Medical Center


On Mon, 13 Jul 1998, Craig Murphy wrote:

> If you haven't worked it out yet (I'm a bit behind here and can't see any
> replies) perhaps your serialization of your copy group is set to static. Your
> options are:
>
> Static = If file is modified during a backup then not backed up and does not
> retry
> Shared Static = As above but does retry as many time as set by CHANGINGRETRIES
> Dynamic = Modified file is backed up on first attempt.
> Shared Dynamic = Modified file is backed up on its last try. Again uses the
> CHANGINGRETRIES option
>
>
> Craig Murphy
>
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 10-07-98 00:35:28
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: dsmsched.log changed
>
>
> Hi All,
>
> Since I upgraded clients and server to v3, one node has consistently
> been refusing to backup dsmsched.log, saying that it has changed during
> the backup.   This results in the backup status being "Failed".   This
> is not hapenning on the other nodes (except one other last night), and
> it never happened on v2.   I know I could put this file in the exclude
> list, but I kinda like having it backed up.   Has anyone else seen this?
>
> --
> Gene Mangum
> University of Michigan Medical Center
>
>
>
>