I'm having some difficulties in setting up the NMSQL 5.2.1 in a SQL 2008 active/active cluster running on Windows 2008 R2. I have several differrent instances running in the cluster where none are the default instance.
Just to give a brief description this is how the setup is:
2 x physical server
4 x instances
I'm no MSSQL wiz but I guess that a cluster configuration in SQL 2008 is still server\instance, but the difference is that each instance is like a virtual machine. So basically inst1(server)\inst1(instance)
The problem is when I try to connect with the SQL module I can only choose instances where it is the physical server\ instances name. In my example
When I try to connect through the SQL module to one of the connections I get tons of errors saying that I'm trying to connect to the wrong instance and no connection can be established.
"These are the error messages I'm getting
38006:nwmssql:SQL Server Network Interfaces: Error Locating Server/Instance Specified[xFFFFFFFFFF]
38006:nwmssql:A Network-related or instance-specific error has occured while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. "
The servers are setup for remote connections. The problem that I see here is that Networker cannot see my instances running on the server. It's like I'm not getting the correct information into the NMSQL GUI regarding instances.
Has anyone seen this before??
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?
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
I would believe so
on the virtual client I have configured the remote access with
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.
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
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?
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 <virtual server>.
Remote access *@<cluster1> and *@<cluster2>.
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.