This post is more than 5 years old
1 Rookie
•
20 Posts
0
1476
June 16th, 2014 01:00
MSSQL backup fails to either standalone or cluster
Networker server 8.1 (on Windows 2008 R2)
Networker clients all 7.6.5 (on windows 2003 R2 Enterprise)
All MSSQL 2005
The error is:
29100:(pid 7492): Invalid SQL virtual server name DIRECT_ACCESS=No
38563:(pid 7492): Invalid option -a
37758:(pid 7492): Usage: nsrsqlsv [ ] {path}
options: [-CGjqRTvkuHXZ] [-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] [-w browse] [-y retention]
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:(pid 7492):Stop time: Mon Jun 16 11:25:17 2014
The message is the same even if i put the -a switch with server name (short - FQDN).
There no Client Direct checked and no Deduplication box checked.
I cannot remember how to overcome this so any help appreciated.
Thanks


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
June 16th, 2014 01:00
The problem here is that you unchecked Direct Save and this is passed as -a argument to backup command which does not work in your case due to old software module you use. Since you run 8.1, I would suggest to update client and start using NMM 3.x (depending on NW8 client version) which replaces NMSQL and issue will be gone.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
June 16th, 2014 02:00
NMM 2.3 does not support server on 8.1 - check compatibility guide. Further, when I check compatibility guide I see no issues running NW8 on win2k3 with SQL 2005.
PapadopoulosA
1 Rookie
•
20 Posts
0
June 16th, 2014 02:00
Due to Windows 2003 nad MSSQL 2005 the compatible module is NMM 2.3 so i will go afor it and make my tests.
I am checking back "client direct" and it seems that backup is running.
PapadopoulosA
1 Rookie
•
20 Posts
0
June 16th, 2014 02:00
Unfortunately the only module that support MSSQL 2005 on Windows 2003 R2 x64 server is the 2.3
I can try NMM 3.0 with 8.0 client
PapadopoulosA
1 Rookie
•
20 Posts
0
June 16th, 2014 03:00
You are right but is true that the NSCG.pdf is somewhat unclear.
If i am not mistaken all R2 are x64 based although in NSCG have the windows 2003 R2 in x86 category.
Thank you again.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
June 16th, 2014 03:00
Again, have you checked the software compatibility guide? Because, if do that you will:
- find x64 win2k3 to be supported with NW 8.1
- NMM 3.1 to support SQL 2005
It might not be clear, but page 68 and 69 are split, but they all refer to same combo. Attached document.
1 Attachment
NSCG.pdf