OK, seems it works:

tsm: SHITSM01>q copygroup t=b

Policy    Policy    Mgmt      Copy      Versions Versions   Retain  Retain
Domain    Set Name  Class     Group         Data     Data    Extra    Only
Name                Name      Name        Exists  Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
DOM_SRV   ACTIVE    MC_90DAYS STANDARD  No Limit No Limit       60      60
DOM_SRV   SET_SRV   MC_90DAYS STANDARD  No Limit No Limit       60      60
STANDARD  ACTIVE    STANDARD  STANDARD  No Limit No Limit       60      60
STANDARD  STANDARD  STANDARD  STANDARD  No Limit No Limit       60      60

tsm: SHITSM01>q copygroup t=a

Policy        Policy        Mgmt          Copy            Retain
Domain        Set Name      Class         Group          Version
Name                        Name          Name
---------     ---------     ---------     ---------     --------
DOM_SRV       ACTIVE        MC_90DAYS     STANDARD         1,095
DOM_SRV       SET_SRV       MC_90DAYS     STANDARD         1,095
STANDARD      ACTIVE        STANDARD      STANDARD           365
STANDARD      STANDARD      STANDARD      STANDARD           365


TSM can retain 60day for backup data and archive data 3years.

Many thanks for your help.

Best Regards



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Saturday, December 26, 2009 12:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem

On Dec 25, 2009, at 3:08 AM, William ZHANG wrote:

> Again,
> I want to add a archive copy group for archiving files to retain 3 years.
>
> So, see manual, but donot fully understand.
> If I should input:
>
>
> Tsm:> define copygroup DOM_SRV SET_SRV MC_90DAYS type=archive
>       Dest=LTO3_ARCH_SRV retver=1095 retmin=1095
>
> Will this command rewrite my policyset and copygroup: SET_SRV MC_90DAYS?

A copygroup has two "sides": Backup and Archive.  You should always assure
that both have desired settings, as clients may happen to use both, though
you expect them to just do backups.

There is seldom a need to define a new policy set.  Once a copygroup is
updated, validate the policyset, then activate it.

>
>
> Or I need define a new policyset in DOM_SRV for archive copygroup?
>
> tsm:>q copygroup   (seams there is no archive copygroup in my DOM_SRV)

What do you see when you do 'help query copygroup'?  ;-)


  Richard Sims