|
[Veritas-bu] Problem with Netbackup 3.2
2003-06-02 14:27:13
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C32934.962F5B30
Content-Type: text/plain;
charset="iso-8859-1"
well it certainly could be a multitude of things. if you want, post your
vm.conf and tpconfig -d.
-----Original Message-----
From: Wes Neal [mailto:wes.neal AT mci DOT com]
Sent: Monday, June 02, 2003 1:48 PM
To: 'Markham, Richard'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem with Netbackup 3.2
No change in IP for quite some time
There is only one server and it has been rebooted multiple times since this
problem occured.
# more bp.conf
SERVER = backup
CLIENT_NAME = backup
Which is my server name. Any idea what else could be causing the error 16?
This is a single server with the L1000 hooked directly to it, so I would
think the network would not be involved.
----
Wes Neal
MCI GNMSS - OSS
(813)829-6915
VNET: 838-6915
Sametime: wes.neal
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Markham,
Richard
Sent: Monday, June 02, 2003 11:33 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Problem with Netbackup 3.2
i'd say its more of a connection problem as opposed to drive problem.
(1) has there been any change in ip
(2) have you bounced services on both master and media
(3) are the appropriate server= entries in bp.conf on both master media
-----Original Message-----
From: Wes Neal [ mailto:wes.neal AT mci DOT com <mailto:wes.neal AT mci DOT
com> ]
Sent: Monday, June 02, 2003 11:27 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem with Netbackup 3.2
Says it is up:
Device Robot Drive Robot Drive Device
Second
Type Num Index Type DrNum Status Comment Name Path
Device Path
robot 0 - TLD - - - - /dev/sg/c2t0l0
drive - 0 dlt 1 UP - Drive0 /dev/rmt/0cbn
----
Wes Neal
MCI GNMSS - OSS
(813)829-6915
VNET: 838-6915
Sametime: wes.neal
-----Original Message-----
From: Teklu, Daniel [ mailto:daniel.teklu AT tfn DOT com
<mailto:daniel.teklu AT tfn DOT com> ]
Sent: Monday, June 02, 2003 11:21 AM
To: 'Wes Neal'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem with Netbackup 3.2
Check if the drive is down? I get that when my drive is down. Check the
status by
# ./tpconfig -l
if it is down, try to bring it up by
# ./vmoprcmd -up Drive_Index
Good Luck
Daniel
-----Original Message-----
From: Wes Neal [ mailto:wes.neal AT mci DOT com <mailto:wes.neal AT mci DOT
com> ]
Sent: Monday, June 02, 2003 11:10 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Problem with Netbackup 3.2
Howdy people, hopefully someone can give me some insight on this. I
have had this implementation of Netbackup 3.2 running for about 3 hours
without a hitch and suddenly about 4 weeks ago it quit working. I am
running Solaris 7. Basically whatever Netbackup tries to do it gets an
error 219 or 213. Here is a snippet from the bpsched log:
10:38:24 [1787] <4> bpsched: INITIATING...
10:38:24 [1787] <2> logparams: /usr/openv/netbackup/bin/bpsched 10:38:24
[1787] <4> bpsched_main: wait_on_que=0, timeout_in_que=36000,
reread_interval=30 0,queue_on_error=0, bptm_query_timeout=480 10:38:24
[1787] <4> db_ATTDEFS: Class_att_defs protocol 3.2 10:38:24 [1787] <4>
bpsched_main: VSMInit () failed: 2d
10:38:24 [1787] <4> ?: post process images: yes
10:38:24 [1787] <4> ?: keep tir: yes
10:38:25 [1787] <2> getsockconnected: Connect to backup on port 689
10:38:26 [1787] <2> getsockconnected: Connect to backup on port 529
10:38:27 [1787] <2> getsockconnected: Connect to backup on port 947
10:38:28 [1787] <2> getsockconnected: Connect to backup on port 783
10:38:29 [1787] <2> getsockconnected: Connect to backup on port 593
10:38:30 [1787] <2> getsockconnected: Connect to backup on port 1017
10:38:31 [1787] <2> getsockconnected: Connect to backup on port 787
10:38:32 [1787] <2> getsockconnected: Connect to backup on port 695
10:38:33 [1787] <2> getsockconnected: Connect to backup on port 561
10:38:34 [1787] <2> getsockconnected: Connect to backup on port 641
10:38:35 [1787] <2> getsockconnected: Connect to backup on port 947
10:38:36 [1787] <2> getsockconnected: Connect to backup on port 799
10:38:37 [1787] <2> getsockconnected: Connect to backup on port 721
10:38:38 [1787] <2> getsockconnected: Connect to backup on port 873
10:38:39 [1787] <2> getsockconnected: Connect to backup on port 787
10:38:40 [1787] <2> getsockconnected: Connect to backup on port 647
10:38:41 [1787] <2> getsockconnected: Connect to backup on port 945
10:38:42 [1787] <2> getsockconnected: Connect to backup on port 817
10:38:43 [1787] <2> getsockconnected: Connect to backup on port 947
10:38:44 [1787] <2> getsockconnected: Connect to backup on port 815
10:38:45 [1787] <2> getsockconnected: Connect to backup on port 849
10:38:46 [1787] <2> getsockconnected: Connect to backup on port 729
10:38:47 [1787] <2> getsockconnected: Connect to backup on port 787
10:38:48 [1787] <2> getsockconnected: Connect to backup on port 663
10:38:49 [1787] <2> getsockconnected: Connect to backup on port 817
10:38:50 [1787] <2> getsockconnected: Connect to backup on port 929
10:38:51 [1787] <2> getsockconnected: Connect to backup on port 947
10:38:52 [1787] <2> getsockconnected: Connect to backup on port 831
10:38:53 [1787] <2> getsockconnected: Connect to backup on port 977
10:38:54 [1787] <2> getsockconnected: Connect to backup on port 585
10:38:55 [1787] <2> getsockconnected: Connect to backup on port 787
10:38:56 [1787] <2> getsockconnected: Connect to backup on port 871
10:38:56 [1787] <16> getsockconnected: exceeded timeout of 30 seconds
10:38:56 [1787] <2> getsockconnected: sockfd:-1 timo:32 10:38:56 [1787]
<16> bpcr_connect: Can't connect to client backup 10:38:56 [1787] <16>
start_bptm: connection refused by host backup 10:38:56 [1787] <16>
get_stunits: get_num_avail_drives failed with stat 204 10:38:56 [1787]
<4> get_db_info: no available storage units 10:38:56 [1787] <8>
bpsched_main: failed getting database information 10:38:56 [1787] <16>
log_in_errorDB: scheduler exiting - no storage units available for u se
(213) 10:38:56 [1787] <16> bpsched: scheduler exiting - no storage units
available for use (213
)
I have not seen these before. Any help would be much appreciated.
Thanks
Wes
----
Wes Neal
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
------_=_NextPart_001_01C32934.962F5B30
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=940172618-02062003>well
it certainly could be a multitude of things. if you want, post your
vm.conf and tpconfig -d.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=940172618-02062003></SPAN></FONT> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Wes Neal
[mailto:wes.neal AT mci DOT com]<BR><B>Sent:</B> Monday, June 02, 2003 1:48
PM<BR><B>To:</B> 'Markham, Richard';
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Problem
with Netbackup 3.2<BR><BR></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=860004617-02062003>No
change in IP for quite some time</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=860004617-02062003>There is only one server and it has been rebooted
multiple times since this problem occured.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=860004617-02062003>#
more bp.conf<BR>SERVER = backup<BR>CLIENT_NAME = backup</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=860004617-02062003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=860004617-02062003>Which is my server name. Any idea what else
could be causing the error 16?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=860004617-02062003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=860004617-02062003>This
is a single server with the L1000 hooked directly to it, so I would think the
network would not be involved.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>----<BR>Wes Neal<BR>MCI GNMSS - OSS<BR>(813)829-6915<BR>VNET:
838-6915<BR>Sametime: wes.neal<BR> </FONT> </P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Markham, Richard<BR><B>Sent:</B> Monday, June 02, 2003 11:33
AM<BR><B>To:</B> 'veritas-bu AT mailman.eng.auburn DOT
edu'<BR><B>Subject:</B> RE:
[Veritas-bu] Problem with Netbackup 3.2<BR><BR></FONT></DIV>
<P><FONT size=2>i'd say its more of a connection problem as opposed to
drive
problem. </FONT></P>
<P><FONT size=2>(1) has there been any change in ip</FONT> <BR><FONT
size=2>(2) have you bounced services on both master and media</FONT>
<BR><FONT size=2>(3) are the appropriate server= entries in bp.conf on both
master media</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Wes
Neal [<A href="mailto:wes.neal AT mci DOT com">mailto:wes.neal AT mci DOT
com</A>]</FONT>
<BR><FONT size=2>Sent: Monday, June 02, 2003 11:27 AM</FONT> <BR><FONT
size=2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT
size=2>Subject: RE: [Veritas-bu] Problem with Netbackup 3.2</FONT> </P><BR>
<P><FONT size=2>Says it is up:</FONT> </P>
<P><FONT size=2>Device Robot Drive
Robot
Drive Device</FONT> <BR><FONT size=2>Second</FONT> <BR><FONT
size=2>Type Num Index Type DrNum Status
Comment Name Path</FONT> <BR><FONT
size=2>Device Path</FONT> <BR><FONT
size=2>robot 0
- TLD
- -
-
- /dev/sg/c2t0l0</FONT> <BR><FONT
size=2> drive -
0 dlt 1
UP -
Drive0 /dev/rmt/0cbn</FONT> </P><BR>
<P><FONT size=2>----</FONT> <BR><FONT size=2>Wes Neal</FONT> <BR><FONT
size=2>MCI GNMSS - OSS</FONT> <BR><FONT size=2>(813)829-6915</FONT>
<BR><FONT size=2>VNET: 838-6915</FONT> <BR><FONT size=2>Sametime:
wes.neal</FONT> <BR><FONT size=2> </FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Teklu, Daniel [<A
href="mailto:daniel.teklu AT tfn DOT com">mailto:daniel.teklu AT tfn DOT
com</A>]
</FONT><BR><FONT size=2>Sent: Monday, June 02, 2003 11:21 AM</FONT>
<BR><FONT size=2>To: 'Wes Neal'; veritas-bu AT mailman.eng.auburn DOT
edu</FONT>
<BR><FONT size=2>Subject: RE: [Veritas-bu] Problem with Netbackup
3.2</FONT>
</P><BR>
<P><FONT size=2>Check if the drive is down? I get that when my drive is
down. Check the</FONT> <BR><FONT size=2>status by</FONT> </P>
<P><FONT size=2># ./tpconfig -l</FONT> </P>
<P><FONT size=2>if it is down, try to bring it up by</FONT> </P>
<P><FONT size=2># ./vmoprcmd -up Drive_Index</FONT> </P>
<P><FONT size=2>Good Luck</FONT> <BR><FONT size=2>Daniel</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Wes
Neal [<A href="mailto:wes.neal AT mci DOT com">mailto:wes.neal AT mci DOT
com</A>]</FONT>
<BR><FONT size=2>Sent: Monday, June 02, 2003 11:10 AM</FONT> <BR><FONT
size=2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT
size=2>Subject: [Veritas-bu] Problem with Netbackup 3.2</FONT> </P><BR>
<P><FONT size=2>Howdy people, hopefully someone can give me some insight on
this. I</FONT> <BR><FONT size=2>have had this implementation of
Netbackup 3.2 running for about 3 hours</FONT> <BR><FONT size=2>without a
hitch and suddenly about 4 weeks ago it quit working. I am</FONT>
<BR><FONT size=2>running Solaris 7. Basically whatever Netbackup
tries
to do it gets an</FONT> <BR><FONT size=2>error 219 or 213. Here is a
snippet from the bpsched log:</FONT> </P>
<P><FONT size=2>10:38:24 [1787] <4> bpsched: INITIATING...</FONT>
<BR><FONT size=2>10:38:24 [1787] <2> logparams:
/usr/openv/netbackup/bin/bpsched 10:38:24</FONT> <BR><FONT size=2>[1787]
<4> bpsched_main: wait_on_que=0, timeout_in_que=36000,</FONT>
<BR><FONT size=2>reread_interval=30 0,queue_on_error=0,
bptm_query_timeout=480 10:38:24</FONT> <BR><FONT size=2>[1787] <4>
db_ATTDEFS: Class_att_defs protocol 3.2 10:38:24 [1787] <4></FONT>
<BR><FONT size=2>bpsched_main: VSMInit () failed: 2d</FONT> <BR><FONT
size=2>10:38:24 [1787] <4> ?: post process
images: yes</FONT> <BR><FONT size=2>10:38:24 [1787] <4>
?: keep tir: yes</FONT> <BR><FONT size=2>10:38:25
[1787] <2> getsockconnected: Connect to backup on port 689</FONT>
<BR><FONT size=2>10:38:26 [1787] <2> getsockconnected: Connect to
backup on port 529</FONT> <BR><FONT size=2>10:38:27 [1787] <2>
getsockconnected: Connect to backup on port 947</FONT> <BR><FONT
size=2>10:38:28 [1787] <2> getsockconnected: Connect to backup on
port
783</FONT> <BR><FONT size=2>10:38:29 [1787] <2> getsockconnected:
Connect to backup on port 593</FONT> <BR><FONT size=2>10:38:30 [1787]
<2> getsockconnected: Connect to backup on port 1017</FONT> <BR><FONT
size=2>10:38:31 [1787] <2> getsockconnected: Connect to backup on
port
787</FONT> <BR><FONT size=2>10:38:32 [1787] <2> getsockconnected:
Connect to backup on port 695</FONT> <BR><FONT size=2>10:38:33 [1787]
<2> getsockconnected: Connect to backup on port 561</FONT> <BR><FONT
size=2>10:38:34 [1787] <2> getsockconnected: Connect to backup on
port
641</FONT> <BR><FONT size=2>10:38:35 [1787] <2> getsockconnected:
Connect to backup on port 947</FONT> <BR><FONT size=2>10:38:36 [1787]
<2> getsockconnected: Connect to backup on port 799</FONT> <BR><FONT
size=2>10:38:37 [1787] <2> getsockconnected: Connect to backup on
port
721</FONT> <BR><FONT size=2>10:38:38 [1787] <2> getsockconnected:
Connect to backup on port 873</FONT> <BR><FONT size=2>10:38:39 [1787]
<2> getsockconnected: Connect to backup on port 787</FONT> <BR><FONT
size=2>10:38:40 [1787] <2> getsockconnected: Connect to backup on
port
647</FONT> <BR><FONT size=2>10:38:41 [1787] <2> getsockconnected:
Connect to backup on port 945</FONT> <BR><FONT size=2>10:38:42 [1787]
<2> getsockconnected: Connect to backup on port 817</FONT> <BR><FONT
size=2>10:38:43 [1787] <2> getsockconnected: Connect to backup on
port
947</FONT> <BR><FONT size=2>10:38:44 [1787] <2> getsockconnected:
Connect to backup on port 815</FONT> <BR><FONT size=2>10:38:45 [1787]
<2> getsockconnected: Connect to backup on port 849</FONT> <BR><FONT
size=2>10:38:46 [1787] <2> getsockconnected: Connect to backup on
port
729</FONT> <BR><FONT size=2>10:38:47 [1787] <2> getsockconnected:
Connect to backup on port 787</FONT> <BR><FONT size=2>10:38:48 [1787]
<2> getsockconnected: Connect to backup on port 663</FONT> <BR><FONT
size=2>10:38:49 [1787] <2> getsockconnected: Connect to backup on
port
817</FONT> <BR><FONT size=2>10:38:50 [1787] <2> getsockconnected:
Connect to backup on port 929</FONT> <BR><FONT size=2>10:38:51 [1787]
<2> getsockconnected: Connect to backup on port 947</FONT> <BR><FONT
size=2>10:38:52 [1787] <2> getsockconnected: Connect to backup on
port
831</FONT> <BR><FONT size=2>10:38:53 [1787] <2> getsockconnected:
Connect to backup on port 977</FONT> <BR><FONT size=2>10:38:54 [1787]
<2> getsockconnected: Connect to backup on port 585</FONT> <BR><FONT
size=2>10:38:55 [1787] <2> getsockconnected: Connect to backup on
port
787</FONT> <BR><FONT size=2>10:38:56 [1787] <2> getsockconnected:
Connect to backup on port 871</FONT> <BR><FONT size=2>10:38:56 [1787]
<16> getsockconnected: exceeded timeout of 30 seconds</FONT>
<BR><FONT
size=2>10:38:56 [1787] <2> getsockconnected: sockfd:-1 timo:32
10:38:56 [1787]</FONT> <BR><FONT size=2><16> bpcr_connect: Can't
connect to client backup 10:38:56 [1787] <16></FONT> <BR><FONT
size=2>start_bptm: connection refused by host backup 10:38:56 [1787]
<16></FONT> <BR><FONT size=2>get_stunits: get_num_avail_drives failed
with stat 204 10:38:56 [1787]</FONT> <BR><FONT size=2><4>
get_db_info:
no available storage units 10:38:56 [1787] <8></FONT> <BR><FONT
size=2>bpsched_main: failed getting database information 10:38:56 [1787]
<16></FONT> <BR><FONT size=2>log_in_errorDB: scheduler exiting - no
storage units available for u se</FONT> <BR><FONT size=2>(213) 10:38:56
[1787] <16> bpsched: scheduler exiting - no storage units</FONT>
<BR><FONT size=2>available for use (213</FONT> <BR><FONT size=2>)</FONT>
</P>
<P><FONT size=2>I have not seen these before. Any help would be much
appreciated.</FONT> </P>
<P><FONT size=2>Thanks</FONT> <BR><FONT size=2>Wes</FONT> </P><BR>
<P><FONT size=2>----</FONT> <BR><FONT size=2>Wes Neal</FONT> </P>
<P><FONT size=2>_______________________________________________</FONT>
<BR><FONT size=2>Veritas-bu maillist -
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=2><A
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";
target=_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FONT>
</P>
<P><FONT size=2>_______________________________________________</FONT>
<BR><FONT size=2>Veritas-bu maillist -
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=2><A
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";
target=_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FONT>
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C32934.962F5B30--
|
| Previous by Date: |
[Veritas-bu] format of "bpimagelist -l", Fisk, Nathan (ROC) |
| Next by Date: |
[Veritas-bu] NBU 3.5, Solaris, SAN, DiskSuite problems, Jeff Bryer |
| Previous by Thread: |
[Veritas-bu] Problem with Netbackup 3.2, Markham, Richard |
| Next by Thread: |
[Veritas-bu] Problem with Netbackup 3.2, Markham, Richard |
| Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|
