Being able to have like a 'base' option set and then have others that reference that 'base'. For example at one client I have I created a generic WIN32 option set for all the NT servers. I then had to create option sets for 'special' servers that were, for example, running the TDP agents. I would COPY CLOPTSET WIN32 to the newname and then add in my Excludes for the SQL databases or Domino NSF databases that would normally be backed up via the TDP. Now when they started migrating to Win2k, that had more Excludes in the standard WIN32 option set, but instead of just having to update the 'base' WIN32 option set, I had to (try and) remember what all option sets I created from the 'base' WIN32 set to make sure that I added all the new Include/Excludes to them.
Maybe just being able to have line an INCLUDE CLOPTSET, or some other way to reference this 'base' option set would make life easier. Maybe someone could bring this up at the next SHARE conference?? Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Cascanette Sent: Wednesday, April 10, 2002 8:43 PM To: [EMAIL PROTECTED] Subject: Re: Client Option Sets I have placed all my include/exclude/exclude.archive all in the same dsm.opt file and I have had no problems with any of my clients even if the directory/file does not exist. Server 4.2.1.12 (Windows) Clients 4.2.1.20 Joe (or am I reading the message wrong?) -----Original Message----- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Wed 4/10/2002 3:45 PM To: [EMAIL PROTECTED] Cc: Subject: Re: Client Option Sets I suspect we mean the same thing, I just don't write in my native tongue very well -- Multiple client options sets where you define exclusions for specific things: One set with inclexcl for WINNT4 clients, a set with inclexcl for Oracle, one for MSSQL and if you had a WNNT server with Oracle, you just specify the WINNT and the Oracle for the client. I'm one of those sorts that likes to keep administration as simple as possible - only one place to look at the lists rather than 1500 dsm.opt files as we do at this location now. Just my thoughts with the wish that IBM/Tivoli is listening ;) -----Original Message----- From: Ptur Ey rsson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 2:27 PM To: [EMAIL PROTECTED] Subject: Re: Client Option Sets Yes i agree with you Dale. although i dont see it like that I would like to see a hierarchy in Client Option Sets. One Mother Client option for all, and then you can define it longer and in more details down the road. Kvedja/Regards Petur Eythorsson Taeknimadur/Technician IBM Certified Specialist - AIX Tivoli Storage Manager Certified Professional Microsoft Certified System Engineer [EMAIL PROTECTED] Nyherji Hf Simi TEL: +354-569-7700 Borgartun 37 105 Iceland URL: http://www.nyherji.is -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jolliff, Dale Sent: 10. apr l 2002 13:44 To: [EMAIL PROTECTED] Subject: Client Option Sets Is it just me, or would anyone else like to see the ability to attach multiple client option sets to a node? Why would it not be a good idea to be able to do this?
