Backup Central

I created a new Domain Name on a TSM6.2.3 server, no problem.

I then assumed (that's bad) that deleting Option Sets within that domain would be isolated to that domain.

However, the Option sets were removed from the "server", not just that domain.

Is that normal?

I see that Mgmt Classes are unique to the Domain and would think that Option sets would also be unique to the Domain.

I've recreated them, but curious if this is normal or a bug in 6.2.3?

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information Technology Services
Harold.Vandeventer < at > da.ks.gov<mailto:Dane.Woodring < at > da.ks.gov>
(785) 296-0631

Hi Harold,

Client Options Sets are server-wide and not related to Policy Domains. It has always been like that. It's'not a bug.

When you define (or delete) a Client Options Set, there is no référence to a Policy Domain.


------Message d'origine------
De: Vandeventer, Harold [BS]
Expéditeur : ADSM: Dist Stor Manager
À: ADSM-L < at > VM.MARIST.EDU
Répondre à: ADSM: Dist Stor Manager
Objet: [ADSM-L] Policy Option Sets relation to Domains
Envoyé: 15 déc. 2011 19:50

I created a new Domain Name on a TSM6.2.3 server, no problem.

I then assumed (that's bad) that deleting Option Sets within that domain would be isolated to that domain.

However, the Option sets were removed from the "server", not just that domain.

Is that normal?

I see that Mgmt Classes are unique to the Domain and would think that Option sets would also be unique to the Domain.

I've recreated them, but curious if this is normal or a bug in 6.2.3?

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information Technology Services
Harold.Vandeventer < at > da.ks.gov<mailto:Dane.Woodring < at > da.ks.gov>
(785) 296-0631


--
Best regards / Cordialement / مع تحياتي
Erwann SIMON

The "Parts of a Policy" in the Admin Guide manual illustrates what elements constitute a Policy Domain, which is involved in the governance of data. The mechanical elements of data handling and the housing of client options are external to that, as they are not specifically related to enterprise policies.

Richard Sims

did you specify a domainname when creating the optionset?.... I bet you didn't.


On 15 dec. 2011, at 19:50, Vandeventer, Harold [BS] wrote:

I created a new Domain Name on a TSM6.2.3 server, no problem.

I then assumed (that's bad) that deleting Option Sets within that domain would be isolated to that domain.

However, the Option sets were removed from the "server", not just that domain.

Is that normal?

I see that Mgmt Classes are unique to the Domain and would think that Option sets would also be unique to the Domain.

I've recreated them, but curious if this is normal or a bug in 6.2.3?

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information Technology Services
Harold.Vandeventer < at > da.ks.gov<mailto:Dane.Woodring < at > da.ks.gov>
(785) 296-0631

--
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post < at > plcs.nl
+31 6 248 21 622