ADSM-L

My journal blew up :(

2004-01-28 13:34:51
Subject: My journal blew up :(
From: "French, Michael" <Michael.French AT SAVVIS DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 28 Jan 2004 12:33:22 -0600
        One of my customer's boxes has been running the TSM journaling service 
for about 2 months now and doing backups with no problems.  His box has several 
million files on it and the journal has reduced backup times significantly 
until yesterday when the journal service hung and blew up.  The server at that 
point backed up everything on the system, pushing almost 140GB till we stopped 
it.
        The customer could not stop the journal service, it's going to take a 
reboot.  His system:

Win2K Server
TSM Client 4.2.3
Plenty of free space on both drives
Journal service allowed to grow as large as it needs to

Our setup:
TSM server 5.1.8.1
Solaris 8

        The journal files completely disappeared, he can't locate them on 
either partition.  He found the jbberror.log right where it was supposed to be 
on C:\, see below:

01/22/2004 11:30:07 psFsMonitorThread(tid 1860): Object 'D:\Files\~WRD0001.tmp' 
was deleted after notification.
01/22/2004 11:30:07 psFsMonitorThread(tid 1860): Object 'D:\Files\~WRD0001.tmp' 
was deleted after notification.
01/27/2004 12:55:16 NpWrite: Error 109 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe
01/27/2004 12:55:16 NpWrite: Error 232 writing to named pipe

No real problems until yesterday morning.  He is going to apply the latest 
service pack to this system tomorrow and we will be rollling out the latest TSM 
client in the next week or two (we just upgraded the server in mid-Dec).  I 
haven't seen anything like this either on the list or googling around.  I hope 
someone can help, I don't want my customer to lose confidence in TSM, thanks!



Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
 

<Prev in Thread] Current Thread [Next in Thread>