Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Best\s+practice\s+for\s+Policy\s+Domains\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Best\s+practice\s+for\s+Policy\s+Domains\s*$/: 9 ]

Total 9 documents matching your query.

1. [ADSM-L] Best practice for Policy Domains (score: 1): Author: Shannon Bach <SBach AT MGE DOT COM>; Date: Thu, 5 Jun 2008 14:19:50 -0500; I have always been told that it is easiest to maintain as few Policy Domains as you can get away with. Currently I have a standard Policy Domain which is the Default for all Windows boxes, a Policy D; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00058.html (12,467 bytes)
2. [ADSM-L] Best practice for Policy Domains (score: 1): Author: EVILUTION <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Thu, 5 Jun 2008 15:53:32 -0400; Why not use the managment class to set retention? +-- +--; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00060.html (11,507 bytes)
3. Re: [ADSM-L] Best practice for Policy Domains (score: 1): Author: Shannon Bach <SBach AT MGE DOT COM>; Date: Thu, 5 Jun 2008 15:09:55 -0500; By using the Policy Domain as a retention bucket the TSM Admins are able to have a better control of what each clients data actually is retained for. By using the management classes we can only find; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00062.html (12,247 bytes)
4. [ADSM-L] Best practice for Policy Domains (score: 1): Author: EVILUTION <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Thu, 5 Jun 2008 16:40:25 -0400; Hmmm I'm not sure about that..... I have only a standard active domain. I do have serveral mgmt classes for various types of data and various retention requiresments..... A default for 99% of the nod; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00064.html (12,281 bytes)
5. Re: [ADSM-L] Best practice for Policy Domains (score: 1): Author: Wanda Prather <wprather AT JASI DOT COM>; Date: Fri, 6 Jun 2008 11:18:50 -0400; I think "best practice" is whatever gives you the most control and consistent results, and it will vary depending on your site conditions. It is extremely difficult to figure out after the fact (say; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00082.html (14,033 bytes)
6. [ADSM-L] Best practice for Policy Domains (score: 1): Author: EVILUTION <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Fri, 6 Jun 2008 11:30:09 -0400; Okay.... I can see how that would help keep tabs on whats going where. Though it does seem odd that you would need more than a handful of retentions especially defaults. +-- +--; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00084.html (11,675 bytes)
7. Re: [ADSM-L] Best practice for Policy Domains (score: 1): Author: Cory Heikel <cheikel AT HMC.PSU DOT EDU>; Date: Fri, 6 Jun 2008 11:52:34 -0400; Our general rule here is each node gets its own policy domain, that way I rarely have to deal with any includes for management classes. I think "best practice" is whatever gives you the most control; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00085.html (14,264 bytes)
8. Re: [ADSM-L] Best practice for Policy Domains (score: 1): Author: Norman Bloch <Norman_Bloch AT READERSDIGEST.TM DOT FR>; Date: Wed, 18 Jun 2008 17:48:10 +0200; I remember I read many years ago in the manual : a Policy Domain is a logical grouping of nodes. Rather than splitting between OS, I would make Policy Domains for File servers, Application servers, M; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00189.html (13,236 bytes)
9. Re: [ADSM-L] Best practice for Policy Domains (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Wed, 18 Jun 2008 10:00:44 -0600; I teach our Level 1 students that having fewer domains rather than more makes more sense. Further, I suggest a separate domain for systems that have vastly different retention policies for most if no; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-06/msg00190.html (14,857 bytes)

Current List: 1 - 9
Page: [1]