Problem SQL virtual node

Question

Hi

Platform:
Window server 2003 R2 ( 32bit) Networker 7.3.3 ( Build 510) SQL Module 5.1.

We clustered out client SQL server. the configuration include 2x Physical Nodes and 4xSQL instances. Each instance has its own IP address.

My backup command -
nsrsqlsv -a VirtualNode -s NWServer
also tried; nsrsqlsv -a VirtualNode

My saveset - MSSQL$INSTANCE: also tries;
MSSQL:
NSSQL$INSTANCE:Database

From one of the Virtial server I can run NW SQL user and backup one the instances. ( have only tried one so far)

When I tried to run the backup from the NW server the backup fails, the virtual server can not be recognised and I get the following error message in my savegroup;

1 retry attempted
29100:nsrsqlsv:Invalid SQL virtual server name gpcl.ssc.com
38563:nsrsqlsv:Invalid option -a
37758:nsrsqlsv:Usage: nsrsqlsv [ ] {path}
options: [-CGjqRTvkuHZ] [-s server] [-N name] [-b pool] [-g group]
[-S count] [-l level] [-m masquerade] [-U user [-P passwd]]
[[-a virtual-server] | [-c client]] [-f aes]
path: d-path | i-path
d-path: MSSQL: | [MSSQL:]s-path [[MSSQL:]s-path [...]]
i-path: MSSQL$inst-name: | MSSQL$inst-name:s-path [...]
s-path: database | database. | database.filegroup |
database.filegroup. | database.filegroup.file
43709:nsrsqlsv:Stop time: Fri Jun 06 15:08:35 2008

Below is a segment from my deamon.log

06/06/08 15:08:10 nsrd: backup001.ssc.com:index:gpcl saving to pool 'Daily' (000026L3)
06/06/08 15:08:10 nsrd: backup001.ssc.com:index:gpcl done saving to pool 'Daily' (000026L3) 18 KB
06/06/08 15:08:10 nsrd: savegroup failure alert: SQLCLDBS Completed/Aborted, Total 1 client(s), 0 Clients disabled, 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded.
06/06/08 15:08:10 nsrd: savegroup alert: SQLCLDBS completed, Total 1 client(s), 1 Failed. Please see group completion details for more information.
* gpcl:MSSQL:GPSQL 29100:nsrsqlsv:Invalid SQL virtual server name gpcl.ssc.com
* gpcl:MSSQL:GPSQL 38563:nsrsqlsv:Invalid option -a
* gpcl:MSSQL:GPSQL 37758:nsrsqlsv:Usage: nsrsqlsv [ ] {path}
* gpcl:MSSQL:GPSQL options: [-CGjqRTvkuHZ] [-s server] [-N name] [-b pool] [-g group]
* gpcl:MSSQL:GPSQL [-S count] [-l level] [-m masquerade] [-U user [-P passwd]]
* gpcl:MSSQL:GPSQL [[-a virtual-server] | [-c client]] [-f aes]
* gpcl:MSSQL:GPSQL path: d-path | i-path
* gpcl:MSSQL:GPSQL d-path: MSSQL: | [MSSQL:]s-path [[MSSQL:]s-path [...]]
* gpcl:MSSQL:GPSQL i-path: MSSQL$inst-name: | MSSQL$inst-name:s-path [...]
* gpcl:MSSQL:GPSQL s-path: database | database. | database.filegroup |
* gpcl:MSSQL:GPSQL database.filegroup. | database.filegroup.file
* gpcl:MSSQL:GPSQL 43709:nsrsqlsv:Stop time: Fri Jun 06 15:06:35 2008
* gpcl:MSSQL:GPSQL
* gpcl:MSSQL:GPSQL 1 retry attempted
* gpcl:MSSQL:GPSQL 29100:nsrsqlsv:Invalid SQL virtual server name gpcl.ssc.com
* gpcl:MSSQL:GPSQL 38563:nsrsqlsv:Invalid option -a
* gpcl:MSSQL:GPSQL 37758:nsrsqlsv:Usage: nsrsqlsv [ ] {path}
* gpcl:MSSQL:GPSQL options: [-CGjqRTvkuHZ] [-s server] [-N name] [-b pool] [-g group]
* gpcl:MSSQL:GPSQL [-S count] [-l level] [-m masquerade] [-U user [-P passwd]]
* gpcl:MSSQL:GPSQL [[-a virtual-server] | [-c client]] [-f aes]
* gpcl:MSSQL:GPSQL path: d-path | i-path
* gpcl:MSSQL:GPSQL d-path: MSSQL: | [MSSQL:]s-path [[MSSQL:]s-path [...]]
* gpcl:MSSQL:GPSQL i-path: MSSQL$inst-name: | MSSQL$inst-name:s-path [...]
* gpcl:MSSQL:GPSQL s-path: database | database. | database.filegroup |
* gpcl:MSSQL:GPSQL database.filegroup. | database.filegroup.file
* gpcl:MSSQL:GPSQL 43709:nsrsqlsv:Stop time: Fri Jun 06 15:06:37 2008
* gpcl:MSSQL:GPSQL
06/06/08 15:08:11 nsrd: runq: NSR group SQLCLDBS exited with return code 1.
pools supported: Daily;

Thanks for your help

ble1 · Accepted Answer

Cluster - multiple db instance - one virtual node
· nodes = nodeA, nodeB
· machine = virt1
· database = db1, db2
· client = virt1

Database Licensing:
· one license for each IP through which the db module backs up data
· as db1 and db2 are backed up through the IP "virt1": one license

Cluster - multiple db instance - multiple virtual nodes
· nodes = nodeA, nodeB
· machine = virt1, virt2
· database = db1, db2
· client = virt1 for db1
· client = virt2 for db2

Database Licensing:
· one license for each IP through which the db module backs up data
· as db1 is backed up through IP "virt1" and db2 is backed up through IP "virt2": two licenses

Since I missed the point where each of your instance is 1 virtual IP then that would 4 licenses indeed.

ble1 · Answer

I would suggest to use newer module build first - I believe build 279 is the latest one.

I know sometimes or in some occasions (or some build, can't remember anymore) -a didn't work so you had to use -c instead. Before you start schedule job, try client initiated one (there is module GUI) to see if it works in the first place.

HabibG2 · Answer

Hi Hrvoje,Client initiated backup, using SQL Module GUI works as mentioned in my 1st message.You mentioned build 279, is it SQL module. I dowloaded the latest one from Powerlink last Friday. Thanks for your helpHabib

HabibG2 · Answer

I will check this.Support got me to run savegrp with -p and the result, according to support was successful, see below;gpcl:Probe level=full, pool=Daily, save as of Fri Jun 06 20:49:19 GMT+0100 2008gpcl:MSSQL$GPCL: level=full, pool=Daily, save as of Fri Jun 06 20:49:19 GMT+0100 2008gpcl:index level=full, pool=Daily, save as of Fri Jun 06 20:49:19 GMT+0100 2008 I then run nsrsqlsv.exe -D5, , XBSA remains empty, see resule from nsrsqlsv.raw below;43708 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 14 Start time: %s 1 35 25 Fri Jun 06 23:48:15 200843621 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 35 Computer Name: %s User Name: %s 2 12 6 SQL002 13 6 SYSTEM52702 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 33 System Version: %d.%d Build %d %s 4 1 1 5 1 1 2 1 4 3790 0 1 S0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Entering log_MDAC_version(). 2 23 9 sqlutil.c 1 4 95670 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 2 660 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 3 1170 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 22 %s(%d): Reg '%s' => %s 4 23 9 sqlutil.c 1 4 9627 23 29 Software\Microsoft\DataAccess 0 11 2.82.3959.037975 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 49 Microsoft Data Access Component(MDAC) version: %s 1 0 11 2.82.3959.00 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 35 %s(%d): Exiting log_MDAC_version(). 2 23 9 sqlutil.c 1 4 96320 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering log_MSSQL_version(). 2 23 9 sqlutil.c 1 4 97130 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 2 660 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 3 1170 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 22 %s(%d): Reg '%s' => %s 4 23 9 sqlutil.c 1 4 9806 23 71 Software\Microsoft\Microsoft SQL Server\GPCL\MSSQLServer\CurrentVersion 0 12 9.00.3042.0037980 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 49 Microsoft SQL Server version (from registry) : %s 1 0 12 9.00.3042.000 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting log_MSSQL_version(). 2 23 9 sqlutil.c 1 4 98100 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 41 %s(%d): Entering log_MSSQL_Name_OnLine(). 2 23 9 sqlutil.c 1 4 96480 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Entering bsFindSqlServers(). 2 23 9 sqlutil.c 1 4 14570 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 40 %s(%d): Entering bsExecFindSqlServers(). 2 23 9 sqlutil.c 1 4 15150 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 46 %s(%d): Entering bsHostToShilohSvsLogonName(). 2 23 9 sqlutil.c 1 3 4830 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 45 %s(%d): Exiting bsHostToShilohSvsLogonName(). 2 23 9 sqlutil.c 1 3 5930 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 49 %s(%d): Unable to determine SVS logon name for %s 3 23 9 sqlutil.c 1 4 1544 12 14 exchcl.ssc.com0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 42 %s(%d): Exiting bsExecFindSqlServers() #2. 2 23 9 sqlutil.c 1 4 15460 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 35 %s(%d): Exiting bsFindSqlServers(). 2 23 9 sqlutil.c 1 4 14720 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 27 %s(%d): Entering cleanUp(). 2 23 12 savemain.cpp 1 3 3390 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 28 %s(%d): Entering saveTerm(). 2 23 10 nsrsqlsv.c 1 4 22500 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 27 %s(%d): Exiting saveTerm(). 2 23 10 nsrsqlsv.c 1 4 23160 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 26 %s(%d): Exiting cleanUp(). 2 23 12 savemain.cpp 1 3 38543709 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 13 Stop time: %s 1 35 25 Fri Jun 06 23:48:15 2008Thanks again.

ble1 · Answer

I'm not sure when that build was released... usually you see build specified in local log.

HabibG2 · Answer

Tried nsrsqlsv -c also -c and -s No joy.

ble1 · Answer

Client initiated backup, using SQL Module GUI worksas mentioned in my 1st message. When looking at first message I see nothing about client side backup.

HabibG2 · Answer

I performed a backup from the virtual server using the NW SQL module and this works. I can do it again and sent you some logs if you think this will help.

When you said client, do you mean the one of the Pnodes ot the Vnode.?

I am sorry if I missed you point.

Thanks
Habib

ble1 · Answer

I was just referring to start client GUI and see if that would work. Since it works, that's already good as at least gives you one way on how to do backup. When you do it that way, is the instance/SQL server the same as what you have defined when running this from server side.

HabibG2 · Answer

My virtual node name is GPCL and my instance is GPCL
When on the client GUI I see the instance as "GPCL\GPCL". I just had to select the instance.

On the server I have tried various combinations;

MSSQL:
MSSQL&GPCL:
MSSQL:GPCL
MSSQL:MSSQL$GPCL

No joy so far.
Thanks
Habib

ble1 · Answer

MSSQL&GPCL:

I assume this is MSSQL$GPCL:

From failures you shown it looks as if when you call backup command there is something that module doesn't like it - name or parameter. MSSQL: should cover them all thus remaining part is to make backup command work correctly.

HabibG2 · Answer

Tried many combinations of save command, no luck so far.

I have tried to start a schedule backup from one of the PNOdes, this also does not work.

Does this error message mean anything to you?

0 1213200382 5 0 0 5352 3888 0 sql002 nsrsqlsv 2 %s 1 24 27 An internal error occurred.

Thanks
Habib

ble1 · Answer

It would better if message was rendered... Can you put your server on 7.4.2? And if not can you try the same with module 5.0?

HabibG2 · Answer

I revert back to 5.0 and this solved most of the problem. However,every time I add a new SQL instance NW cannot seem to be able to allocate the license properly. So I have to remove the module license and reinstall it. I then have to restart nsrd before I can perform a backup. I have two more instances to add, I will keep track of the problem.

Thanks
Habib

HabibG2 · Answer

Hi,I have 4 SQL instances which behaving like 4 individual Virtual clients. Would I need a seperate SQL module license for each instance? I only have one SQL module license, how can I backup the 4 SQL instances with this one SQL module license?ThanksRegardsHabib

NetWorker

Problem SQL virtual node

Was this post helpful?