ADSM-L

Re: [ADSM-L] TSM 5.3.4 Policy problem

2009-12-24 00:38:49
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 24 Dec 2009 08:37:20 +0300
I think you just need to wait for 60 days.

But you need to understand next relationship:

Node (dsm.opt in Windows, InclExcl list in UNIX) --> Management class --> Copy 
group (you are hire).

If your management class is default, you do need to do anything. If you have a 
few management classes for domain and modified class (copy group) is not 
default, you need to edit dsm.opt or include/exclude list.

To control expiry process:

1)     connect to node using your management class;

2)     start TSM Client GUI;

3)     select restore;

4)     click View-->Display active\inactive files;

5)     check file C:\Program Files\Tivoli\TSM\baclient\dsmsched.log or any 
other file , which is updated daily - it should be 1 active version and some 
number of inactive files. This number can show you current expiry period, but 
if you increased expiry period just now, you will see one more inactive file 
every day till new expiry date is reached.



Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com



Please consider the environment before printing this Email





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
William ZHANG
Sent: Thursday, December 24, 2009 6:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem



Hi All,

I have updated copygroup to "type=backup verexists=nolimit

verdeleted=nolimit retextra=60 retonly=60"

and, ACTIVATE all my POLICYSET.



Then, Could you please tell how can I check it works or not?

Because, I found some files have been kept (since 12/22/2009) , but some

files still missed(maybe say expired).

(just have two policyset, and change them all)



So need I modify any other setting in TSM ?

Such as "update domain backupretention=60" ? and anyother ?



-------------------

Another question how can I modidy archiving time to 3 years?





Many thanks!



Best Regards,

william



-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of

David E Ehresman

Sent: Friday, December 18, 2009 12:24 AM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem



If you REALLY want to keep data in TSM for 60 days, you need



Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=nolimit

verdeleted=nolimit retextra=60 retonly=60



Otherwise, multiple backups run during a day can result in files expiring in

less than 60 days.



David



>>> William ZHANG <william.zhang AT ST DOT COM> 12/16/2009 11:27 PM >>>

Hello,



Thanks Grigori,Karel,

I want to retain deleted data 60days in TSM.

So should I input:



Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60

verdeleted=60 retextra=60 retonly=60



But got error, said, active policy cannot be modified,

So could anyone can tell me how can I modified my policy set and copygroup

so that I can get what I want?





Many thanks!



William





-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of

Bos, Karel

Sent: Wednesday, December 16, 2009 6:27 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem



I would take a look at the RETExtra/Only parm of the copy group, they manage

the data by date instead of versions. Managing retention time using the

versions parameters can give some unintended results (an extra backup of a

changed file will reduce the period you can restore from for instance).



Kind regards,



Karel





-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of

Grigori Solonovitch

Sent: woensdag 16 december 2009 10:31

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: TSM 5.3.4 Policy problem



Yes, but it is better to use 60 instead of 59.



Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Bank of Kuwait and Middle East http://www.bkme.com



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail:

G.Solonovitch AT bkme DOT com



Please consider the environment before printing this Email





-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of

William ZHANG

Sent: Wednesday, December 16, 2009 12:28 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: [ADSM-L] TSM 5.3.4 Policy problem



Hello All,







I meet a problem,



If I want to retain deleted data 60days in TSM, what commands should I input

to modified policy in TSM?







should the "versions data exists"  and "versions data deleted" be modified

from 2 to 59 , right?







These are my configuration:



---------------------------------------------------------------



tsm: SHITSM01>q copygroup







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             2

1           90          90



DOM_SRV       SET_SRV       MC_90DAYS     STANDARD            90

90           90          90



STANDARD      ACTIVE        STANDARD      STANDARD             2

1           30          60



STANDARD      STANDARD      STANDARD      STANDARD             2

1           30          60



---------------------------------------------------------------



tsm: SHITSM01>q domain f=d







              Policy Domain Name: DOM_SRV



            Activated Policy Set: SET_SRV



            Activation Date/Time: 05/10/2007 11:09:44



           Days Since Activation: 951



    Activated Default Mgmt Class: MC_90DAYS



      Number of Registered Nodes: 3



                     Description:



 Backup Retention (Grace Period): 60



Archive Retention (Grace Period): 1,095



  Last Update by (administrator): ADMIN



           Last Update Date/Time: 07/30/2009 11:30:05



                Managing profile:



                 Changes Pending: Yes







              Policy Domain Name: STANDARD



            Activated Policy Set: STANDARD



            Activation Date/Time: 05/09/2007 12:41:05



           Days Since Activation: 952



    Activated Default Mgmt Class: STANDARD



      Number of Registered Nodes: 1



                     Description: Installed default policy domain.



 Backup Retention (Grace Period): 30



Archive Retention (Grace Period): 365



  Last Update by (administrator): SERVER_CONSOLE



           Last Update Date/Time: 05/09/2007 12:41:05



                Managing profile:



                 Changes Pending: No







-----------------------------------------------------------



tsm: SHITSM01>q mgmtclass







Policy        Policy        Mgmt          Default       Description



Domain        Set Name      Class         Mgmt



Name                        Name          Class ?



---------     ---------     ---------     ---------

------------------------



DOM_SRV       ACTIVE        MC_90DAYS     Yes



DOM_SRV       SET_SRV       MC_90DAYS     Yes



STANDARD      ACTIVE        STANDARD      Yes           Installed

default



                                                         management class.



STANDARD      STANDARD      STANDARD      Yes           Installed

default



                                                         management class.



--------------------------------------------------------------



Please consider the environment before printing this Email.



"This email message and any attachments transmitted with it may contain

confidential and proprietary information, intended only for the named

recipient(s). If you have received this message in error, or if you are not

the named recipient(s), please delete this email after notifying the sender

immediately. BKME cannot guarantee the integrity of this communication and

accepts no liability for any damage caused by this email or its attachments

due to viruses, any other defects, interception or unauthorized

modification. The information, views, opinions and comments of this message

are those of the individual and not necessarily endorsed by BKME."

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."

<Prev in Thread] Current Thread [Next in Thread>