Re: client option sets
On our windows clients here, I found that I needed to enclose all incl/exl commands in the cloptset with single quotes. Didn't have to for netware,vms, or tru64, but for some reason the windows clients wanted them. I'm not 100% sure if cloptset changes need to be followed by a restart of the client services, but I've always done it just to be safe. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 11/16/2004 12:04:57 PM I am implementing client optionset's on my server at this time and I ran an incremental backup yesterday evening after assigning a node to a client optionset but the include/exclude's that I specified were ignored. Do I have to restart my node's client or sched in order for such a change to take affect. I am pretty sure the syntax is correct because they worked fine when used in a local dsm.opt incl/excl file. I could always just restart the services on the windows 2000 client but I wanted to run it by the list to make sure that everything else looked fine instead of waiting for my backups to run again. R. (necessary information below) Option: INCLEXCL Sequence number: 22 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat.LOG Option: INCLEXCL Sequence number: 23 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat Option: INCLEXCL Sequence number: 24 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat.LOG Option: INCLEXCL Sequence number: 25 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat 11/15/2004 19:12:19 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:20 ANS1898I * Processed 5,500 files * 11/15/2004 19:12:22 ANS1898I * Processed 6,000 files * 11/15/2004 19:12:23 ANS1898I * Processed 6,500 files * 11/15/2004 19:12:24 ANS1898I * Processed 7,000 files * 11/15/2004 19:12:25 Retry # 1 Normal File-- 344,064 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT.LOG [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 8,192 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG [Sent] 11/15/2004 19:12:26 ANS1898I * Processed 7,500 files * 11/15/2004 19:12:27 ANS1898I * Processed 8,000 files * 11/15/2004 19:12:28 Retry # 1 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 ANS1228E Sending of object ' \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT' failed 11/15/2004 19:12:28 ANS4987E Error processing ' \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT': the object is in use by another process 11/15/2004 19:12:28 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Normal File-- 16,384 \\zinc\c$\Documents and Settings\backupexec.CORP\Cookies\index.dat [Sent] Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: client option sets
Agreed; here is what my DEFINE command looks like for a windows Exclude: define clientopt win2kserver inclexcl exclude *:\...\netscape*\...\cache\*seq=130 You don't have to restart the client service. You can also check it without waiting for your overnight backups: On the client machine, start the command line version of the client Enter: Q incl You will see a list of all the effective excludes; if a line is tagged server, the exclude was pushed from the server via cloptset; if it says dsm.opt, it came from the dsm.opt file. One warning: the output from q incl displays incl/exl sorted as they will match from top down, not bottpm up like the dsm.opt file (go figure...) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, November 16, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: Re: client option sets On our windows clients here, I found that I needed to enclose all incl/exl commands in the cloptset with single quotes. Didn't have to for netware,vms, or tru64, but for some reason the windows clients wanted them. I'm not 100% sure if cloptset changes need to be followed by a restart of the client services, but I've always done it just to be safe. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 11/16/2004 12:04:57 PM I am implementing client optionset's on my server at this time and I ran an incremental backup yesterday evening after assigning a node to a client optionset but the include/exclude's that I specified were ignored. Do I have to restart my node's client or sched in order for such a change to take affect. I am pretty sure the syntax is correct because they worked fine when used in a local dsm.opt incl/excl file. I could always just restart the services on the windows 2000 client but I wanted to run it by the list to make sure that everything else looked fine instead of waiting for my backups to run again. R. (necessary information below) Option: INCLEXCL Sequence number: 22 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat.LOG Option: INCLEXCL Sequence number: 23 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat Option: INCLEXCL Sequence number: 24 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat.LOG Option: INCLEXCL Sequence number: 25 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat 11/15/2004 19:12:19 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:20 ANS1898I * Processed 5,500 files * 11/15/2004 19:12:22 ANS1898I * Processed 6,000 files * 11/15/2004 19:12:23 ANS1898I * Processed 6,500 files * 11/15/2004 19:12:24 ANS1898I * Processed 7,000 files * 11/15/2004 19:12:25 Retry # 1 Normal File-- 344,064 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT.LOG [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 8,192 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG [Sent] 11/15/2004 19:12:26 ANS1898I * Processed 7,500 files * 11/15/2004 19:12:27 ANS1898I * Processed 8,000 files * 11/15/2004 19:12:28 Retry # 1 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 ANS1228E Sending of object ' \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT' failed 11/15/2004 19:12:28 ANS4987E Error processing ' \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT': the object is in use by another process 11/15/2004 19:12:28 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG
Re: client option sets
Include your file specification in double quotes, since it contains spaces. Guillaume -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of CORP Rick Willmore Sent: November 16, 2004 13:05 PM To: [EMAIL PROTECTED] Subject: client option sets I am implementing client optionset's on my server at this time and I ran an incremental backup yesterday evening after assigning a node to a client optionset but the include/exclude's that I specified were ignored. Do I have to restart my node's client or sched in order for such a change to take affect. I am pretty sure the syntax is correct because they worked fine when used in a local dsm.opt incl/excl file. I could always just restart the services on the windows 2000 client but I wanted to run it by the list to make sure that everything else looked fine instead of waiting for my backups to run again. R. (necessary information below) Option: INCLEXCL Sequence number: 22 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat.LOG Option: INCLEXCL Sequence number: 23 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat Option: INCLEXCL Sequence number: 24 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat.LOG Option: INCLEXCL Sequence number: 25 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat 11/15/2004 19:12:19 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:20 ANS1898I * Processed 5,500 files * 11/15/2004 19:12:22 ANS1898I * Processed 6,000 files * 11/15/2004 19:12:23 ANS1898I * Processed 6,500 files * 11/15/2004 19:12:24 ANS1898I * Processed 7,000 files * 11/15/2004 19:12:25 Retry # 1 Normal File-- 344,064 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT.LOG [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 8,192 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG [Sent] 11/15/2004 19:12:26 ANS1898I * Processed 7,500 files * 11/15/2004 19:12:27 ANS1898I * Processed 8,000 files * 11/15/2004 19:12:28 Retry # 1 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 ANS1228E Sending of object '\\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT' failed 11/15/2004 19:12:28 ANS4987E Error processing '\\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT': the object is in use by another process 11/15/2004 19:12:28 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 3 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 4 Normal File-- 1,024 \\zinc\c$\Documents and Settings\backupexec.CORP\ntuser.dat.LOG ** Unsuccessful ** 11/15/2004 19:12:28 Normal File--16,384 \\zinc\c$\Documents and Settings\backupexec.CORP\Cookies\index.dat [Sent]
Re: client option sets
I will go ahead and change all my lines in the client optionset I created to quote around each one (ALL 35 of them) but I did a check on the server per wanda (q incl) and I noticed that the Documents and settings exclusion looks like a match before I ever quoted anything. R. Incl All *\...\*.* Server Incl All *\...\*Server Incl SystemObject ALLServer Excl All C:\WINNT\system32\NtmsData\...\* Operating System Excl All C:\WINNT\system32\inetsrv\metabase.xml Operating System Excl All C:\WINNT\system32\inetsrv\metabase.bin Operating System Excl All C:\WINNT\system32\inetsrv\mbschema.xml Operating System Excl All C:\WINNT\System32\DTCLog\MSDTC.LOG Operating System Excl All C:\WINNT\system32\config\system.log Operating System Excl All C:\WINNT\system32\config\system.alt Operating System Excl All C:\WINNT\system32\config\system Operating System Excl All C:\WINNT\system32\config\software.log Operating System Excl All C:\WINNT\system32\config\software Operating System Excl All C:\WINNT\system32\config\security.log Operating System Excl All C:\WINNT\system32\config\security Operating System Excl All C:\WINNT\system32\config\sam.log Operating System Excl All C:\WINNT\system32\config\sam Operating System Excl All C:\WINNT\system32\config\default.log Operating System Excl All C:\WINNT\system32\config\default Operating System Excl All C:\WINNT\schedlgu.txt Operating System Excl All C:\WINNT\registration\*.clbOperating System Excl All C:\WINNT\netlogon.chg Operating System Excl All C:\WINNT\debug\* Operating System Excl All C:\WINNT\csc\...\* Operating System Excl All C:\DOCUME~1\RWILLM~1\LOCALS~1\Temp\1\...\* Operating System Excl All C:\Documents and Settings\rwillmore\...\index.dat Operating Syste m Excl All C:\adsm.sys\...\* Operating System Excl All *\Pagefile.sys Operating System Excl All *\hiberfil.sys Operating System Excl All *\...\*.crmlog Operating System No DFS include/exclude statements defined. tsm -Original Message- From: CORP Rick Willmore Sent: Tuesday, November 16, 2004 10:05 AM To: 'ADSM: Dist Stor Manager' Subject: client option sets I am implementing client optionset's on my server at this time and I ran an incremental backup yesterday evening after assigning a node to a client optionset but the include/exclude's that I specified were ignored. Do I have to restart my node's client or sched in order for such a change to take affect. I am pretty sure the syntax is correct because they worked fine when used in a local dsm.opt incl/excl file. I could always just restart the services on the windows 2000 client but I wanted to run it by the list to make sure that everything else looked fine instead of waiting for my backups to run again. R. (necessary information below) Option: INCLEXCL Sequence number: 22 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat.LOG Option: INCLEXCL Sequence number: 23 Override: No Option Value: exclude *:\documents and settings\...\ntuser.dat Option: INCLEXCL Sequence number: 24 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat.LOG Option: INCLEXCL Sequence number: 25 Override: No Option Value: exclude *:\documents and settings\...\usrclass.dat 11/15/2004 19:12:19 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:20 ANS1898I * Processed 5,500 files * 11/15/2004 19:12:22 ANS1898I * Processed 6,000 files * 11/15/2004 19:12:23 ANS1898I * Processed 6,500 files * 11/15/2004 19:12:24 ANS1898I * Processed 7,000 files * 11/15/2004 19:12:25 Retry # 1 Normal File-- 344,064 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\NTUSER.DAT.LOG [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 8,192 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat [Sent] 11/15/2004 19:12:25 Retry # 1 Normal File-- 1,024 \\zinc\c$\Documents and Settings\appsdev\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG [Sent] 11/15/2004 19:12:26 ANS1898I * Processed 7,500 files * 11/15/2004 19:12:27 ANS1898I * Processed 8,000 files * 11/15/2004 19:12:28 Retry # 1 Normal File-- 270,336 \\zinc\c$\Documents and Settings\backupexec.CORP\NTUSER.DAT ** Unsuccessful ** 11/15/2004 19:12:28 Retry # 2
Re: client option sets
On Nov 16, 2004, at 1:48 PM, CORP Rick Willmore wrote: I will go ahead and change all my lines in the client optionset I created to quote around each one (ALL 35 of them) but I did a check on the server per wanda (q incl) and I noticed that the Documents and settings exclusion looks like a match before I ever quoted anything. Rick - Your clientopts do specify Override: No which may be a contributing factor. Always do 'dsmc q inclexcl' as Wanda suggests, on a participating client to compile the Include-Excludes to assure that you are getting the combinatorial result you expect, before backups run. Richard Sims
Re: client option sets
In TSM V5.3 (will be GA next month ?) there is a:
Preview command displays files that would be included, exclude, or both
---Preview--Backup|Archive--filespec--filter--{All/incl/excl}---filename--console--{yes/no,
traverse}---
Hoa.
Richard Sims [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
11/16/2004 01:29 PM
Please respond to
ADSM: Dist Stor Manager
To
[EMAIL PROTECTED]
cc
Subject
Re: client option sets
On Nov 16, 2004, at 1:48 PM, CORP Rick Willmore wrote:
I will go ahead and change all my lines in the client optionset I
created to quote around each one (ALL 35 of them) but I did a check on
the server per wanda (q incl) and I noticed that the Documents and
settings exclusion looks like a match before I ever quoted anything.
Rick - Your clientopts do specify Override: No
which may be a contributing factor. Always do 'dsmc q inclexcl'
as
Wanda suggests, on a participating client to compile the
Include-Excludes
to assure that you are getting the combinatorial result you expect,
before
backups run.
Richard Sims
Re: Client Option Sets vs. Option Files
hi, how many client are you handlig ? thanks, goran - Original Message - From: Prather, Wanda [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 11:35 PM Subject: Re: Client Option Sets vs. Option Files We use about 5 different cloptsets. One for macs, one for Win2K, one for Win2K3 servers, one for Windows desktops, one for AIX servers, etc. We put in the cloptset things that apply to all Win2K servers, (or macs, or AIX, etc.) and put in dsm.opt anything that only applies to that particular client. That seems to be the most logical thing for us. That way nobody has to remember all the annoying stuff that applies to EVERY windows system, 'cause it's all in one place. And we don't have multiple people putting a zillion machine-specific things into the cloptset that we might trip up on later. See more answers below each question: 1) Can we use just one large option set that encompasses all possible excludes and includes (since our includes are usually directory specific)? all POSSIBLE? Not sure what that would mean!! :) Duuno, probably. I haven't tried putting AIX excludes into a cloptset for a Windows sytem, for example, but I suspect it would work OK. a) If so, does that slow down backups being a larger option set file? Dunno. Our largest CLOPTSET is 55 lines, and I haven't seen any noticeable slowdown. Cloptsets are pretty harmless, have never run into any real gotcha's (except for the lack of an editor!) b) Does the server read it each time for each client that logs on? Dunno, never wondered. Probably, 'cause- you can do a q inclexcl even if you aren't doing a backup. I suspect the cloptset is small compared to the list of active backups that gets sent down for a normal incremental! c) Is it a problem if multiple servers log on at the same time? Nope, works just like you want it to. 2) Can we use both option sets and option files, where we can have the specifics added to the option file and the generic in the option set? Yep, that's what we do. It's a little weird - for options other than INCLUDE/EXCLUDE, you can specify whether the server option overrides the local dsm.opt. But for INCLUDE/EXCLUDE, ALL the includes and excludes are merged together. So you could have conflicts. So after you set up your CLOPTSET, be sure you go to a client and do q inclexcl to make sure you are getting the results you want. (We don't have that situation, since we leave in dsm.opt only the things that apply to the specific client.) Hope that helps! Wanda Prather I/O, I/O, It's all about I/O -(me)
Re: Client Option Sets vs. Option Files
Hi All! Would anyone be willing to provide examples of your client option sets? I know that you will probably have certain parameters that other companies wouldn't need, but as a starting point... Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] Prather, Wanda [EMAIL PROTECTED] UAPL.EDU To Sent by: ADSM: [EMAIL PROTECTED] Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Client Option Sets vs. Option Files 07/13/2004 05:35 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU We use about 5 different cloptsets. One for macs, one for Win2K, one for Win2K3 servers, one for Windows desktops, one for AIX servers, etc. We put in the cloptset things that apply to all Win2K servers, (or macs, or AIX, etc.) and put in dsm.opt anything that only applies to that particular client. That seems to be the most logical thing for us. That way nobody has to remember all the annoying stuff that applies to EVERY windows system, 'cause it's all in one place. And we don't have multiple people putting a zillion machine-specific things into the cloptset that we might trip up on later. See more answers below each question: 1) Can we use just one large option set that encompasses all possible excludes and includes (since our includes are usually directory specific)? all POSSIBLE? Not sure what that would mean!! :) Duuno, probably. I haven't tried putting AIX excludes into a cloptset for a Windows sytem, for example, but I suspect it would work OK. a) If so, does that slow down backups being a larger option set file? Dunno. Our largest CLOPTSET is 55 lines, and I haven't seen any noticeable slowdown. Cloptsets are pretty harmless, have never run into any real gotcha's (except for the lack of an editor!) b) Does the server read it each time for each client that logs on? Dunno, never wondered. Probably, 'cause- you can do a q inclexcl even if you aren't doing a backup. I suspect the cloptset is small compared to the list of active backups that gets sent down for a normal incremental! c) Is it a problem if multiple servers log on at the same time? Nope, works just like you want it to. 2) Can we use both option sets and option files, where we can have the specifics added to the option file and the generic in the option set? Yep, that's what we do. It's a little weird - for options other than INCLUDE/EXCLUDE, you can specify whether the server option overrides the local dsm.opt. But for INCLUDE/EXCLUDE, ALL the includes and excludes are merged together. So you could have conflicts. So after you set up your CLOPTSET, be sure you go to a client and do q inclexcl to make sure you are getting the results you want. (We don't have that situation, since we leave in dsm.opt only the things that apply to the specific client.) Hope that helps! Wanda Prather I/O, I/O, It's all about I/O -(me)
Re: Client Option Sets vs. Option Files
Sure. Here's a sample for Win2K servers; customize it to be appropriate to your environment; I'm no Windows expert! define cloptset win2kserver description=Backup options for TSM Win2K Servers define clientopt win2kserver compression oFF define clientopt win2kserver maxcmdretries 99 define clientopt win2kserver queryschedperiod 24 define clientopt win2kserver retryperiod 20 define clientopt win2kserver slowincr no define clientopt win2kserver subdir yes define clientopt win2kserver subfilecaches 200 define clientopt win2kserver txnbytelimit 25600 define clientopt win2kserver inclexcl exclude *:\DOCUMENTS\...\INDEX.DAT seq=15 define clientopt win2kserver inclexcl exclude *:\IBMBIO.COM seq=46 define clientopt win2kserver inclexcl exclude *:\IBMDOS.COM seq=47 define clientopt win2kserver inclexcl exclude '*:\...\ea data. sf' seq=50 define clientopt win2kserver inclexcl exclude *:\...\*.swp seq=55 define clientopt win2kserver inclexcl exclude *:\...\*.csm seq=65 define clientopt win2kserver inclexcl exclude *:\...\*.par seq=75 define clientopt win2kserver inclexcl exclude '*:\microsoft uam volume\*' seq=80 define clientopt win2kserver inclexcl exclude '*:\microsoft uam volume\...\*' seq=81 define clientopt win2kserver inclexcl exclude *:\...\system32\config\...\*seq=86 define clientopt win2kserver inclexcl exclude *:\Windows\spool\printers\* seq=87 define clientopt win2kserver inclexcl exclude.dir *:\...\ntfrs\jet seq=90 define clientopt win2kserver inclexcl exclude.dir *:\...\ntds seq=95 define clientopt win2kserver inclexcl exclude.dir '*:\System Volume Information' seq=100 define clientopt win2kserver inclexcl exclude.dir '*:\...\Temporary Internet Files' seq=105 define clientopt win2kserver inclexcl exclude *:\RECYCLE?\...\* seq=110 define clientopt win2kserver inclexcl exclude.dir *:\RECYCLED seq=111 define clientopt win2kserver inclexcl exclude.dir *:\RECYCLER seq=112 define clientopt win2kserver inclexcl exclude *:\...\TEMP\...\* seq=115 define clientopt win2kserver inclexcl exclude *:\...\tmp\...\* seq=120 define clientopt win2kserver inclexcl exclude *:\...\*.tmp seq=125 define clientopt win2kserver inclexcl exclude.dir *:\TEMP seq=126 define clientopt win2kserver inclexcl exclude *:\...\netscape*\...\cache\*seq=130 define clientopt win2kserver inclexcl exclude.dir *:\...\mozilla\...\cache seq=131 define clientopt win2kserver inclexcl exclude *:\...\netscape\users\...\news\...\*seq=135 define clientopt win2kserver inclexcl exclude.dir *:\...\History.IE5 seq=140 define clientopt win2kserver inclexcl exclude.dir *:\...\MS\SMS seq=141 define clientopt win2kserver inclexcl exclude.dir *:\...\Catalog.wci seq=142 define clientopt win2kserver inclexcl exclude *:\...\PointCast*\...\* seq=145 define clientopt win2kserver inclexcl exclude *:\...\baclient\...\cache\...\* seq=150 define clientopt win2kserver inclexcl exclude '*:\...\Documents and Settings\SMSCliSvcAcct*' seq=153 define clientopt win2kserver inclexcl exclude '*:\...\Documents and Settings\SMSCliToknAcct*' seq=154 define clientopt win2kserver inclexcl exclude *:\WINNT\MS\SMS\LOGS\...\* seq=155 define clientopt win2kserver inclexcl exclude *:\WINNT\MS\SMS\clicomp\...\complete\...\*seq=157 define clientopt win2kserver inclexcl exclude '*:\...\Documents and Settings\...\Recent\...\*' seq=160 define clientopt win2kserver inclexcl exclude *:\...\WINNT\system32\Perflib*.dat seq=170 define clientopt win2kserver inclexcl exclude *:\...\ntuser.dat.LOG seq=171 define clientopt win2kserver inclexcl exclude *:\...\UsrClass.dat.LOG seq=172 define clientopt win2kserver inclexcl exclude.compression *:\...\*.zip seq=190 define clientopt win2kserver inclexcl exclude.compression *:\...\*.jpg seq=191 define clientopt win2kserver inclexcl exclude.compression *:\...\*.tif seq=192 define clientopt win2kserver inclexcl exclude.compression *:\...\*.gif seq=193 define clientopt win2kserver inclexcl exclude.compression *:\...\*.cgm seq=194 define clientopt win2kserver inclexcl include *:\...\dsmsched.log MGTC_CHANGING seq=200 define clientopt win2kserver inclexcl include *:\...\dsmerror.log MGTC_CHANGING seq=202
Re: Client Option Sets vs. Option Files
We use about 5 different cloptsets. One for macs, one for Win2K, one for Win2K3 servers, one for Windows desktops, one for AIX servers, etc. We put in the cloptset things that apply to all Win2K servers, (or macs, or AIX, etc.) and put in dsm.opt anything that only applies to that particular client. That seems to be the most logical thing for us. That way nobody has to remember all the annoying stuff that applies to EVERY windows system, 'cause it's all in one place. And we don't have multiple people putting a zillion machine-specific things into the cloptset that we might trip up on later. See more answers below each question: 1) Can we use just one large option set that encompasses all possible excludes and includes (since our includes are usually directory specific)? all POSSIBLE? Not sure what that would mean!! :) Duuno, probably. I haven't tried putting AIX excludes into a cloptset for a Windows sytem, for example, but I suspect it would work OK. a) If so, does that slow down backups being a larger option set file? Dunno. Our largest CLOPTSET is 55 lines, and I haven't seen any noticeable slowdown. Cloptsets are pretty harmless, have never run into any real gotcha's (except for the lack of an editor!) b) Does the server read it each time for each client that logs on? Dunno, never wondered. Probably, 'cause- you can do a q inclexcl even if you aren't doing a backup. I suspect the cloptset is small compared to the list of active backups that gets sent down for a normal incremental! c) Is it a problem if multiple servers log on at the same time? Nope, works just like you want it to. 2) Can we use both option sets and option files, where we can have the specifics added to the option file and the generic in the option set? Yep, that's what we do. It's a little weird - for options other than INCLUDE/EXCLUDE, you can specify whether the server option overrides the local dsm.opt. But for INCLUDE/EXCLUDE, ALL the includes and excludes are merged together. So you could have conflicts. So after you set up your CLOPTSET, be sure you go to a client and do q inclexcl to make sure you are getting the results you want. (We don't have that situation, since we leave in dsm.opt only the things that apply to the specific client.) Hope that helps! Wanda Prather I/O, I/O, It's all about I/O -(me)
Re: Client Option Sets
BOOKs is obsolete, I think.. Back in the V2 client, you could put BOOKS in your dsm.opt file and point to the BOOKMANAGER (I think) files for the ADSM manuals so that ADSM would know where to find them when the user clicked HELP. I don't think it applies to current clients, you don't need it - the GUI has WIndows-style HELP now, and the HTML versions also get installed in the program group. -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Friday, April 26, 2002 9:13 AM To: [EMAIL PROTECTED] Subject: Client Option Sets I'm setting up a new client option set and noticed that there are some options available that I can't find documentation for... BOOKS and DSMCDEFAULTCOMMAND I searched the knowledgeable and didn't see anything that jumped right out and slapped me - Anyone have a pointer to some explanations of this?
Re: Client Option Sets
Hi, I had previosly workaround for that, managing hierarchy of clopsets outsided of TSM (ITSM?) (making all changes in flat files hierarchy and updating cloptsets via scripts). This worked but was for my small installation of 100 clients rather complex, so I abandoned it. So, you are not alone. regards Juraj Salak -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 3:44 PM 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?
Re: Client Option Sets
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 37105 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?
Re: Client Option Sets
Yes, I have wanted this numerous times. _ William Mansfield Senior Consultant Solution Technology, Inc Jolliff, Dale [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 04/10/2002 08:44 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: 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?
Re: Client Option Sets
Yes i agree with you Dale. although i don´t 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 37105 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?
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: Pétur 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 don´t 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 37105 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?
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: Pétur 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 don´t 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 37105 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?
