Re: TSM 5.3.4 Policy problem
Thanks All. Policy problem has been resolved currently. -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Thursday, December 24, 2009 9:11 PM To: William ZHANG Subject: Re: TSM 5.3.4 Policy problem On Dec 23, 2009, at 10:16 PM, William ZHANG wrote: > > --- > Another question how can I modidy archiving time to 3 years? See Archive Copy Group in the Administration Guide manual.
Re: TSM 5.3.4 Policy problem
OK, seems it works: tsm: SHITSM01>q copygroup t=b PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD No Limit No Limit 60 60 DOM_SRV SET_SRV MC_90DAYS STANDARD No Limit No Limit 60 60 STANDARD ACTIVESTANDARD STANDARD No Limit No Limit 60 60 STANDARD STANDARD STANDARD STANDARD No Limit No Limit 60 60 tsm: SHITSM01>q copygroup t=a PolicyPolicyMgmt CopyRetain DomainSet Name Class Group Version NameName Name - - - - DOM_SRV ACTIVEMC_90DAYS STANDARD 1,095 DOM_SRV SET_SRV MC_90DAYS STANDARD 1,095 STANDARD ACTIVESTANDARD 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:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Saturday, December 26, 2009 12:32 AM To: ADSM-L@VM.MARIST.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
Re: 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
Re: TSM 5.3.4 Policy problem
Hello All, Merry Christmas! 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? 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) PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD No Limit No Limit 60 60 DOM_SRV SET_SRV MC_90DAYS STANDARD No Limit No Limit 60 60 STANDARD ACTIVESTANDARD STANDARD No Limit No Limit 60 60 STANDARD STANDARD STANDARD STANDARD No Limit No Limit 60 60 Many thanks! Best Regards, william -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Thursday, December 24, 2009 9:11 PM To: William ZHANG Subject: Re: TSM 5.3.4 Policy problem On Dec 23, 2009, at 10:16 PM, William ZHANG wrote: > > --- > Another question how can I modidy archiving time to 3 years? See Archive Copy Group in the Administration Guide manual.
Re: TSM 5.3.4 Policy problem
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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Thursday, December 24, 2009 6:16 AM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Friday, December 18, 2009 12:24 AM To: ADSM-L@VM.MARIST.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 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:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain Domain
Re: 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:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Friday, December 18, 2009 12:24 AM To: ADSM-L@VM.MARIST.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 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:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 defau
Re: TSM 5.3.4 Policy problem
Hi All, The problem has been solved. Many thanks to all of you! Merry Christmas! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Monday, December 21, 2009 8:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem On Dec 20, 2009, at 8:46 PM, William ZHANG wrote: > Hi All, > Thanks for your help. > > Do anyone know if I change the setting of TSM , how can I restore my setting > back to before change? You would change your settings back in the same way that you altered them. Be aware when you reduce retention settings that you are committing all file versions outside the retention boundaries to go away. Richard Sims
Re: TSM 5.3.4 Policy problem
On Dec 20, 2009, at 8:46 PM, William ZHANG wrote: > Hi All, > Thanks for your help. > > Do anyone know if I change the setting of TSM , how can I restore my setting > back to before change? You would change your settings back in the same way that you altered them. Be aware when you reduce retention settings that you are committing all file versions outside the retention boundaries to go away. Richard Sims
Re: TSM 5.3.4 Policy problem
Hi All, Thanks for your help. Do anyone know if I change the setting of TSM , how can I restore my setting back to before change? Thanks! Best Regards, william -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: Friday, December 18, 2009 4:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem On 18 dec 2009, at 07:18, William ZHANG wrote: > Hi All, > > Thanks for your help! > > When I input: > ACTIVATE POLICYSET DOM_SRC SET_SRV > > TSM give a message: > ANR1557W The space management migration destination in management class > MC_90DAYS does > Not refer to a defined storage pool: SPACEMGPOOL. > If this pooll does not exist when policy set SET_SRV is activated, clients > will fail > When using this management class to migrate space-managed files to the > server. > > But actually,my stgpool are DISK_SRV and LTO3_BCK_SRV, not SPACEMGPOOL, so, read very carefully what this says: "clients to migrate space-managed files ...". Space management is also called HSM for Unix. So, when you use HSM for Unix, this warning is significant. If you don't use HSM for Unix (most likely), of you do but it points to a different management class (I'd think that you won't be asking this question in that case), you can safely ignore this message. -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM 5.3.4 Policy problem
On 18 dec 2009, at 07:18, William ZHANG wrote: > Hi All, > > Thanks for your help! > > When I input: > ACTIVATE POLICYSET DOM_SRC SET_SRV > > TSM give a message: > ANR1557W The space management migration destination in management class > MC_90DAYS does > Not refer to a defined storage pool: SPACEMGPOOL. > If this pooll does not exist when policy set SET_SRV is activated, clients > will fail > When using this management class to migrate space-managed files to the > server. > > But actually,my stgpool are DISK_SRV and LTO3_BCK_SRV, not SPACEMGPOOL, so, read very carefully what this says: "clients to migrate space-managed files ...". Space management is also called HSM for Unix. So, when you use HSM for Unix, this warning is significant. If you don't use HSM for Unix (most likely), of you do but it points to a different management class (I'd think that you won't be asking this question in that case), you can safely ignore this message. -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM 5.3.4 Policy problem
in DOM_SRC SET_SRV, then issue the VALIDATE (to see any possible issues) and ACTIVATE commands for DOM_SRC SET_SRV - ACTIVATE POLICYSET DOM_SRC SET_SRV - this will copy the current contents of the SET_SRV policy into ACTIVE. For the domain STANDARD, if the changes are needed there also, you would do the same thing for policy set STANDARD, so the commands would be issued to STANDARD STANDARD The 6.1 Administration Center has some features to assist in managing domains. It hides policy sets from the user, and shows changes since last activation in the management class notebook, or in the Manage Pending Changes form. You can make the changes to the management classes using the management class notebook, then activate from the Manage Pending Changes actions, which will do the validate before activation, and if there are any validation messages, display them and give you an option to continue with activation or resolve the issues. Carol Trible IBM Tivoli Storage Manager Development tri...@us.ibm.com Skylar Thompson Yeah, I typo'd the activate statement. It should be: ACTIVATE POLICYSET DOM_SRC STANDARD This will actually rename STANDARD to ACTIVE, and ACTIVE to STANDARD. William ZHANG wrote: > Hello Skylar, > > Do you mean, > >> update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV SET_SRV >> > Then, > >> update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV ACTIVE >> > > Right? > > tsm: SHITSM01>q copygroup > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > DomainSet Name Class Group Data > DataExtraOnly > NameName NameExists > Deleted Versions Version > - - - - > --- > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > DOM_SRV SET_SRV MC_90DAYS STANDARD 2 > 1 60 60 > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Skylar Thompson > Sent: Thursday, December 17, 2009 12:44 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem > > You actually want to modify the copy group from your inactive policy > set. In most cases this should be STANDARD rather than ACTIVE. You then > swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. > > William ZHANG wrote: > >> 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:ads...@vm.marist.edu] On Behalf Of >> Bos, Karel >> Sent: Wednesday, December 16, 2009 6:27 PM >> To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of >> Grigori Solonovitch >> Sent: woensdag 16 december 2009 10:31 >> To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com >> >&g
Re: TSM 5.3.4 Policy problem
Erm, can't update the active policy set :) Update copygroup DOM_SRV SET_SRV MC_90DAYS type=backup verexists=nolimit verdeleted=nolimit retextra=60 retonly=60 Validate and activate the set afterwards. Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: donderdag 17 december 2009 17:24 To: ADSM-L@VM.MARIST.EDU Subject: Re: 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 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:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 PolicyP
Re: 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 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:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default
Re: TSM 5.3.4 Policy problem
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:ads...@vm.marist.edu] On Behalf Of >> Grigori Solonovitch >> Sent: woensdag 16 december 2009 10:31 >> To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com >> >> Please consider the environment before printing this Email >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> William ZHANG >> Sent: Wednesday, December 16, 2009 12:28 PM >> To: ADSM-L@VM.MARIST.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 >> >> >> >> PolicyPolicyMgmt Copy Versions >> Versions Retain Retain >> >> DomainSet Name Class Group Data >> DataExtraOnly >> >> NameName NameExists >> Deleted Versions Version >> >> - - - - >> --- >> >> DOM_SRV ACTIVEMC_90DAYS STANDARD 2 >> 1 90 90 >> >> DOM_SRV SET_SRV MC_90DAYS STANDARD90 >> 90 90 90 >> >> STANDARD ACTIVESTANDARD 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 >> >> >> >> PolicyPolicyMgmt Default Description >> >> DomainSet Name Class Mgmt >> >> NameName Class ? >> >> - - - --
Re: TSM 5.3.4 Policy problem
Zhang, It is good practice to validate the policyset before activating it. After updating the copygroup, run validate po DOMAIN_NAME POLICYSET_NAME. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Thursday, December 17, 2009 12:24 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem Hello Skylar, Do you mean, > update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV SET_SRV Then, > update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV ACTIVE Right? tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD 2 1 60 60 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Skylar Thompson Sent: Thursday, December 17, 2009 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: > 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:ads...@vm.marist.edu] On Behalf > Of Bos, Karel > Sent: Wednesday, December 16, 2009 6:27 PM > To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf > Of Grigori Solonovitch > Sent: woensdag 16 december 2009 10:31 > To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com > > Please consider the environment before printing this Email > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of William ZHANG > Sent: Wednesday, December 16, 2009 12:28 PM > To: ADSM-L@VM.MARIST.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 > > > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > > DomainSet Name Class Group Data > DataExtraOnly > > NameName NameExists > Deleted Versions Version > > - - - - > ---
Re: TSM 5.3.4 Policy problem
Yeah, I typo'd the activate statement. It should be: ACTIVATE POLICYSET DOM_SRC STANDARD This will actually rename STANDARD to ACTIVE, and ACTIVE to STANDARD. William ZHANG wrote: > Hello Skylar, > > Do you mean, > >> update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV SET_SRV >> > Then, > >> update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV ACTIVE >> > > Right? > > tsm: SHITSM01>q copygroup > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > DomainSet Name Class Group Data > DataExtraOnly > NameName NameExists > Deleted Versions Version > - - - - > --- > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > DOM_SRV SET_SRV MC_90DAYS STANDARD 2 > 1 60 60 > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Skylar Thompson > Sent: Thursday, December 17, 2009 12:44 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem > > You actually want to modify the copy group from your inactive policy > set. In most cases this should be STANDARD rather than ACTIVE. You then > swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. > > William ZHANG wrote: > >> 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:ads...@vm.marist.edu] On Behalf Of >> Bos, Karel >> Sent: Wednesday, December 16, 2009 6:27 PM >> To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of >> Grigori Solonovitch >> Sent: woensdag 16 december 2009 10:31 >> To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com >> >> Please consider the environment before printing this Email >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> William ZHANG >> Sent: Wednesday, December 16, 2009 12:28 PM >> To: ADSM-L@VM.MARIST.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 >> >> >> >> PolicyPolicyMgmt Co
Re: TSM 5.3.4 Policy problem
Hello Skylar, Do you mean, > update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV SET_SRV Then, > update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV ACTIVE Right? tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD 2 1 60 60 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Skylar Thompson Sent: Thursday, December 17, 2009 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: > 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:ads...@vm.marist.edu] On Behalf Of > Bos, Karel > Sent: Wednesday, December 16, 2009 6:27 PM > To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of > Grigori Solonovitch > Sent: woensdag 16 december 2009 10:31 > To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com > > Please consider the environment before printing this Email > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > William ZHANG > Sent: Wednesday, December 16, 2009 12:28 PM > To: ADSM-L@VM.MARIST.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 > > > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > > DomainSet Name Class Group Data > DataExtraOnly > > NameName NameExists > Deleted Versions Version > > - - - - > --- > > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > > DOM_SRV SET_SRV MC_90DAYS STANDARD90 > 90 90 90 > > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > --
Re: TSM 5.3.4 Policy problem
You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: > 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:ads...@vm.marist.edu] On Behalf Of > Bos, Karel > Sent: Wednesday, December 16, 2009 6:27 PM > To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of > Grigori Solonovitch > Sent: woensdag 16 december 2009 10:31 > To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com > > Please consider the environment before printing this Email > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > William ZHANG > Sent: Wednesday, December 16, 2009 12:28 PM > To: ADSM-L@VM.MARIST.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 > > > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > > DomainSet Name Class Group Data > DataExtraOnly > > NameName NameExists > Deleted Versions Version > > - - - - > --- > > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > > DOM_SRV SET_SRV MC_90DAYS STANDARD90 > 90 90 90 > > STANDARD ACTIVESTANDARD 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/200
Re: TSM 5.3.4 Policy problem
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:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD 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 attachmen
Re: 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:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD 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.&quo
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.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.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 PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD 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 PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD 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."
