David,
I dont know about anyone else, but here is a snip from an error log
regarding journal crashes:
10/05/2005 14:56:05 win32NpWrite(): Error 232 writing to named pipe
10/05/2005 14:56:05 jnlWrite(): Write failed, rc -190 from commWrite().
10/05/2005 14:56:05 win32NpWrite(): Error 232 writing to named pipe
10/05/2005 14:56:05 jnlWrite(): Write failed, rc -190 from commWrite().
10/05/2005 14:56:05 win32NpWrite(): Error 232 writing to named pipe
10/05/2005 14:56:05 jnlWrite(): Write failed, rc -190 from commWrite().
also:
10/05/2005 08:52:54 psFsMonitorThread(tid 4144): Notification buffer
overrun for monitored FS 'F:\', journal will be reset.
10/05/2005 08:52:54 Error 6 killing thread 556.
10/05/2005 08:52:54 Attempt to free unknown pointer. Addr 008236C8, File
psfsmon.cpp, Line 845
10/05/2005 08:52:54 ReadFsChangesThread(tid 8624):
ReadDirectoryChangesW: buffer overflow error.
10/05/2005 08:52:54 ReadFsChangesThread(tid 8624):
ReadDirectoryChangesW: exiting thread due to buffer overflow error.
10/05/2005 08:52:56 psFsMonitorThread(tid 4144): Notification buffer
overrun for monitored FS 'F:\', journal will be reset.
10/05/2005 08:52:56 Error 6 killing thread 556.
10/05/2005 08:52:56 Assertion failed. Addr 008236C0, File psfsmon.cpp,
Line 845
10/05/2005 08:52:56 ReadFsChangesThread(tid 8692):
ReadDirectoryChangesW: buffer overflow error.
10/05/2005 08:52:56 ReadFsChangesThread(tid 8692):
ReadDirectoryChangesW: exiting thread due to buffer overflow error.
10/05/2005 08:52:58 psFsMonitorThread(tid 4144): Notification buffer
overrun for monitored FS 'F:\', journal will be reset.
10/05/2005 08:52:58 Error 6 killing thread 556.
10/05/2005 08:52:58 Assertion failed. Addr 00834908, File psfsmon.cpp,
Line 845
10/05/2005 08:52:58 ReadFsChangesThread(tid 6464):
ReadDirectoryChangesW: buffer overflow error.
10/05/2005 08:52:58 ReadFsChangesThread(tid 6464):
ReadDirectoryChangesW: exiting thread due to buffer overflow error.
10/05/2005 08:53:00 psFsMonitorThread(tid 4144): Notification buffer
overrun for monitored FS 'F:\', journal will be reset.
10/05/2005 08:53:00 Error 6 killing thread 556.
10/05/2005 08:53:00 ReadFsChangesThread(tid 8712):
ReadDirectoryChangesW: buffer overflow error.
my tsmjbbd.ini looks like this (set per tsm support recommendations):
[JournalSettings]
Nlsrepos=dscameng.txt
Errorlog=jbberror.log
[JournalExcludeList]
%WINDIR%\*
%SystemDrive%\Adsm.Sys\*
%TEMP%\*
%TMP%\*
%USERPROFILE%\*\index.dat
%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
%SystemRoot%\System32\Config\*
*.jdb.dir
*.jdb.pag
*.jdbinc.dir
*.jdbinc.pag
*.jbbdb
*:\pagefile.sys
*:\*.crmlog
*:\hiberfil.sys
*:\...\*.tmp
*:\...\*.ldb
*:\...\*.mdf
*:\...\*.ldf
*:\...\cache\*
*:\...\tsmlvsacache\*
*:\...\exchsrvr\*
*:\...\Temporary Internet Files\*
*:\Recycled\*
*:\Recycler\*
*:\system volume information\*
[JournaledFileSystemSettings]
JournaledFileSystems=E: F: G: H: I: J:
JournalDBSize=0x00000000
NotifyFilter=0x0000015b
NotifyBufferSize=0x00A00000
I am trying to use it on a Win2003 (not going to be SP1 anytime soon)
fileserver with 2 volumes containing a total of 3+TB and 5mil+ files.
TSM server is 5.2.4.3 and client is 5.3.0.5. Incremental backups
transfer 500-600GB per night (alot of large .pst files). The journal
crashes every few weeks and takes the backup with it. I'm going to
start resetting the journal every weekend to see if that helps during
the week, but it shouldnt be that way.
anyone else having journal blues?
Steve Schaub
Systems Engineer, WNI
BlueCross BlueShield of Tennessee
423-752-6574 (desk)
423-785-7347 (cell)
________________________________
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David McClelland
Sent: Wednesday, October 05, 2005 8:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tivoli Continuous Data Protection for Files
Richard,
Certainly take a look at the newer 5.3 TSM client versions of
journaling, if you haven't already, as there are many improvements over
5.2's and below at this level (including a new B-tree based journal DB
which is much more reliable and isn't limited to 2GB in size).
Otherwise, can you tell us what problems are you encountering with
journaling?
CDP sits on top of the same Win32 API that the TSM Journal engine does -
I personally haven't tried it on large file servers, only on local
workstations. I guess you'd need to make sure you tune/allocate enough
disk space for the \RealTimeBackup local backup area for a start (from
the CDP 'gui' in the Configure tree). As a matter of interest, is anyone
else using CDP in this way yet (I know it's only been out and about
externally for a few weeks).
If you're not familiar with it, take a look here for more details:
http://www-306.ibm.com/software/tivoli/products/continuous-data-protecti
on/
Rgds,
David McClelland
Storage and Systems Management Specialist
IBM Tivoli Certified Deployment Professional (ITSM 5.2)
SSO UK Service Delivery - Storage Services
IBM Global Services - IBM United Kingdom
"Dearman, Richard" <rdearm1 AT UIC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/10/2005 17:31
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
[ADSM-L] Tivoli Continuous Data Protection for Files
Has anyone used " Tivoli Continuous Data Protection for Files" product
on a file server with a very large amount of files and directories. I
have a server with millions of files and directories that I can not get
backed because the TSM client either runs out of memory and shuts down
trying to do an incremental, I tried journaling but it keeps failing as
well. This product seems to be journaling continuously which would be
good so the journal would not fill up and fail but can it complete the
initial filesytem backup.
Thanks
**************************EMAIL DISCLAIMER***************************
This email and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is strictly prohibited. If you have received
this
e-mail in error, please delete it and notify the sender or contact
Health
Information Management 312.413.4947.
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
A MIME attachment of type <image/gif> was removed here
by a drop-attachments-by-filetype filter rule on the host <mail2.bcbst.com>.
|
