--=_mixed 005546D085256FC4_=
Content-Type: multipart/alternative; boundary="=_alternative 005546D285256FC4_="
--=_alternative 005546D285256FC4_=
Content-Type: text/plain; charset="US-ASCII"
Content-Disposition: inline
Something to think about
Regarding checking their own backup status. There is a third party
solution that can do this
The Aptare Storage Console. It provides a web based portal with the
capability to define a client
or group of clients that can been viewed by a login user name.
Check it out at www.aptare.com
=============================
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
David Rock <dave-bu AT graniteweb DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
03/12/2005 11:49 PM
Please respond to
David Rock <dave-bu AT graniteweb DOT com>
To
veritas-bu AT mailman.eng.auburn DOT edu
cc
Subject
Re: [Veritas-bu] "Can't read socket" error on client
* Bobby Williams <Bobby.Williams AT gtsi DOT com> [2005-03-12 13:05]:
> Master is Solaris 8 NB 4.5FP6
>
> I have several Windows (Win2K and NT 4.0) clients that are being backed
up successfully. However, when they go into the console on the client to
view there backups, they get "Can't read socket" error. We updated the
clients to the latest 4.5 release but the error is still there.
>
> I can push restores from the master with no problem. Using bpclntcmd
with any options works correctly from the client. No errors on backups or
restores. It is getting to be a pain when we get paged in the night just
to do a restore for a file.
>
> They would also like to check their own backup status (instead of asking
me every morning).
>
> I don't really know which log to turn on for the client to help identify
the problem.
Make sure the client's name matches what is on the netbackup server,
EXACTLY. In most cases this doesn't matter much, but that changes
drastically once you start dealing with communication INITIATED by the
client. This goes the same for making sure the client has the exact name
of the master server in its name resolution. Sounds stupid, but it's
easy to screw up.
Also, one thing you may try is setting ALLOW_NON_RESERVED_PORTS. This
needs to be added to the bp.conf (in the registry) on the client and
checked in the Host properties of the master server (connect non
reserved port there) in order for it to work. We have had numerous
problems with networking and firewall rules getting in the way of this.
It is possible to allow traffic from the netbackup server TO the client,
but NOT allow it in the opposite direction.
As for turning on logs on the client, run makelog(s).bat in the log
directory in the install location to create ALL log directories. You
will be the mostinterested in bpcd and bprd.
--
David Rock
david AT graniteweb DOT com
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
--=_alternative 005546D285256FC4_=
Content-Type: text/html; charset="US-ASCII"
Content-Disposition: inline
<br><font size=2 face="sans-serif">Something to think about</font>
<br>
<br><font size=2 face="sans-serif">Regarding checking their own backup
status. There is a third party solution that can do this</font>
<br><font size=2 face="sans-serif">The Aptare Storage Console. It
provides a web based portal with the capability to define a client</font>
<br><font size=2 face="sans-serif">or group of clients that can been viewed
by a login user name. </font>
<br>
<br><font size=2 face="sans-serif">Check it out at www.aptare.com</font>
<br>
<br>
<br><font size=2 face="sans-serif">=============================<br>
Carl Stehman<br>
PHI Services Company<br>
202-331-6619<br>
Pager 301-765-2703<br>
ckstehman AT pepco DOT com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>David Rock <dave-bu AT
graniteweb DOT com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">03/12/2005 11:49 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
David Rock <dave-bu AT graniteweb DOT com></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">veritas-bu AT mailman.eng.auburn DOT
edu</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Veritas-bu] "Can't read
socket"
error on client</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>* Bobby Williams <Bobby.Williams AT gtsi DOT com>
[2005-03-12
13:05]:<br>
> Master is Solaris 8 NB 4.5FP6<br>
> <br>
> I have several Windows (Win2K and NT 4.0) clients that are being backed
up successfully. However, when they go into the console on the client
to view there backups, they get "Can't read socket" error. We
updated the clients to the latest 4.5 release but the error is still there.<br>
> <br>
> I can push restores from the master with no problem. Using bpclntcmd
with any options works correctly from the client. No errors on backups
or restores. It is getting to be a pain when we get paged in the
night just to do a restore for a file.<br>
> <br>
> They would also like to check their own backup status (instead of
asking me every morning).<br>
> <br>
> I don't really know which log to turn on for the client to help identify
the problem.<br>
<br>
Make sure the client's name matches what is on the netbackup server,<br>
EXACTLY. In most cases this doesn't matter much, but that changes<br>
drastically once you start dealing with communication INITIATED by the<br>
client. This goes the same for making sure the client has the exact name<br>
of the master server in its name resolution. Sounds stupid, but it's<br>
easy to screw up.<br>
<br>
Also, one thing you may try is setting ALLOW_NON_RESERVED_PORTS. This<br>
needs to be added to the bp.conf (in the registry) on the client and<br>
checked in the Host properties of the master server (connect non<br>
reserved port there) in order for it to work. We have had numerous<br>
problems with networking and firewall rules getting in the way of this.<br>
It is possible to allow traffic from the netbackup server TO the client,<br>
but NOT allow it in the opposite direction.<br>
<br>
As for turning on logs on the client, run makelog(s).bat in the log<br>
directory in the install location to create ALL log directories. You<br>
will be the mostinterested in bpcd and bprd.<br>
<br>
-- <br>
David Rock<br>
david AT graniteweb DOT com<br>
</tt></font>
<br>
<br><br>This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If you
are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
--=_alternative 005546D285256FC4_=--
--=_mixed 005546D085256FC4_=
Content-Type: application/octet-stream; name="attjw3jv.dat"
Content-Disposition: attachment; filename="attjw3jv.dat"
Content-Transfer-Encoding: base64
LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBH
IHYxLjIuNiAoR05VL0xpbnV4KQ0KDQppRDhEQlFGQ004WkhNck80L1liL3h3
WVJBbVNzQUo5VU81ampkdTZVQnlWUGFrV2I3TGl0dUVidlFRQ2cydDBVDQov
SnE3NG5GRm1tckpYVklJaUFYa1oyND0NCj1FMVNPDQotLS0tLUVORCBQR1Ag
U0lHTkFUVVJFLS0tLS0NCg==
--=_mixed 005546D085256FC4_=--
|
