Scribd
Upload
517 views3 pages

NMM NSRSQLSV Syntax For An SQL Server Cluster Instance

This document discusses how to backup a clustered virtual SQL Server instance using the 'nsrsqlsv' command line syntax in NetWorker. It explains that the save set name cannot include the instance name when backing up a clustered SQL Server. It provides an example of the correct syntax to use -A to specify the virtual server name and use MSSQL without the instance name in the save set.

Uploaded by

jyxg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
517 views3 pages

NMM NSRSQLSV Syntax For An SQL Server Cluster Instance

This document discusses how to backup a clustered virtual SQL Server instance using the 'nsrsqlsv' command line syntax in NetWorker. It explains that the save set name cannot include the instance name when backing up a clustered SQL Server. It provides an example of the correct syntax to use -A to specify the virtual server name and use MSSQL without the instance name in the save set.

Uploaded by

jyxg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

NMM: 'nsrsqlsv' syntax for an SQL Server Cluster Instance

�� Prajith �� 2014-10-1 ����2:20 �ϴ���������� vipin_joy �� 2014-10-7 ����6:16 ���޸�


�汾 2
Environment:
Microsoft Windows 2008 or above

Microsoft SQL Server 2005 or above

NetWorker Server and Client 8.0 or above

NMM 3.0 or above

Description:
How to backup a Virtual SQL Server using NMSQL or NMM SQL VDI command line syntax
or 'nsrsqlsv'?

Command line syntax fails for 'nsrsqlsv' when performing manual backup of a
Clustered virtual SQL Server instance.

Usage: nsrsqlsv [<options>] {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]] [-a device interface=data domain] [-f


aes] [-w browse] [-y retention]

[[-A virtual-server] | [-c client]] [-a De-duplication backup=yes] [-a De-


duplication node=<Avamar Node Name>] [-a De-duplication client name=<client>] [-f
aes] [-w browse] [-y retention]

[[-A virtual-server] | [-c client]] [-z FEDERATED_SLAVE=true]

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

To use 'nsrsqlsv' in a Clustered SQL Server instance requires specific parameters.


The two most important ones are:

-A virtualservername
Save Set name cannot incldue the Instance name

Wrong Save Set MSSQL$instancename:databasename

Correct Save Set MSSQL:databasename


Resolution:
Cluster setups for the SQL VDI backups using Networker Module for Microsoft (NMM)
or older NetWorker Module for SQL Server (NMSQL) requires the save set name:

MSSQL: * without * the named instance name.

Unlike Stand-alone SQL Server Named instances which require the instance name in
Save set like this:

MSSQL$Instancename:

EXAMPLE:

Virtual SQL Server name = er-sqlvir

SQL Server instance name = sqlvir

Physical cluster node name = er-sqldb1

CORRECT SYNTAX:

nsrsqlsv -b Default -v -s er-bup -A er-sqlvir -c er-sqldb1.dbs.adroot.local


MSSQL:msdb

WRONG SYNTAX:

nsrsqlsv -b Default -v -s er-bup -A er-sqlvir -c er-sqldb1.dbs.adroot.local


MSSQL$SQLVIR:msdb

Reason # Has Named instance in Save Set

nsrsqlsv -b Default -v -s er-bup -A er-sqldb1 -c er-sqldb1.dbs.adroot.local


MSSQL:msdb

Reason # has physical host in �CA

nsrsqlsv -b Default -v -s er-bup -c er-sqlvirdb1 MSSQL:msdb

Reason # has virtual host in �Cc


Reference:
EMC Support Solution Number: 184054

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy