Activate makes the activated policy set the active one by copying that policy set into active. It does not change the policy set that is "activated".
Each domain has only one ACTIVE policy set. The command ACTIVATE POLICYSET DOM_SRC STANDARD will copy the policy set STANDARD into DOM_SRC ACTIVE. but since the query didn't show a STANDARD policy set in the domain DOM_SRC, with the desired copygroup, there most likely is not a STANDARD policy set in that domain, and the command will fail. Domain DOM_SRC has 2 policy sets with copygroups, ACTIVE, which is a copy of whatever policy set was last activated, and SET_SRV, which is presumably the policy last activated since it is the only one in DOM_SRC with copygroups defined. To update the ACTIVE policy set in domain DOM_SRC, issue the update commands for the management classes and copygroups 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 <skyl...@u.washington.edu> 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 > > 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 2 > 1 60 60 > STANDARD ACTIVE STANDARD 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 >> >> >> >> 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." >> >> > > -- > -- Skylar Thompson (skyl...@u.washington.edu) > -- Genome Sciences Department, System Administrator > -- Foege Building S048, (206)-685-7354 > -- University of Washington School of Medicine > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine
