I have basically configured this:

The physical clients are set with saveset All.

the virtual client(Virtual instance) is set with save MSSQL:

backup command: nsrsqlsv.exe -a virtual name.

I have also tried to specify the specific instance after MSSQL but with no luck. My problem is not with the instances but with the virtual server name vs. the physical server name

How is your configuration looks like? All instances are configured as separate NetWorker Clients and in the save set attribute the particular instance is configured for backup from that virtual client?

Jep, everything is setup as you describe in Networker.

best regards

Thomas

I would believe so

on the virtual client I have configured the remote access with

*@physicalnode1

*@physicalnode2

The reason I'm using * is for testing at the moment. When I get it to work I will sort out the specific user. My remote user does have the required permission to backup the databases.

Do you have all those "remote access list" etc. configuration parameters set correctly?

If you bring NMSQL GUI from client, does that work?

I don't have in current env SQL like you to play with it, but top of my head I would suspect first some sort of permissions to be the issue.  When I say that, in first place I suspect user (SYSTEM user for scheduled backups) does not have permission to connect (and browse) instances.  Not sure which user you used from client side (was it SQL admin?), but same might apply.  I didn't check docs recently, but in the past I believe some permissons were required and those were documented as well.  Could you verify that please?

Yes, it connects but shows me the "wrong" instances. It shows my the physical server name / instance instead of instance / instance. When I try to connect if fails with the above mentioned error messages

Hello,

it's an old topic, but I have the same problem.

MSSQL 2008R2 on Windows 2008 R2 active/active cluster with different instances.

The NW server scheduled backups of the instances are running well. One client resource for every instance.

Saveset MSSQL: and Backup command nsrsqlsv -a .

Remote access *@ and *@.

But when I start the NetWorker User for SQL Server and choose the SQL instance I want to work with I'm getting the error messages:

The user I'm connected with the server has sysadmin rights on the databases.

Unfortunately i don't remember the solution and I should have updated this string with the solution. I guess you are trying to run the NMSQL client from the client in the above screenshots. Have you tried to switch of UAC in Windows or try to run the NMSQL as Administrator?

Yes, I've tried to run the NMSQL as Administrator.

We cannot switch of the UAC because we cannot reboot the server at this moment.

The strange thing is that the instance name in the "Select SQL Instance" window seems to be wrong.

It shows me \ but ist should be \ .

Hello Daniel,

Have you tried adding *`@* to all the nodes? This test will determine wether this is permissions related or not.

Also, have you created a client entry per SQL instance?

I would suggest to create one client per SQL instance as follows:

Client for inst1

Client for inst2

Client for inst3

Client for inst4

Thank you.

Carlos.

What user are you loged in as? Did you use a SQL admin to login on to the SQL server and then mopen NMSQL?

What do you have in the list of NW admins in NMC?

Thank you.

Carlos.

I've tried with SQL service user (domain user), lokal admin and own domain user. All users have sysadmin rights.

I've added the physical hosts to the administrators list in NMC... doesn't work.

Hello Carlos,

do you mean adding this to the Remote Access field?

I've added this to all nodes (physical and virtual) but it did not help.

Yes, I've created one client per SQL instance.