ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: My journal blew up :(

2004-01-28 17:11:36
Subject: Re: 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 16:10:22 -0600 
        Got the error log from the customer (box is colo, can't login
myself):

01/14/2004 02:04:03 NpPeek: No data
01/14/2004 02:04:08 NpPeek: No data
01/14/2004 02:04:13 NpPeek: No data
01/14/2004 02:04:18 NpPeek: No data
01/14/2004 02:04:23 NpPeek: No data
01/14/2004 02:04:28 NpPeek: No data
01/14/2004 02:04:33 NpPeek: No data
01/15/2004 02:30:51 NpPeek: No data
01/15/2004 02:30:56 NpPeek: No data
01/15/2004 02:31:01 NpPeek: No data
01/15/2004 02:31:06 NpPeek: No data
01/15/2004 02:31:11 NpPeek: No data
01/15/2004 02:31:16 NpPeek: No data
01/16/2004 04:34:18 NpPeek: No data
01/16/2004 04:34:23 NpPeek: No data
01/16/2004 04:34:28 NpPeek: No data
01/16/2004 04:34:33 NpPeek: No data
01/16/2004 04:34:38 NpPeek: No data
01/16/2004 04:34:43 NpPeek: No data
01/16/2004 04:34:48 NpPeek: No data
01/16/2004 04:34:53 NpPeek: No data
01/16/2004 04:34:58 NpPeek: No data
01/16/2004 04:35:03 NpPeek: No data
01/16/2004 04:35:08 NpPeek: No data
01/16/2004 04:35:13 NpPeek: No data
01/16/2004 06:33:57 ANS1228E Sending of object
'\\devstudio\g$\backups\local\VersionControl3.rar' failed
01/16/2004 06:33:57 ANS4037E File
'\\devstudio\g$\backups\local\VersionControl3.rar' changed during
processing.  File skipped.
01/16/2004 06:33:57 ANS1802E Incremental backup of '\\devstudio\g$'
finished with 1 failure

01/16/2004 06:33:57 ANS1802E Incremental backup of '\\devstudio\g$'
finished with 1 failure

01/17/2004 03:42:06 NpPeek: No data
01/17/2004 03:42:11 NpPeek: No data
01/17/2004 03:42:16 NpPeek: No data
01/17/2004 03:42:21 NpPeek: No data
01/17/2004 03:42:26 NpPeek: No data
01/17/2004 03:42:31 NpPeek: No data
01/17/2004 03:42:36 NpPeek: No data
01/17/2004 03:42:41 NpPeek: No data
01/17/2004 03:42:46 NpPeek: No data
01/17/2004 03:42:51 NpPeek: No data
01/17/2004 03:42:56 NpPeek: No data
01/17/2004 03:43:01 NpPeek: No data
01/17/2004 03:43:06 NpPeek: No data
01/17/2004 03:43:11 NpPeek: No data
01/17/2004 03:43:16 NpPeek: No data
01/17/2004 03:43:21 NpPeek: No data
01/17/2004 03:43:26 NpPeek: No data
01/17/2004 03:43:31 NpPeek: No data
01/17/2004 03:43:36 NpPeek: No data
01/18/2004 03:25:22 NpPeek: No data
01/18/2004 03:25:27 NpPeek: No data
01/18/2004 03:25:32 NpPeek: No data
01/18/2004 03:25:37 NpPeek: No data
01/18/2004 03:25:42 NpPeek: No data
01/19/2004 01:59:18 NpPeek: No data
01/19/2004 01:59:23 NpPeek: No data
01/20/2004 02:45:58 NpPeek: No data
01/20/2004 02:46:03 NpPeek: No data
01/20/2004 02:46:08 NpPeek: No data
01/20/2004 02:46:13 NpPeek: No data
01/20/2004 02:46:18 NpPeek: No data
01/20/2004 02:46:23 NpPeek: No data
01/20/2004 02:46:28 NpPeek: No data
01/21/2004 02:20:01 NpPeek: No data
01/21/2004 02:20:06 NpPeek: No data
01/21/2004 02:20:11 NpPeek: No data
01/21/2004 02:20:16 NpPeek: No data
01/21/2004 02:20:21 NpPeek: No data
01/21/2004 02:20:26 NpPeek: No data
01/22/2004 03:17:31 NpPeek: No data
01/22/2004 03:17:36 NpPeek: No data
01/22/2004 03:17:41 NpPeek: No data
01/22/2004 03:17:46 NpPeek: No data
01/22/2004 03:17:51 NpPeek: No data
01/22/2004 03:17:56 NpPeek: No data
01/22/2004 03:18:01 NpPeek: No data
01/22/2004 03:18:06 NpPeek: No data
01/22/2004 03:18:11 NpPeek: No data
01/22/2004 03:18:16 NpPeek: No data
01/22/2004 03:18:21 NpPeek: No data
01/22/2004 03:18:26 NpPeek: No data
01/22/2004 03:18:31 NpPeek: No data
01/23/2004 02:10:36 NpPeek: No data
01/23/2004 02:10:41 NpPeek: No data
01/23/2004 02:10:46 NpPeek: No data
01/23/2004 02:10:51 NpPeek: No data
01/23/2004 02:10:56 NpPeek: No data
01/23/2004 02:11:01 NpPeek: No data
01/24/2004 02:33:31 NpPeek: No data
01/24/2004 02:33:36 NpPeek: No data
01/24/2004 02:33:41 NpPeek: No data
01/24/2004 02:33:46 NpPeek: No data
01/24/2004 02:33:51 NpPeek: No data
01/24/2004 02:33:56 NpPeek: No data
01/25/2004 03:33:42 NpPeek: No data
01/25/2004 03:33:47 NpPeek: No data
01/26/2004 03:18:41 NpPeek: No data
01/26/2004 03:18:46 NpPeek: No data
01/27/2004 02:33:48 NpPeek: No data
01/27/2004 02:33:53 NpPeek: No data
01/27/2004 02:33:58 NpPeek: No data
01/27/2004 02:34:03 NpPeek: No data
01/27/2004 02:34:08 NpPeek: No data
01/27/2004 02:34:13 NpPeek: No data
01/27/2004 02:34:18 NpPeek: No data
01/27/2004 02:34:23 NpPeek: No data
01/27/2004 02:34:28 NpPeek: No data
01/27/2004 02:34:33 NpPeek: No data
01/27/2004 02:34:38 NpPeek: No data
01/27/2004 02:34:43 NpPeek: No data
01/27/2004 02:34:48 NpPeek: No data
01/27/2004 02:34:53 NpPeek: No data
01/27/2004 02:34:58 NpPeek: No data
01/27/2004 02:35:03 NpPeek: No data
01/27/2004 02:35:08 NpPeek: No data
01/27/2004 02:35:13 NpPeek: No data
01/27/2004 02:35:18 NpPeek: No data
01/27/2004 02:35:23 NpPeek: No data
01/27/2004 02:35:28 NpPeek: No data
01/27/2004 02:35:33 NpPeek: No data
01/27/2004 02:35:38 NpPeek: No data
01/27/2004 02:35:43 NpPeek: No data
01/27/2004 02:35:48 NpPeek: No data
01/27/2004 02:35:53 NpPeek: No data
01/27/2004 02:35:58 NpPeek: No data
01/27/2004 02:36:03 NpPeek: No data
01/27/2004 02:36:08 NpPeek: No data
01/27/2004 02:36:13 NpPeek: No data
01/27/2004 02:36:18 NpPeek: No data
01/27/2004 02:36:23 NpPeek: No data
01/27/2004 02:36:28 NpPeek: No data
01/27/2004 02:36:33 NpPeek: No data
01/27/2004 02:36:38 NpPeek: No data
01/27/2004 02:36:43 NpPeek: No data
01/27/2004 02:36:48 NpPeek: No data
01/27/2004 02:36:53 NpPeek: No data
01/27/2004 02:36:58 NpPeek: No data
01/27/2004 02:37:03 NpPeek: No data
01/27/2004 02:37:08 NpPeek: No data
01/27/2004 02:37:13 NpPeek: No data
01/27/2004 02:37:18 NpPeek: No data
01/27/2004 02:37:23 NpPeek: No data
01/27/2004 02:37:28 NpPeek: No data
01/27/2004 02:37:33 NpPeek: No data
01/27/2004 02:37:38 NpPeek: No data
01/27/2004 02:37:43 NpPeek: No data
01/27/2004 02:37:48 NpPeek: No data
01/27/2004 02:37:53 NpPeek: No data
01/27/2004 02:37:58 NpPeek: No data
01/27/2004 02:38:03 NpPeek: No data
01/27/2004 02:38:08 NpPeek: No data
01/27/2004 02:38:13 NpPeek: No data
01/27/2004 12:55:25 ConsoleEventHandler(): Caught Ctrl-C console event .
01/27/2004 12:55:25 ConsoleEventHandler(): Cleaning up and terminating
Process ...

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


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Pete Tanenhaus
Sent: Wednesday, January 28, 2004 11:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: My journal blew up :(


>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:

>From the looks of the jbberror log it appears that perhaps the
client/server session was severed (you would see this in the client
errorlog) and that the backup didn't complete, which in the current
client causes the journal to be invalidated and thus will force the next
backup to be a non-journal based full incremental.

If you post your client errorlog (dsmerror.log) I might be able to
determine what happened.

That being said, I encourage you to upgrade to the 5.16.15 client as
soon as it becomes available as this fixtest contains a significant
number of journal fixes.

I also encourage you to view the Journal Based Backup FAQ Knowledge
article at the follow
location:

http://www-1.ibm.com/support/docview.wss?rs=203&context=SWI00&context=SW
J00&context=SWK00&q1=Journal+Based+Backup&uid=swg21155524&loc=en_US&cs=u
tf-8&lang=en+en

Hope this helps ....


Pete Tanenhaus
Tivoli Storage Solutions Software 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
01/28/2004 01:48 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:        My journal blew up :(



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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Libraries LTO problems with WIN2000 SP4 and TSM 5.2.2.0, Prather, Wanda
Next by Date:  New LTO1 drives for older 3583 libraries (was: New drive in TS M 3583 library - set SCSI ID (NOT), Prather, Wanda
Previous by Thread:  My journal blew up :(, Pete Tanenhaus
Next by Thread:  Re: My journal blew up :(, Richard Sims
Indexes:  [Date] [Thread] [Top] [All Lists]