This is a multipart message in MIME format.
--=_alternative 005A392E86256E7F_=
Content-Type: text/plain; charset="US-ASCII"
Ok....
I'm a twit ;)
I was using a UNIX to manually submit my backups using bpbackup on the
master server
I had SERVER_PORT_WINDOW = 13740 13750 and CLIENT_PORT_WINDOW = 13740
13750
enabled in bp.conf
Not enough ports were being opened up on the netbackup server. Causing an
error 25, and then error 96's since vmd could start up.
Commented out server_port_window and client_port_window and everything
worked like a charm. I originally backed set server_port_window to backup
threw a firewall on 3.4 see
http://www.backupcentral.com/cgi-bin/netbackup-fom?_highlightWords=server%20port%20window&file=70
4.5 and 5.0 allows me to set that for each client.
Thanks,
Karl
PS: The veritas tech that helped me said that MP2 should be out within a
week.
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 04/22/2004 04:48:20 PM:
>
> veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 04/22/2004 11:24:02
> AM:
>
> > Windows and Unix can't share the same storage unit since you can't mix
> > Windows and Unix data on the same tape (type 13 vs type 0). So, your
> > Windows storage unit likely has no free tapes which is what will give
> > you the 96. When you get an error 25, is the current tape frozen? If
> > so, that would explain the 96 errors since you're out of tapes.
>
> Ed,
>
> The status 25 tapes are not frozen.
>
> I have two autoloaders. Each autoloader only has 1 tape in it with 1
drive.
>
> I'm waiting on a call back from veritas, so i have had a lot of time
> to sit and speculate what's going on.
> 1. Netbackup is doing as it's configured and backing one client to
> each drive(2 jobs, one to each drive).
> 2. One of the clients/jobs get's an error 25.
> 3. Netbackup retries the job and gets another error 25.
> 4. Netbackup now cancels the job.
> 5. Then netbackup decides to start a queued job starts up.
> BUT Netbackup for some reason has not wait long enough to release
> the tape it was using. It thinks it's still in use(or half frozen).
> Then the error 96's start popping up.
>
> I'm going to add an extra tape to each autoloader tonight. With
> luck, I'll still get my error 25's(which i can troubleshoot) but the
> error 96's will not be there.
>
> KFR
--=_alternative 005A392E86256E7F_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Ok....</font>
<br>
<br>
<br><font size=2 face="sans-serif">I'm a twit ;)</font>
<br>
<br><font size=2 face="sans-serif">I was using a UNIX to manually submit
my backups using bpbackup on the master server</font>
<br><font size=2 face="sans-serif">I had </font><font size=2 color=#000080
face="Arial">SERVER_PORT_WINDOW
= 13740 13750 and CLIENT_PORT_WINDOW = 13740 13750</font>
<br><font size=2 face="sans-serif">enabled in bp.conf</font>
<br>
<br><font size=2 face="sans-serif">Not enough ports were being opened up
on the netbackup server. Causing an error 25, and then error 96's since
vmd could start up.</font>
<br>
<br><font size=2 face="sans-serif">Commented out server_port_window and
client_port_window and everything worked like a charm. I originally backed
set server_port_window to backup threw a firewall on 3.4 see
http://www.backupcentral.com/cgi-bin/netbackup-fom?_highlightWords=server%20port%20window&file=70</font>
<br>
<br><font size=2 face="sans-serif">4.5 and 5.0 allows me to set that for
each client.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Karl</font>
<br>
<br><font size=2 face="sans-serif">PS: The veritas tech that helped me
said that MP2 should be out within a week.</font>
<br>
<br><font size=2><tt>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on
04/22/2004
04:48:20 PM:<br>
<br>
> <br>
> veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 04/22/2004 11:24:02
AM:<br>
> <br>
> > Windows and Unix can't share the same storage unit since you
can't mix<br>
> > Windows and Unix data on the same tape (type 13 vs type 0). So,
your<br>
> > Windows storage unit likely has no free tapes which is what will
give<br>
> > you the 96. When you get an error 25, is the current tape
frozen? If<br>
> > so, that would explain the 96 errors since you're out of tapes.<br>
> <br>
> Ed, <br>
> <br>
> The status 25 tapes are not frozen. <br>
> <br>
> I have two autoloaders. Each autoloader only has 1 tape in it with
1 drive. <br>
> <br>
> I'm waiting on a call back from veritas, so i have had a lot of time<br>
> to sit and speculate what's going on. </tt></font>
<br><font size=2><tt>> 1. Netbackup is doing as it's configured and
backing one client to <br>
> each drive(2 jobs, one to each drive). </tt></font>
<br><font size=2><tt>> 2. One of the clients/jobs get's an error 25.
</tt></font>
<br><font size=2><tt>> 3. Netbackup retries the job and gets another
error 25. </tt></font>
<br><font size=2><tt>> 4. Netbackup now cancels the job. </tt></font>
<br><font size=2><tt>> 5. Then netbackup decides to start a queued job
starts up.<br>
> BUT Netbackup for some reason has not wait long enough to release
<br>
> the tape it was using. It thinks it's still in use(or half frozen).
<br>
> Then the error 96's start popping up.</tt></font>
<br><font size=2><tt>> <br>
> I'm going to add an extra tape to each autoloader tonight. With <br>
> luck, I'll still get my error 25's(which i can troubleshoot) but the<br>
> error 96's will not be there. <br>
> <br>
> KFR</tt></font>
--=_alternative 005A392E86256E7F_=--
|
