Already scheduled for it, and planning on posing my question there if I
don't have a solution in place by then. Thanks!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
William Boyer
Sent: Tuesday, October 11, 2005 11:39 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Fw: Configuring JBB
Doesn't really apply to helping you out now, but there's an up coming
Tivoli support exchange on JBB. Check here:
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=D600&u
id=swg21219456&loc=en_US&cs=UTF-8&lang=all&rss=ct663tivoli
Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bell, Charles (Chip)
Sent: Tuesday, October 11, 2005 12:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Fw: Configuring JBB
The journal daemon appears to be starting correctly interactively, and
will not stay up as a service.
The list of volumes/drives to monitor was generated by the setup wizard.
In the ini file, I uncommented these options...
PreserveDBOnExit=1
DeferFsMonStart=1
DeferRetryInterval=30
logFsErrors=0
...and afterward was unable to start the journaling service. As a matter
of fact I tried all of that before starting jbb
interactively.
I opened a PMR recently, which has since been closed, and instead of
helping (well, in hindsight, it did help), they pointed me to
documentation, which I was already aware of. While I did learn some
things new, the problem still exists, and I'm trying not to
throw my hands up. The node in question is holding onto a tape drive for
20+ hours per backup because of the file inspection it has
to do, which is why I want to get JBB to work. Please help! Thanks for
the reply!
Chip Bell
Systems Analyst I
IBM Tivoli Certified Deployment Professional (ITSM 5.2) Siemens Health
Services Birmingham, AL charles.bell AT bhsala DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Pete Tanenhaus
Sent: Monday, October 10, 2005 9:41 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Fw: Configuring JBB
Are you saying the journal daemon starts correctly interactively but
crashes when started as a service ?
Was the list of drives/mounted volumes to monitored generated by the
setup wizard or did you manually edit the journal config file ?
I also wasn't clear from your append if manually editing the config file
solved the problem of the journal service crashing and if
you still had questions as to why some of the journals weren't coming
online.
I tried pasting the list in your append into my own config file but it
appears that there are newline characters after each line so
only the first line was recognized (the others were ignored).
When I removed the newline characters (that is placed all the
drive/mounted volume specifications on the same line as the
JournalFileSystems stanza) everything seemed to work (although of course
only journals for drives defined to my machine came
online).
In neither case did the journal daemon crash, either when started
interactively or when started as a service.
If you are stilling having problems getting it to work please elaborate
on what isn't working (service is crashing, journal don't
come online when you think they should, etc.) and I will try to work
thru the problems with you.
Pete Tanenhaus
Tivoli Storage Manager Client Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213
"Those who refuse to challenge authority are condemned to conform to it"
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
10/10/2005 10:11 PM --------------------------- Please respond to "ADSM:
Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Configuring JBB
Help! This is a nightmare...
Client Win 2K3, v5.3.0.0
Server AIX 5.2, v5.3.1.2
Having trouble configuring journal-based backups for client. This
particular client became candidate for JBB, being that it has
around 25 million files to inspect, the majority of them being tiny.
That's just part of the dilemma. Using the GUI, I configured
JBB, but the services will not start, and generates the following error
in the Windows App Log..." Faulting application tsmjbbd.exe,
version 5.3.0.0, faulting module unknown, version 0.0.0.0, fault address
0x00000000." Well, that tells me jack, but digging around,
I only found one reference to this problem, saying that something may be
incorrect in the jbb.ini file, which I am copying and
pasting here. I did make some changes to it to reflect the fact that I
don't want the journal database to be deleted if the client
machine is rebooted. I started the JBB executable in interactive mode,
and it opened journals for all drives and mount points (out
of 30+) but a handful. Why? Here is the tsmjbbd.ini output...
;***********************************************************************
****
; Tivoli Storage Manager - Version 5, Release 2, Level 0
; Journal Service Sample Configuration File
; (C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved
;***********************************************************************
****
;
;
; JournalSettings - General Journal Service Settings
;
; Tracefile - jbb process tracefile
; Traceflags - space delimited set of traceflags
; TestFlags - space delimited set of testflags
; NlsRepos - nls message repository, default is dscameng.txt
; Errorlog - jbb process errorlog, default is jbberror.log
;
;
; Journaldir - Directory where journal database files are stored and
; written.
;
; Default is the Journal Service install directory.
;
; By default this setting applies to all journaled
; file systems but may be overridden via an override
; stanza for each journal file system.
;
; If the default value is a fully qualified path
; (for example c:\tsmjournal) all journal db files
; will be written to the specified directory.
;
; If the default value does not specifiy a drive
; letter (for example \tsmjournal) the journal db
; files for each journal file system will be written
; to the specified directory on each journal file system.
;
;-----------------------------------------------------------------------
-----
;
[JournalSettings]
Nlsrepos=dscameng.txt
Errorlog=jbberror.log
JournalDir=C:\Program Files\Tivoli\TSM\baclient
;
;
;
; JournalExcludeList
;
; Specifies objects which will be filtered from being inserted/process
; to/from the journal database.
;
; Filesystem changes to objects which match exclude criteria are not
; recorded in the journal.
;
; Patterns may contain simple wildcard characters and environment
variable
; specifications as follows:
;
; %EnvVar% - expand environment variable
;
; Note that environment variable expansions are done prior to
; pattern matching.
;
; Pattern matching characters:
;
; * - match zero or more characters
; % - match one character
;
;
;
; Note that this list contains system files which should always be
excluded.
; Please do not remove any of these entries.
;
[JournalExcludeList]
%SystemRoot%\System32\Config\*
%SystemDrive%\Adsm.Sys\*
%TEMP%\*
%TMP%\*
%USERPROFILE\*\index.dat
*.jdb.dir
*.jdb.pag
*.jdbinc.dir
*.jdbinc.pag
*:\pagefile.sys
*:\*.crmlog
*:\hiberfil.sys
%SystemRoot%\csc\*
%SystemRoot%\System32\DTCLog\MSDTC.LOG
%SystemRoot%\netlogon.chg
%SystemRoot%\schedlgu.txt
%SystemRoot%\registration\*.clb
%WINDIR%\debug\*
%SystemDrive%\Documents and Settings\NetShowServices\ntuser.dat
%SystemDrive%\Documents and Settings\NetShowServices\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat
%USERPROFILE%\ntuser.dat
%USERPROFILE%\Local Settings\Application
Data\Microsoft\Windows\UsrClass.dat
;
;
;
;
;
; JournaledFileSystemSettings
;
; JournaledFileSystems
;
; Space delimited list of filesystems to monitor and journal.
;
; Only local, fixed filesystems are supported, network and
removable
; filesystems are not.
;
; Windows 2000 mountpoints may also be specified
(i.e.c:\mountpntdir).
;
; There must be at least one entry in this list or the Journal
service
; will not start. If the service does not start, the reason may be
; found in the event viewer application log.
;
;
;
; Note the following settings specified under the
JournaledFileSystemSettings
; stanza will apply to all journaled filesystems unless overridden by
a
; JournaledFileSystems override stanza setting of the same name.
;
; For example, the override stanza name for C:\ would be
; JournaledFileSystemSettings.C:\ .
;
;
; JournalDBSize
;
; Maximum journal database size for a journaled filesystem.
;
; A size of 0 indicates that the journal database size will be
; restricted only be the capacity of the drive where journal db
; directory resides.
;
; NotifyFilter
;
; Specifies what types of filesystem activity to monitor for
; a journaled filesystem.
;
; Multiple activities may be monitored by combining (logical OR)
; values.
;
; The default value is 0x117 (File and Dir name changes,
; last write changes, attribute changes, size changes, and
; security changes).
;
;
; Notification Type Filter Value
;
; File name changes, including create, 0x00000001
; delete and rename
;
; Dir name changes, including create, 0x00000002
; delete, and rename
;
; Attribute changes 0x00000004
;
; Size changes, notification is deferred 0x00000008
; until cache is flushed
;
; Last written time changes, notification 0x00000010
; is deferred until cache is flushed
;
; Last access time changes 0x00000020
;
; Creation time changes 0x00000040
;
; Security changes 0x00000100
;
;
;
; NotifyBufferSize
;
; Change notification buffer size for a journaled filesystem.
;
; Large amount of change activity on a journaled filesystem may
; require that this to be increased. The default is 0x100000 (1
Meg).
;
;
; JournalDir
;
; See description under JournalSettings
;
;
; PreserverDBOnExit
;
; A value of 1 indicates that the journaled file system journal
database
; will not be deleted when the journal file system goes offline
and
; will be valid when the journal file system comes back online.
;
; This value should be used with caution as any file system
change
; activity which occurs while the journaled file system is
offline
; will not be reflected in the journal database.
;
; The default setting is 0 (delete journal db on exit).
;
;
; DeferFsMonStart
;
; A value of 1 will defer bringing a journaled file system
online until the
; specified journaled filesystem is valid/available and the
specified journal
; directory can be created/accessed.
;
; Also will monitor online journaled filesystems for
availability
; and will bring the filesystem offline if it becomes
unavailable.
;
; Resources are checked at the interval specified by the
deferRetryInterval
; setting.
;
; This setting is most commonly used in a cluster environment
where shared
; resources may move to different machines in the cluster.
;
; The default setting is 0, meaning that unavailable or
inaccessible journaled
; file systems will not be restarted until the journal service
is recycled.
;
;
; DeferRetryInterval
;
; The value in seconds journaled filesystems with the
deferFsMonStart setting
; enabled will be checked for availability.
;
; The default value is 60 seconds.
;
;
; logFsErrors
;
; A value of 1 indicates that all errors encountered accessing
; a journaled filesystem or journal directory should be logged
; (both to the jbb errorlog and the NT eventlog).
;
; A value of zero indicates that logging of errors encountered
; while checking deferred file systems and journal directories
; will be suppressed.
;
; Usually used in conjunction with the deferFsMonStart setting
to
; eliminate excessive File System unavailable messages from
being
; written to the logs when bringing a journaled filesystem
online
; is deferred.
;
; The default value is 1 (log all errors).
;
;
[JournaledFileSystemSettings]
;
; List of journaled filesystems
;
JournaledFileSystems=C: D: D:\MountPoints\A3M0-Archive_1
D:\MountPoints\A3M0-Archive_10 D:\MountPoints\A3M0-Archive_11
D:\MountPoints\A3M0-Archive_12 D:\MountPoints\A3M0-Archive_13
D:\MountPoints\A3M0-Archive_14 D:\MountPoints\A3M0-Archive_15
D:\MountPoints\A3M0-Archive_16 D:\MountPoints\A3M0-Archive_17
D:\MountPoints\A3M0-Archive_18 D:\MountPoints\A3M0-Archive_19
D:\MountPoints\A3M0-Archive_2 D:\MountPoints\A3M0-Archive_20
D:\MountPoints\A3M0-Archive_21 D:\MountPoints\A3M0-Archive_22
D:\MountPoints\A3M0-Archive_23 D:\MountPoints\A3M0-Archive_24
D:\MountPoints\A3M0-Archive_25 D:\MountPoints\A3M0-Archive_26
D:\MountPoints\A3M0-Archive_27 D:\MountPoints\A3M0-Archive_28
D:\MountPoints\A3M0-Archive_29 D:\MountPoints\A3M0-Archive_3
D:\MountPoints\A3M0-Archive_30 D:\MountPoints\A3M0-Archive_31
D:\MountPoints\A3M0-Archive_32 D:\MountPoints\A3M0-Archive_33
D:\MountPoints\A3M0-Archive_34 D:\MountPoints\A3M0-Archive_35
D:\MountPoints\A3M0-Archive_36 D:\MountPoints\A3M0-Archive_4
D:\MountPoints\A3M0-Archive_5 D:\MountPoints\A3M0-Archive_6
D:\MountPoints\A3M0-Archive_7 D:\MountPoints\A3M0-Archive_8
D:\MountPoints\A3M0-Archive_9 D:\MountPoints\A3M0-Database_1
D:\MountPoints\A3M0-Journal_1 D:\MountPoints\A3M0-Journal_2 E:
;
; Default journal db size
; Allows journal to grow, limited only by space available
JournalDBSize=0x00000000
;
; What events to monitor
;
;
; File & Dir Name, Size, Attrib, Last Write, Security
NotifyFilter=0x00000117
;
;
;
; File & Dir Name, Attrib, Size, Security
; (no caching, immediate notification)
;NotifyFilter=0x00000107
;
;
;
; Notification Buffer Size
;
NotifyBufferSize=0x00100000
;
;
; Don't delete the journal when a journaled file system goes offline
;
;PreserveDBOnExit=1
;
;
; Override settings for individual journaled filesystems.
;
; These settings override settings in JournaledFileSystemSettings
;
;[JournaledFileSystemSettings.C:\]
;JournalDBSize=0x0020000
;NotifyFilter=0x00000107
;NotifyBufferSize=0x00500000
;JournalDir=c:\tsmjournal
PreserveDBOnExit=1
DeferFsMonStart=1
DeferRetryInterval=30
logFsErrors=0
;
;
[JournaledFileSystemSettings.C:\]
JournalDBSize=0x00000000
[JournaledFileSystemSettings.D:\]
JournalDBSize=0x00000000
[JournaledFileSystemSettings.E:\]
JournalDBSize=0x00000000
God bless you!!!
Chip Bell
Systems Analyst I
IBM Tivoli Certified Deployment Professional (ITSM 5.2) Siemens Health
Services Birmingham, AL Office (205) 715-5106 Pager (205)
817-0357 Home (256) 739-0947
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly prohibited. If
you received this information in error, please notify the
sender and delete this information from your computer and retain no
copies of any of this information.
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly prohibited. If
you received this information in error, please notify the
sender and delete this information from your computer and retain no
copies of any of this information.
Confidentiality Notice:
The information contained in this email message is privileged and confidential
information and intended only for the use of the individual or entity named in
the address. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution, or copying of this information is
strictly prohibited. If you received this information in error, please notify
the sender and delete this information from your computer and retain no copies
of any of this information.
|
