Re: Help Understanding Mgmt classes
Thank you Don and Zlatko for all the information on management classes. It really helped. I know what we are doing is against the TSM backup ideology. The system was originally setup to do AFS backups only, which doesn't really use the management class. The type of backup and it's retention is handled through AFS. Now we have another group who wishes to use our TSM system for their Win2k backups. We currently do not do copypools as our resources are limited and we didn't need them for the type of data we back up under AFS. We save a week old copy of the backups offsite and that was fine for us. The other users who are now testing their backups on our TSM server are taking fulls once a week for purpose of offsite storage. We intend on changing this once they have decided whether they are going to continue to use the TSM server for backups. They don't care for the copypool backup idea and prefer a snapshot taken once a month by using instant archive. We are still in discussions with them on what their requirements are and how we want to accomplish them and how much additional hardware will be required to meet their requirements. Thanks again for all your help. Diana Quoting Zlatko Krastev <[EMAIL PROTECTED]>: > Diana, > > The only "major flaw" I see is your intention to use "absolute". This is > against the TSM backup ideology. I am interested what is the business > reason to go this way. > The rest is "as designed" but I personally am not happy with your design. > If you change default class (be it through setting another one as default > or by activating another policy set), on next backup all files will be > re-bound to that class. But if in the new policyset you set retextra=4 on > next expiration 26 versions would be deleted. Having two mgmt classes > differing only by mode will not give you two times 30 versions. The number > of versions kept will be min(30,30) - again 30. > Do not overcomplicate your policy. Create one class (or more) and use it. > If you still want to have "full" backup on Sundays - I would use selective > backup in Sunday's schedule and leave policy/classes unchanged. Again - is > there actual need to resend all the data over the LAN? It is on the server > already. Lets manage it better. If you can define the requirements in > *business* terms only and prevent full/incremental/differential ideology > to predefine the solution - this list can help you. > TSM is very different from other backup products. And sometimes its > "traditional" usage looks to me as driving a jet fighter on a highway with > 100 km/h instead of flying with 1500 km/h over shorter route. > > Zlatko Krastev > IT Consultant > > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > cc: > > 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 >
Re: Help Understanding Mgmt classes
ok, thanks... it makes sens to me now.. I have some work to do to change it all ! Mike > ___ > Michael REGELIN > Ingénieur Informatique - O.S.O. > Groupware & Messagerie > Centre des Technologies de l'Information (CTI) > Route des Acacias 82 > CP149 - 1211 Genève 8 > Tél. + 41 22 3274322 - Fax + 41 22 3275499 > Mailto:[EMAIL PROTECTED] > http://intraCTI.etat-ge.ch/services_complementaires/messagerie.html > __ > -Message d'origine- De : Don France (TSMnews) [mailto:[EMAIL PROTECTED]] Envoyé : vendredi, 3. mai 2002 23:22 À : [EMAIL PROTECTED] Objet : Re: Help Understanding Mgmt classes Michael, The rules I described apply universally to backup objects with the same name owned by a given node in backup storage. With TDP products, in some cases, the backup objects are given different, unique names every time a backup occurs -- you must review the Install & User's Guide for the TDP you are using. For example, TDP v1 for Exchange creates unique names for every backup, so retention/expiration must be done manually; in v2 of this TDP, objects stored in backup storage are given the same name, so their retention/expiration becomes "automated" like for files backed up by the b/a-client -- and the management class rules, as I described, will apply. Hope this helps. - Original Message - From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 5:17 AM Subject: Re: Help Understanding Mgmt classes Hi Don, I'm not sure to understand your answer. By the way, thanks for your answer. I'm interested in this mailing and was not the originator. Our Backup solution is based on tdp for domino 1.1.2. Our tsm client is 4.2.1.20 based on Windows Nt4 server. here is our strategy: a full backup a week - keeping 5 version (management class=week) a full backup a month - keeping 13 version (management class=month) an incremental version a day - keeping 5 version (management class=daily) after reading your mail, I understand that having 3 MC for the same file will cause the retention to change after every backup when the MC is used. So for example: when week backup is finished, it will apply the MC for the file and when month backup is finished, it will change all retention on every file base on the new MC ? thanks Mike > ___ > Michael REGELIN > Inginieur Informatique - O.S.O. > Groupware & Messagerie > Centre des Technologies de l'Information (CTI) > Route des Acacias 82 > CP149 - 1211 Genhve 8 > Til. + 41 22 3274322 - Fax + 41 22 3275499 > Mailto:[EMAIL PROTECTED] > http://intraCTI.etat-ge.ch/services_complementaires/messagerie.html > __ > -Message d'origine----- De : Don France (TSMnews) [mailto:[EMAIL PROTECTED]] Envoyi : vendredi, 3. mai 2002 03:39 @ : [EMAIL PROTECTED] Objet : Re: Help Understanding Mgmt classes 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 t
Re: Help Understanding Mgmt classes
Diana, The only "major flaw" I see is your intention to use "absolute". This is against the TSM backup ideology. I am interested what is the business reason to go this way. The rest is "as designed" but I personally am not happy with your design. If you change default class (be it through setting another one as default or by activating another policy set), on next backup all files will be re-bound to that class. But if in the new policyset you set retextra=4 on next expiration 26 versions would be deleted. Having two mgmt classes differing only by mode will not give you two times 30 versions. The number of versions kept will be min(30,30) - again 30. Do not overcomplicate your policy. Create one class (or more) and use it. If you still want to have "full" backup on Sundays - I would use selective backup in Sunday's schedule and leave policy/classes unchanged. Again - is there actual need to resend all the data over the LAN? It is on the server already. Lets manage it better. If you can define the requirements in *business* terms only and prevent full/incremental/differential ideology to predefine the solution - this list can help you. TSM is very different from other backup products. And sometimes its "traditional" usage looks to me as driving a jet fighter on a highway with 100 km/h instead of flying with 1500 km/h over shorter route. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: 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
Re: Help Understanding Mgmt classes
Michael, The rules I described apply universally to backup objects with the same name owned by a given node in backup storage. With TDP products, in some cases, the backup objects are given different, unique names every time a backup occurs -- you must review the Install & User's Guide for the TDP you are using. For example, TDP v1 for Exchange creates unique names for every backup, so retention/expiration must be done manually; in v2 of this TDP, objects stored in backup storage are given the same name, so their retention/expiration becomes "automated" like for files backed up by the b/a-client -- and the management class rules, as I described, will apply. Hope this helps. - Original Message - From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 5:17 AM Subject: Re: Help Understanding Mgmt classes Hi Don, I'm not sure to understand your answer. By the way, thanks for your answer. I'm interested in this mailing and was not the originator. Our Backup solution is based on tdp for domino 1.1.2. Our tsm client is 4.2.1.20 based on Windows Nt4 server. here is our strategy: a full backup a week - keeping 5 version (management class=week) a full backup a month - keeping 13 version (management class=month) an incremental version a day - keeping 5 version (management class=daily) after reading your mail, I understand that having 3 MC for the same file will cause the retention to change after every backup when the MC is used. So for example: when week backup is finished, it will apply the MC for the file and when month backup is finished, it will change all retention on every file base on the new MC ? thanks Mike > ___ > Michael REGELIN > Inginieur Informatique - O.S.O. > Groupware & Messagerie > Centre des Technologies de l'Information (CTI) > Route des Acacias 82 > CP149 - 1211 Genhve 8 > Til. + 41 22 3274322 - Fax + 41 22 3275499 > Mailto:[EMAIL PROTECTED] > http://intraCTI.etat-ge.ch/services_complementaires/messagerie.html > __ > -Message d'origine- De : Don France (TSMnews) [mailto:[EMAIL PROTECTED]] Envoyi : vendredi, 3. mai 2002 03:39 @ : [EMAIL PROTECTED] Objet : Re: Help Understanding Mgmt classes 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
Re: Help Understanding Mgmt classes
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 > >
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 >
Re: Help Understanding Mgmt classes
Hi Don, I'm not sure to understand your answer. By the way, thanks for your answer. I'm interested in this mailing and was not the originator. Our Backup solution is based on tdp for domino 1.1.2. Our tsm client is 4.2.1.20 based on Windows Nt4 server. here is our strategy: a full backup a week - keeping 5 version (management class=week) a full backup a month - keeping 13 version (management class=month) an incremental version a day - keeping 5 version (management class=daily) after reading your mail, I understand that having 3 MC for the same file will cause the retention to change after every backup when the MC is used. So for example: when week backup is finished, it will apply the MC for the file and when month backup is finished, it will change all retention on every file base on the new MC ? thanks Mike > ___ > Michael REGELIN > Ingénieur Informatique - O.S.O. > Groupware & Messagerie > Centre des Technologies de l'Information (CTI) > Route des Acacias 82 > CP149 - 1211 Genève 8 > Tél. + 41 22 3274322 - Fax + 41 22 3275499 > Mailto:[EMAIL PROTECTED] > http://intraCTI.etat-ge.ch/services_complementaires/messagerie.html > __ > -Message d'origine- De : Don France (TSMnews) [mailto:[EMAIL PROTECTED]] Envoyé : vendredi, 3. mai 2002 03:39 À : [EMAIL PROTECTED] Objet : Re: Help Understanding Mgmt classes 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
Re: Help Understanding Mgmt classes
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
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
