Unsolved
This post is more than 5 years old
1 Rookie
•
48 Posts
0
1738
October 18th, 2018 12:00
Unable to configure MSSQL Always On DB via Client Wizard
Hi folks,
I need to backup a MSSQL Always On Database on my NetWorker server running v9.2.
There are two hostnames of the Windows server and one listener name which has a DNS entry and is supposed to failover to the standby server when DR occurs. At least that's how I understand it.
The MSSQL user guide states to use the client wizard which will create the dummy clients and all that stuff.
The wizards starts and I choose "SQL-Server":
After that I see the Server but no databases. I try to expand the view by clicking on the black cross but nothing is there. If I choose "Filesystem" in the beginning, a list of the drives is displayed.
I then tried to configure the clients manually but the user guide is not clear on that, I find. So it fails with a message like this: "Syntax error for nsrnmmsv, bad option -o".
Can someone help me or give me a hint?
Thanks
beacon
SergejN.
1 Rookie
•
5 Posts
0
November 8th, 2018 06:00
It is recommended that you back up an Always On Availability Group with a federated backup workflow, and that you use the Windows cluster name as the client Name.
Take a look in the docu: EMC NetWorker Module for Microsoft for SQL VDI
Take care the names of the clients and the cluster name are in DNS (incl. PTR)
SergejN.
1 Rookie
•
5 Posts
0
November 9th, 2018 02:00
does the user have the necessary permission in the MSSQL?
mkeil
68 Posts
0
November 20th, 2018 11:00
Hi,
have you used the availability group listener name or the dns name of the failover cluster instance?
Ibrahiemtami
5 Posts
0
June 19th, 2023 16:00
Hi,
similar issue .. any resolution please .?
barry_beckers
393 Posts
0
June 20th, 2023 11:00
you might wanna shed more light on what you have in place and what you are using and what you tried and what issue you run into (if anything)? And I hope you do not have nor use nw9.2 but an actual supported, more recent version?
We actually never use the nw client wizard, we only configure backups manually as we don't want to deal with needing to be provided nor fill in any user credentials to setup the backups.
Also do you use the backup command that OP mentioned, nsrmmsv? As that would mean VSS based SQL backup, which are way more limited (no transaction log nor incremental backups) than VDI based SQL backups using backup command nsrsqlsv.