[Networker] SQL 2000 backup in clustered environment.
2004-02-20 16:55:23
Hello all,
Wrote about this a while back, but didn't get a response. It's kind
of become urgent now.
I have 2 systems in an MSCS clustered environment. Both are running Win2K
advanced and SQL 2000 Enterprise. Both have Networker client 7.1 and
Networker module for SQL 3.1.1. The nodes are named snap and pans. The
virtual net name for the cluster group is Gecko. The net name for the SQL
server is Blade. I have hosts files on both systems specifying the IPs of the
nodes and virtual interfaces.
On the Legato side, it's a 7.0 server (power edition) running on Linux. When
I attempt to backup the SQL databases (Save set MSSQL:) I am getting a
multitude of problems. I created a client named gecko. In the aliases field
there is gecko, and blade. for the remote command I am running: nsrsqlsv -a
blade. I get an error message from networker on attempting to run a savegrp
on this client saying:
* gecko:MSSQL: nsrsqlsv: Invalid SQL virtual server name blade
* gecko:MSSQL: nsrsqlsv: Invalid option -a
The hosts file on the Networker server has all of the proper entries. This
has been ongoing and now has become a priority as this system will soon need
to go into production. Any assistance can be appreciated. I almost think the
problem is on the cluster side, because there is no MSDTC resource in the
SQL_Servers group in cluster groups. That is going to be added during some
downtime tomorrow. Will this help? Could it be part of the problem? When I
run an rpcinfo -p from the networker server to any node, virtual or real, I
get the following output:
program vers proto port
100000 2 tcp 7938 portmapper
100000 2 udp 7938 portmapper
390113 1 tcp 7937 nsrexec
>From the SQL cluster back to the networker server:
C:\PROGRA~1\Legato\nsr\bin>rpcinfo -p carl
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390115 1 tcp 23123
390113 1 tcp 7937
390103 2 tcp 8087
390109 2 tcp 8087
390110 1 tcp 8087
390103 2 udp 8262
390109 2 udp 8262
390110 1 udp 8262
390107 5 tcp 8194
390107 6 tcp 8194
390105 5 tcp 9787
390104 105 tcp 9067
390104 205 tcp 9456
390104 305 tcp 8597
390104 405 tcp 7981
390104 505 tcp 8722
390104 605 tcp 9863
390104 705 tcp 9275
390104 805 tcp 8416
390104 905 tcp 9781
program vers proto port
100000 2 tcp 111
100000 2 udp 111
100024 1 udp 32768
100024 1 tcp 32768
391002 2 tcp 32769
390115 1 tcp 23123
390113 1 tcp 7937
390103 2 tcp 8087
390109 2 tcp 8087
390110 1 tcp 8087
390103 2 udp 8262
390109 2 udp 8262
390110 1 udp 8262
390107 5 tcp 8194
390107 6 tcp 8194
390105 5 tcp 9787
390104 105 tcp 9067
390104 205 tcp 9456
390104 305 tcp 8597
390104 405 tcp 7981
390104 505 tcp 8722
390104 605 tcp 9863
390104 705 tcp 9275
390104 805 tcp 8416
390104 905 tcp 9781
Why doesn't the SQL cluster name the UDP ports like the Networker server? Is
this something particular to Windows? Also, why does this get displayed
twice? Any help would be greatly appreciated as we are at a standstill.
Thanks!
Matt Ungaro (mjungaro AT capitolindemnity DOT com)
Network Specialist
Capitol Indemnity Corporation
4610 University Ave. Ste. 1400
Madison, WI 53705
Phone: (608)232-5654
Fax: (608)232-5671
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] SQL 2000 backup in clustered environment.,
Ungaro, Matt <=
|
|
|