Diana, I guess I added to your confusion... I will try to clarify. Your CAN use the policy set "trick" to flip between modified and absolute; that's about the only option that will help for a single-node-name solution. Any other attributes that are changed in the copy-group could adversely affect the desired version count subject to expiration.
So, in your example, you could (once a week, when you have the cycles to handle) activate a policy set that sets "absolute" for all nodes in that domain. Then on Monday, re-activate the normal policy set for "modified" incrementals. Assuming you have identical ve/vd/re/ro parameters, with ve/vd both = 30, you will have 30 versions (max) of any given file, for up to re/ro number of days. I hesitate to recommend this approach, because the granularity of control is at the policy domain level. I would (firstly) question why your customer needs to run TSM as if it were Veritas or Legato; full backups this often are unnecessary under TSM, due to its progressive incremental technology. If you must run periodic full backups, I would do it using an alternative node-name... so you don't get hurt trying to complete the backup in a given 24-hour cycle for ALL nodes in the domain (you'd have node-level granularity). Hope this helps. Don ----- Original Message ----- From: "Diana Noble" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 6:22 AM Subject: Re: Help Understanding Mgmt classes > Don - > > I think I'm more than a bit confused. So, according to your first paragraph, I > cannot activate a new (different) policy set within a domain and expect that my > files will then be backed up according to the mgmtclass specifications in in > the new policy set? > > So what is the best way to swap back and forth between absolute and modified > backups, keeping a retention of 30 versions combined. Would it be best to > modifiy my existing management class backup copygroup to absolute or modified > depending on what should be done that day, leaving the version count the same? > If I change it to absolute, what does that do the modified backups already > taken, anything? > > Thank you for your help. > > Diana > > > > Quoting "Don France (TSMnews)" <[EMAIL PROTECTED]>: > > > You are abit confused. The *ONLY* way to have TWO policies applicable to a > > given file is to use TWO node-names for your backups; swapping policy sets > > *may* work for your situation, if what you want (and set) is 30 versions of > > a given file... that piece will work. > > > > Files can be bound only to one management class at a time; if you try > > changing MC for the file, it will change ALL versions to that MC, not just > > the next backup. The policyset-swap trick is useful when changing from > > modified to absolute and back; that's about the only use I've ever seen > > for > > multiple policy sets. Hope this helps. > > > > Regards, > > Don > > > > Don France > > Technical Architect - Tivoli Certified Consultant > > Professional Association of Contract Employees (P.A.C.E.) > > San Jose, CA > > (408) 257-3037 > > [EMAIL PROTECTED] > > > > ----- Original Message ----- > > From: "Diana Noble" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, May 02, 2002 10:13 AM > > Subject: Help Understanding Mgmt classes > > > > > > > Hi All - > > > > > > I believe I have my management classes all defined with a major flaw. We > > > do scheduled modified backups during the week and scheduled absolute > > > backups on Sundays. I have two management classes defined. Both have > > the > > > same retentions coded but one has "absolute" for the copy mode and one > > has > > > "modified" coded. I have a script that swaps the default management > > class > > > on Sundays. After rereading the manual and looking at the archives of > > this > > > list, it seems there's no guarantee that the backup will use the default > > > Management class. Also, if I've specified to keep 30 versions of the > > data > > > in both management classes, does that mean I'm going to retain 30 > > versions > > > from the "absolute" and 30 versions of the "modified"? I really want 30 > > > versions all together. > > > > > > My thought is to create multiply policy sets, and activate the policy set > > > that contains only the management class I want. I would then specify a > > > retention of 4 versions for my policy set that contains the management > > > class for "absolute". This won't delete any of my 30 versions that were > > > saved using the policy set that contains the "modified" management class, > > > will it? Does this make sense, or am I still way off here? > > > > > > Diana > >
