@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Strange status 13 during bpstart script
Well on the client they are empty and on the master server windows its
using the vxlog thingy which i've not looked at before. I.e there's
nothing in ~netbackup\logs\bpbrm. :(
I'm a unix engineer so find
On Wed, May 19, 2010 at 4:57 AM, Dave Markham dave.mark...@fjserv.netwrote:
What we've found out is that its the firewall between media and client
which is cutting off this connection after 2 hours. The bpstart script
is still running on the client but after the firewall tcp timeout of 2
Guys i've been reading on Status 13 quite a bit but am still flummoxed
as to why we are getting this on an environment here.
Ok
Netbackup 6.0MP4 Windows 2003 Master server
Netbackup 6.0MP4 Windows 2003 Media server attached to EMC disk virtual
storage.
Netbackup 6.0MP4 Linux Client running
Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dave
Markham
Sent: 14 May 2010 12:37
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Strange status 13 during bpstart script
Guys i've been reading on Status 13
: Dave Markham [mailto:dave.mark...@fjserv.net]
Sent: 14 May 2010 14:30
To: Whelan, Patrick
Subject: Re: [Veritas-bu] Strange status 13 during bpstart script
No it's just set to 900 still.
We could increase that, but if it's the CLIENT_READ_TIMEOUT why is that
not being hit and exiting
