ADSM-L

Re: Error in DSMERROR.log

2004-02-19 11:10:51
Subject: Re: Error in DSMERROR.log
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 19 Feb 2004 09:10:21 -0700
No, I don't think that's related to the timeout. The journal DB can not
exceed 2 GB (actually 2 * 1024^3 - 1 bytes), so if it's growing that
large, there are other issues.

I recommend you go to
http://www-306.ibm.com/software/sysmgmt/products/support/ and do a search
on

  journal based backup

You will find several useful articles, including a FAQ, that should help
answer many questions.

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.



"Kamp, Bruce" <bkamp AT MHS DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/19/2004 06:49
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Error in DSMERROR.log






Thanks I missed the JNLINBNPTIMEOUT setting.....
One other thing I noticed that my journal DB is over 2Gig.  Could this be
the cause of the timeout?


-----------------------------------------------------
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: bkamp AT mhs DOT net
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: 9542869441 AT archwireless DOT net
Fax: (954) 985-1404
-----------------------------------------------------

-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: Thursday, February 19, 2004 8:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Error in DSMERROR.log

Bruce,

5.2.0.1 or 5.2.0.3 .... not important.

I suggest you carefully re-read the article. If it still doesn't make
sense, post again and quote the part(s) you don't understand so we can
clarify.

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.



"Kamp, Bruce" <bkamp AT MHS DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/19/2004 06:06
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Error in DSMERROR.log






The problem is I'm above that level 5.2.0.3.  The article talks about
version 5.2.0.1.


-----------------------------------------------------
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: bkamp AT mhs DOT net
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: 9542869441 AT archwireless DOT net
Fax: (954) 985-1404
-----------------------------------------------------

-----Original Message-----
From: Warren, Matthew (Retail) [mailto:Matthew.Warren AT POWERGEN.CO DOT UK]
Sent: Thursday, February 19, 2004 6:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Error in DSMERROR.log

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

                -----Original Message-----
                From: "Kamp, Bruce" <bkamp AT MHS DOT NET>@EME
                Sent: Wednesday, February 18, 2004 12:28 PM
                To: ADSM-L AT VM.MARIST DOT EDU
                Subject: Error in DSMERROR.log


                Envirnment:
                Windows 2000 SP4 with TSM client version 5.2.0.3
                TSM server version is 5.2.0.0 on AIX 5.1.

                I have been seeing the following error on onre of my
Windows 2000 nodes:

                02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
                02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
                02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
                pipe.
                02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
                pipe.
                02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
                pipe.
                02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
                pipe.
                02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
                pipe.

                Has anybody else seen this?

                Thanks,
                -----------------------------------------------------
                Bruce Kamp
                Senior Midrange Systems Analyst
                Memorial Healthcare System
                E-mail: bkamp AT mhs DOT net <mailto:bkamp AT mhs DOT net>
                Phone: (954) 987-2020 x4597
                Pager: (954) 286-9441
                Alphapage:  9542869441 AT archwireless DOT net
                Fax: (954) 985-1404
                -----------------------------------------------------


___________________________ Disclaimer Notice __________________________
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended
recipient,
please contact us, delete the message from your computer and destroy any
copies. Any distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen
Group does not accept legal responsibility for this message. The recipient
is responsible for verifying its authenticity before acting on the
contents. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone     +44 (0) 2476 42 4000
Fax           +44 (0) 2476 42 5432

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