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.

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

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.

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

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

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

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

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.

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

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.

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

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?

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

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?

Thanks

Regards
Habib