|
Re: queryschedperiod
2004-10-07 04:22:20
Andrew,
The trace also says it should be 12 hours:
10/07/2004 10:18:12.585 : procopts.cpp (13794): SrvCanOvrRde(Y)
Src(0x01=File ) postschedulecmd /local/domino.sh start
10/07/2004 10:18:12.585 : procopts.cpp (13794): SrvCanOvrRde(Y)
Src(00=Default) prenschedulecmd
10/07/2004 10:18:12.585 : procopts.cpp (13794): SrvCanOvrRde(Y)
Src(0x01=File ) preschedulecmd /local/domino.sh stop_backup
10/07/2004 10:18:12.585 : procopts.cpp (13794): SrvCanOvrRde(Y)
Src(0x01=File ) queryschedperiod 12
10/07/2004 10:18:12.585 : procopts.cpp (13794): SrvCanOvrRde(Y)
Src(00=Default) retryperiod 20
What I always find confusing is the difference between the dsm.sys and the
dsm.opt files.
I always use the dsm.sys files for configuring, but it seems the TRACEFILE
option is only
recognized if you put it in the dsm.opt file...
Still, the dsmsched.log show 4 hours:
10/07/2004 10:18:12 Session established with server SERVER1: Linux/i386
10/07/2004 10:18:12 Server Version 5, Release 1, Level 8.3
10/07/2004 10:18:12 Server date/time: 10/07/2004 10:18:15 Last access:
10/07/2004 10:12:00
10/07/2004 10:18:12 --- SCHEDULEREC QUERY BEGIN
10/07/2004 10:18:12 --- SCHEDULEREC QUERY END
10/07/2004 10:18:12 Next operation scheduled:
10/07/2004 10:18:12
------------------------------------------------------------
10/07/2004 10:18:12 Schedule Name: LOTUSNOTES
10/07/2004 10:18:12 Action: Incremental
10/07/2004 10:18:12 Objects:
10/07/2004 10:18:12 Options:
10/07/2004 10:18:12 Server Window Start: 21:05:00 on 10/07/2004
10/07/2004 10:18:12
------------------------------------------------------------
10/07/2004 10:18:12 Schedule will be refreshed in 4 hours.
10/07/2004 10:21:59
Regards and thanks for the time,
Geert
Andrew Raibeck <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/10/2004 18:57
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: queryschedperiod
Try adding to your dsm.opt file:
TRACEFLAGS OPTIONS
TRACEFILE trace.txm
Then restart the scheduler. Wait a moment, then stop the scheduler. Review
the trace.tsm file and look for "queryschedperiod". What does it show?
What does this output show:
dsmc q opt "que*"
Would hurt to also run:
dsmc q systemi
then review the resulting dsminfo.txt file, particulary the dsm.sys and
dsm.opt file contents that are dumped into dsminfo.txt.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/06/2004
09:11:46:
> Richard,
>
> Yes, I restarted the scheduler after each change. So this should not be
> the problem.
>
> I also checked the server settings (q opt and q clopt) but did not find
> any clues.
>
> I admit it is only a "beauty" problem...
>
> Regards,
>
> Geert
>
> tsm: SERVER1>q opt
> Session established with server SERVER1: Linux/i386
> Server Version 5, Release 1, Level 8.3
> Server date/time: 10/06/2004 18:09:22 Last access: 10/06/2004
18:05:47
>
>
> Server Option Option Setting Server Option Option
> Setting
> ----------------- -------------------- -----------------
> --------------------
> CommTimeOut 600 IdleTimeOut 15
> BufPoolSize 2048 LogPoolSize 512
> DateFormat 1 (mm/dd/yyyy) TimeFormat 1
> (hh:mm:ss)
> NumberFormat 1 (1,000.00) MessageFormat 1
> Language en_US Alias Halt HALT
> MaxSessions 25 ExpInterval 0
> ExpQuiet No EventServer Yes
> MirrorRead DB Normal MirrorRead LOG Normal
> MirrorWrite DB Sequential MirrorWrite LOG Parallel
> VolumeHistory /tivoli/configurati- Devconfig
> /tivoli/configurati-
> on/volhistory.tsm on/devconfig.tsm
> TxnGroupMax 256 MoveBatchSize 40
> MoveSizeThresh 500 StatusMsgCnt 10
> RestoreInterval 1,440 UseLargeBuffers Yes
> DisableScheds No NOBUFPREfetch No
> AuditStorage Yes REQSYSauthoutfile Yes
> SELFTUNEBUFpools- Yes SELFTUNETXNsize Yes
> ize
> DBPAGEShadow No DBPAGESHADOWFile
> dbpgshdw.bdt
> QueryAuth None LogWarnFullPerCe- 90
> nt
> ThroughPutDataTh- 0 ThroughPutTimeTh- 0
> reshold reshold
> NOPREEMPT ( No ) Resource Timeout 60
> TEC UTF8 Events No
> TCPPort 1500 HTTPPort 1580
> HTTPSPort 1543 TCPWindowsize 0
> TCPBufsize 16384 TCPNoDelay Yes
> CommMethod TCPIP CommMethod SNMP
> MsgInterval 1 ShmPort 0
> FileExit FileTextExit
> UserExit AcsAccessId
> AcsTimeoutX 1 AcsLockDrive No
> AcsQuickInit No SNMPSubagentPort 1521
> SNMPSubagentHost 127.0.0.1 SNMPHeartBeatInt 5
> TECHost TECPort 0
> UNIQUETECevents No UNIQUETDPTECeven- No
> ts
> SHAREDLIBIDLE No 3494Shared No
> Enable3590Library No
>
>
> tsm: SERVER1>q clopt
> Session established with server SERVER1: Linux/i386
> Server Version 5, Release 1, Level 8.3
> Server date/time: 10/06/2004 17:52:52 Last access: 10/06/2004
17:27:19
>
>
> UNIX ADMIN
>
> Option Sequence Override Option Value
> number
> ------------------------- -------- --------
> ----------------------------------------
> INCLEXCL 100 Yes exclude.dir
/proc
> INCLEXCL 101 Yes exclude.dir /tmp
> INCLEXCL 102 Yes exclude.dir
> '/.../lost+found'
> INCLEXCL 103 Yes exclude.dir
> '/var/log'
> INCLEXCL 104 Yes exclude.dir
> '/var/run'
> INCLEXCL 105 Yes exclude.dir
> '/var/lock'
> INCLEXCL 106 Yes exclude.dir
> '/var/cache'
> INCLEXCL 107 Yes exclude.dir
'/mnt'
> INCLEXCL 108 Yes exclude
> '/.../*.log'
> INCLEXCL 120 Yes exclude
> /opt/tivoli/tsm/.../*.dsm
> INCLEXCL 130 Yes exclude.dir
> '/ARCHIVE'
> MEMORYEFFICIENTBACKUP 0 No yes
> QUIET 0 No yes
> SUBDIR 0 No yes
>
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/10/2004
> 13:49:57:
>
> > On Oct 6, 2004, at 7:27 AM, Geert De Pecker wrote:
> >
> > > Hi all,
> > >
> > > I checked about everything I can think of, but do not succeed in
> > > changing
> > > the queryperiod. If I understand correctly, the "queryschedperiod
12"
> > > in
> > > the dsm.sys file should do the job, but it always reverts to 4
hours.
> >
> > Your posting doesn't tell us if you restarted the scheduler after
> > making the
> > options file change.
> >
> > Note also that the client manual says:
> > Your administrator can also set this option. If your
administrator
> > specifies a value for this option, that value overrides the value
> > set in your client options file after your client node
successfully
> > contacts the server.
> > This is to say that the same-named option can be Set in the TSM
server.
> >
> > Richard Sims
|
|
|
