Start a Conversation

HabibG2

updated

18 years ago

Solved!

Go to Solution
H

HabibG2

455 Posts

0

3691

June 6th, 2008 12:00

Problem SQL virtual node

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
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2460

    0

    Posted June 20th, 2008 02:00

    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.
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1617

    0

    Posted June 7th, 2008 06:00

    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.
  • H

    HabibG2

    455 Posts

    1617

    0

    Posted June 7th, 2008 14:00

    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 help
    Habib
  • H

    HabibG2

    455 Posts

    1617

    0

    Posted June 7th, 2008 15:00

    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 2008

    gpcl:MSSQL$GPCL: level=full, pool=Daily, save as of Fri Jun 06 20:49:19 GMT+0100 2008

    gpcl: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 2008

    43621 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 35 Computer Name: %s User Name: %s 2 12 6 SQL002 13 6 SYSTEM
    52702 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 S
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Entering log_MDAC_version(). 2 23 9 sqlutil.c 1 4 9567
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 2 66
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 3 117
    0 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.0
    37975 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 49 Microsoft Data Access Component(MDAC) version: %s 1 0 11 2.82.3959.0
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 35 %s(%d): Exiting log_MDAC_version(). 2 23 9 sqlutil.c 1 4 9632
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering log_MSSQL_version(). 2 23 9 sqlutil.c 1 4 9713
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 37 %s(%d): Entering LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 2 66
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting LgRegQueryValueEx(). 2 23 13 sqlutilpp.cpp 1 3 117
    0 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.00
    37980 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 49 Microsoft SQL Server version (from registry) : %s 1 0 12 9.00.3042.00
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Exiting log_MSSQL_version(). 2 23 9 sqlutil.c 1 4 9810
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 41 %s(%d): Entering log_MSSQL_Name_OnLine(). 2 23 9 sqlutil.c 1 4 9648
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 36 %s(%d): Entering bsFindSqlServers(). 2 23 9 sqlutil.c 1 4 1457
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 40 %s(%d): Entering bsExecFindSqlServers(). 2 23 9 sqlutil.c 1 4 1515
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 46 %s(%d): Entering bsHostToShilohSvsLogonName(). 2 23 9 sqlutil.c 1 3 483
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 45 %s(%d): Exiting bsHostToShilohSvsLogonName(). 2 23 9 sqlutil.c 1 3 593
    0 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.com
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 42 %s(%d): Exiting bsExecFindSqlServers() #2. 2 23 9 sqlutil.c 1 4 1546
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 35 %s(%d): Exiting bsFindSqlServers(). 2 23 9 sqlutil.c 1 4 1472
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 27 %s(%d): Entering cleanUp(). 2 23 12 savemain.cpp 1 3 339
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 28 %s(%d): Entering saveTerm(). 2 23 10 nsrsqlsv.c 1 4 2250
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 27 %s(%d): Exiting saveTerm(). 2 23 10 nsrsqlsv.c 1 4 2316
    0 1212792495 0 0 1 4508 6008 0 sql002 nsrsqlsv 26 %s(%d): Exiting cleanUp(). 2 23 12 savemain.cpp 1 3 385
    43709 1212792495 1 0 0 4508 6008 0 sql002 nsrsqlsv 13 Stop time: %s 1 35 25 Fri Jun 06 23:48:15 2008

    Thanks again.
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1617

    0

    Posted June 7th, 2008 15:00

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

    HabibG2

    455 Posts

    1617

    0

    Posted June 10th, 2008 01:00

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

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1617

    0

    Posted June 11th, 2008 00:00

    Client initiated backup, using SQL Module GUI works
    as mentioned in my 1st message.

    When looking at first message I see nothing about client side backup.
  • H

    HabibG2

    455 Posts

    1617

    0

    Posted June 11th, 2008 01:00

    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
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1616

    0

    Posted June 11th, 2008 01:00

    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.
  • H

    HabibG2

    455 Posts

    1616

    0

    Posted June 11th, 2008 04:00

    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

Dell Support Resources

Latest Solutions

View More