-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
Schmarck
Sent: Wednesday, April 30, 2008 1:38 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] (41) network connection timed out
Hello.
When I run a backup job, I get a (41) network
]
Subject: Re: [Veritas-bu] (41) network connection timed out
Hi.
On Wed, Apr 30, 2008 at 2:55 PM, [EMAIL PROTECTED] wrote:
Have you verified your NIC settings from the client to the switch? In
our
No, I have not. But why should that be relevant? After all, backup works
just fine, if I backup
On Tue, May 6, 2008 at 8:04 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
most likely, Network performance related.
Hm. But why don't I have any network performance problems, when
I backup to disk, when I backup to tape (with a shorter delay up front)
or in any other network
this one client
Simon
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael
Schmarck
Sent: Tuesday, May 06, 2008 7:58 AM
To: WEAVER, Simon (external)
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] (41) network connection timed out
On Tue, May
Hello.
On Tue, May 6, 2008 at 8:08 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
Michael
Have you enabled full verbose logging on the client then ?
I now have, yes. (VERBOSE=5 and ran mklogdir and restarted netbackup services)
On the client, there's:
== vnetd/log.050608 ==
]; veritas-bu@mailman.eng.auburn.edu;
[EMAIL PROTECTED]
Subject: Re: [Veritas-bu] (41) network connection timed out
Hello.
On Tue, May 6, 2008 at 8:08 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
Michael
Have you enabled full verbose logging on the client then ?
I now have, yes. (VERBOSE
@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] (41) network connection timed out
nope!
have you enabled and run any logging to isolate the problem Michael?
That sounds like the next port of call my friend. At least it may give
an indication where the problem may lie.
Problem may not be wide spread
Who ... me or Micheal ?
-Original Message-
From: Jeff Lightner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 2:12 PM
To: WEAVER, Simon (external); Michael Schmarck
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] (41) network connection timed out
Wow! 10 emails
@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] (41) network connection timed out
nope!
have you enabled and run any logging to isolate the problem Michael?
That sounds like the next port of call my friend. At least it may give
an indication where the problem may lie.
Problem may
: [Veritas-bu] (41) network connection timed out
Wow! 10 emails flogging already dead horses. Were you being held by the
police or something? :-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon (external)
Sent: Tuesday, May 06, 2008 3:06 AM
]
Subject: Re: [Veritas-bu] (41) network connection timed out
Hello.
On Tue, May 6, 2008 at 8:08 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
Michael
Have you enabled full verbose logging on the client then ?
I now have, yes. (VERBOSE=5 and ran mklogdir and restarted
] On Behalf Of Michael
Schmarck
Sent: Tuesday, May 06, 2008 2:39 PM
To: WEAVER, Simon (external); Jeff Lightner
Cc: [EMAIL PROTECTED]; Veritas NetBackup Mailinglist
Subject: Re: [Veritas-bu] (41) network connection timed out
Simon,
same issue.
I did some more tests, though, and found that I just had
@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] (41) network connection timed out
On Tue, May 6, 2008 at 8:04 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
most likely, Network performance related.
Hm. But why don't I have any network performance problems, when
I backup to disk, when I
@mailman.eng.auburn.edu;
[EMAIL PROTECTED]
Subject: Re: [Veritas-bu] (41) network connection timed out
Hello.
On Tue, May 6, 2008 at 8:08 AM, WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
Michael
Have you enabled full verbose logging on the client then ?
I now have, yes
@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] (41) network connection timed out
Simon,
yes, the verbose logging really helped. But the No space left on
device message really was wrong. I now made the tape available again
and was able to write on it.
I suppose that some NBU process misinterpreted bprm failing
Hi.
On Wed, Apr 30, 2008 at 2:55 PM, [EMAIL PROTECTED] wrote:
Have you verified your NIC settings from the client to the switch? In our
No, I have not. But why should that be relevant? After all, backup works
just fine, if I backup to disk or when I backup to tape with a shorter delay
up
Hello.
When I run a backup job, I get a (41) network connection timed out
error.
The backup job triggers a bpstart_notify.$Policy_Name script. In this
script, I have a
sleep 900
statement. So that this doesn't cause any problems, I increased the
BPSTART_TIMEOUT in
Team
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
[EMAIL PROTECTED]
Michael Schmarck [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/30/2008 08:51 AM
To
veritas-bu@mailman.eng.auburn.edu
cc
Subject
[Veritas-bu] (41) network connection timed out
Hello.
When I run a backup job, I
18 matches
Mail list logo
