I strongly encourage you to read the TSM Administrator's Guide from cover to cover, as it provides a pretty thorough overview of what TSM can do, and how to do it, including information how TSM policy management works. Yes, it's a pretty big book, but should be considered essential reading for TSM administrators.
My two cents. :-) Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 12/16/2004 19:08:12: > Thanks. Just wanted to double check since I've never done this before. > > Thanks again, > Eric > > -----Original Message----- > From: Prather, Wanda [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 16, 2004 1:14 PM > To: ADSM: Dist Stor Manager > Cc: Jones, Eric J > Subject: RE: POLICY SET Question > > > You are exactly correct! > > Changes to the management classes/copy groups do not take effect > immediately, they take effecty when you Activate the policy set. > That will make the Changed policy set and Active the same. > > Changing RETEXTRA and RETONLY to 180 will do what you want. > > The only time you should have to stop/restart your TSM server are to > apply server maintenance, to restore the data base (hopefully something > you nEVER have to do!) or (sometimes) to clear a hardware problem. > > Wanda Prather > "I/O, I/O, It's all about I/O" -(me) > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Jones, Eric J > Sent: Wednesday, December 15, 2004 1:05 PM > To: [EMAIL PROTECTED] > Subject: POLICY SET Question > > > Good Afternoon. > I'm new to the policy sets and someone else set them up for the server. > I need to make a change to a Policy Set and was wondering if I needed to > stop and start the server for the change to take affect. > I need to change the Retain Extra Versions and Retain Only Version from > 30 days to 180 days(6 months). > If I go into the POLICY SET and drill down to "STANDARD Backup Copy > Group" for the policy and do a "Update Copy Group" and change from 30 to > 180 will it take affect immediately or do I need to be at the Policy > Sets, Select "Validate Policy Set", then "Activate Policy Set". Also > when I "Activate Policy Set" does this move it to the "ACTIVE" so both > are the same. > I need to keep all copies of the file for 180 days. > I'm running TSM 5.2.2 server on AIX 5.2. > > ======================================================================== > ============= > Backup Copy Groups : UNIX6MONTH UNIX6_MONTH_POLICY UNIX6_MONTH_MGMT > STANDARD > Policy Domain Name UNIX6MONTH > Policy Set Name UNIX6_MONTH_POLICY > Mgmt Class Name UNIX6_MONTH_MGMT > Copy Group Name STANDARD > Versions Data Exists NOLIMIT > Versions Data Deleted NOLIMIT > Retain Extra Versions 30 > Retain Only Version 30 > Copy Mode MODIFIED > Copy Serialization SHRSTATIC > Copy Frequency 0 > Copy Destination DISKPOOL3 > Table of Contents (TOC) Destination - > Last Update Date/Time 2004-08-24 07:31:25.000000 > Last Update by (administrator) JONES > Managing profile - > > Have a Great Day, > Eric Jones > > * [EMAIL PROTECTED] > > *: 607-751-4133 > Cell : 607-972-7621
