WE are running on os/390 2.6 with adsm 3.1.2.1 and I have run expire inventory
and the completed backup cycle.




"Robinson, Cris" <Cris.Robinson AT LIBERTYMUTUAL DOT COM> on 05/24/99 12:26:27 
PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Kelvin Kloehn/Texas Utilities)
Subject:  Re: Backup Copy Groups - How do I change what has already been ba
      cked up




What version are you on. There is a known problem with expiring inventory.
Looks like that may be your problem.

C

__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / ADSM
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

Dilbert words of Wisdom:
Accept that some days you're the pigeon,
and some days you're the statue!

> -----Original Message-----
> From: Kelvin Kloehn [SMTP:kkloehn1 AT TXU DOT COM]
> Sent: Monday, May 24, 1999 12:37 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Backup Copy Groups - How do I change what has already been
> backed up
>
> +Our current backup copy groups have setting some like:
> Policy Domain Name  TAPEBKUP
> Policy Set Name          ACTIVE
> Mgmt Class Name          ADSM01BKUP
> Copy Group Name          STANDARD
> Versions Data Exists     5
> Versions Data Deleted    1
> Retain Extra Versions    22
> Retain Only Version      35
> Copy Mode           MODIFIED
> Copy Serialization       DYNAMIC
> Copy Frequency           0
> Copy Destination         BACKTAPE
>
> With these setting we can and have ended up with 1 active and 21 inactive
> versions of a file when what we really wanted was 1 active and 4 inactive
>       versions
> of the file. I have since changed the "Retain Extra Versions" to NOLIMIT,
> which
> according to the doc says that extra backup versions are deleted during
> backup
> processing under the control of VEREXISTS or VERDELETED.  There has been
> at least one backup cycle run since the change has been made but we still
> have
>       more
> than the 5 desired versions. My questions are:  Do the ADSM clients need
> to
>       stopped
> and restarted for the change to the backup copygroup to be picked up? Or
> do I
>       have
> to define a new default MGMT Class?