I have a domain DUMMY on my 6 machines, with a single client DUMMY. To transfer an optionset from N3 to N6, I "exp no dummy do=dummy tos=n6 replacedefs=y". That copies whatever optionset is on N3 to N6.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Rhodes Sent: Thursday, January 14, 2010 12:58 PM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Keeping mgt classes in sync across multiple TSM servers We are now up to 6 primary TSM instances (as opposed to special purpose instances). We try and keep the policy sets setup the same so we can move nodes between them as needed. This wasn't bad when there was only a couple instances, but it's getting more of a issue with 6 instances. For example, I just created a 3mo archive class on one instance . . . and did it 5 more times on other instances. (Yes . . the CLI and scripts are your friends!) q) If you keep the domains/policysets/mgtclasses in sync across multiple TSM instances, How do you do it? There isn't some feature to sync these across multiple instances? Thanks Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
