NW 8.0 SP1 NMM2.4 trying to backup SQL2012 Read only DB failng

Hi Deepu83,

Can you upload nsrsqlsv.raw on this topic, or cut/paste messages only that are relevant to this case from the same log file nsrsqlsv.raw?

Have you followed official EMC documentation "NetWorker Module for Microsoft Application 2.4 - Application Guide", Chapter "Microsoft SQL Server VDI Backup and Recovery" section "Configuring scheduled backups" ?

Hi
This is the error we are geting on the group side  when i run a SQL read only side of DB

43708:(pid 6672):Start time: Tue Feb 26 17:58:45 2013

43621:(pid 6672):Computer Name: XXXXX     User Name:XXXXX

37981:(pid 6672): Cannot connect to resdb database: Program not registered

85555:(pid 6672):Unable to fetch Application Information from resdb database

29336:(pid 6672):Cannot connect to resdb database

43709:(pid 6672):Stop time: Tue Feb 26 17:58:46 2013

NSR info 59 Unable to fetch Application Information from resdb database 0

NSR critical 36 Cannot connect to resdb database: %s 1 24 22 Program not registered

Thank you.

Try to remove that backup client and add it again using New client configuration wizard. If you exit from that wizard without any errors, backups should be fine.

Obviously you seem to have permission issues. Can you connect to that database in SQL Server 2012 Management Studio using the same user that you are using in backups?

Hi

I had issues when backing up SQL 2012 with NW 8.0SP1 and NMM2.4

Cannot remember if it was the exact same issue as you have, but here is what solved my issues:

Specify user and password in clientconfig in Networker

Then open secpol.msc on client and:

1. Navigate to Local Policies -> Security Options.
2. Change "User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode" to "Elevate without prompting".
3. Disable "User Account Control: Run all administrators in Admin Approval Mode".
4. Restart the machine.

Hi Deepu,

Please note that for SQL 2012 you need to set a user within the remote user. Please refer to the documentation for further information about permissions requirements.

Disabling UAC would also help.

About recreating the client, please be careful, as if you use the client wizard it will either fail, or will create it with a new client ID, and that will introduce much more issues in the future so, if you have the client already created I would say avoid to recreate it, unless you write down the client ID first.

Is this a cluster environment? If it is NOT try using nsrsqlsv -c client_name instead.

Is the client created with short name or FQDN? If shortname I would recommend you to do as follows:

1.- Write down the client ID of the shortname client

2.- Delete all instances of that client

3.- Manually (not using client wizard) create the client again with FQDN and same client ID as you have previously on the shortname client entry.

4.- If you get a pop-up message saying that client FQDN already exists with client ID xxxxx then write down that client ID from the message.

5.- Create the client with FQDN with the client ID you wrote down form the pop-up message

6.- Create a dummy client for the shortname client with the client ID of the shortname client, but uncheck the box of "scheduled" backup so that you don't have problems with the name resolution (call it for instance dummy-shortname).

This should fix all the issues related with configuration and client ID's.

Thank you

Carlos.

Hi Carlos

Here is what i am trying to backup  on SQL  2012 DB side using VDI

Windows cluster name -AB

Nodes A , B has primarySQL DB and CD(Read only Secondary replica DB server)

Setting and properties of CD server-

Group-Snapshot-Not enabled

advance tab-restart windows;00:01

client retires-0

savegrp paralle-0

Client properties-backup type-sql server

client direct-enabled

directive -None

saveset-MYSQL:

group-DB group

pool-datadomain

schedule-DB

remote user-sysadmin(which is windows admin and sql admin account)

password-password

Backup command-nsrsqlsv –A SQLDBname

application inofrmation-Nothing

dedup-datadomain

globas1of 2 -All alias

Globas 2 of 2-storagenode-nsrserverhost

error-

Computer Name: CD

User Name: xxxxx

37981:(pid 5856): Cannot connect to resdb database: Program not registered

85555:(pid 5856):Unable to fetch Application Information from resdb database

29336:(pid 5856):Cannot connect to resdb database

43709:(pid 5856):Stop time: Wed Feb 27 18:04:34 2013

Please advice me any onfiguration changes to make this backup run

Thank you.

Deepu,

Have you tried to connect to that database by means of SQL 2012 Studio, using the same user as you are using for the backup?

Carlos,

This is command that I use:

nsrsqlsv -A virtual_node_name  (not SQLDBname)

Capital A!

Hi Deepu,

Have you tried as Zlatko said?

Also I think you have the wrong backup command:

nsrsqlsv –A SQLDBname

The command should be as follows:

nsrsqlsv -a virtual_node_name

You don't have to set the SQL DB name in the backup command.

Also, have you created a client entry in NW for PnodeA, PnodeB and Vnodes as well? (P=Physical, V=Virtual).

Have you tried to run this command from NW server?:

rpcinfo -p virtual_name

rpcinfo -p PnodeA

rpcinfo -p PnodeB

Thank you

Carlos.

Hi Zlatko,

You are right, my mistake. It is indeed -A

Deepu, you NEED to install NW client and NMM in all the physical nodes of the cluster, otherwise you will never be able to back this up.

Please try this command:

nsrsqlsv -A virtualSQLserver

If it still doesn't work give a try to this other command:

nsrsqlsv -s servername -A virtualSQLserver

Also note that the client entry for the virtual name has to be created with shortname and not FQDN.

Ensure that you have set, in the remote access field the following:

Option 1 (less secure):

*@*

Option 2 (more restricted):

*@PnodeA

*@PnodeB

*@Vnode

Also ensure that you have configured the remote user name and password with a user with enough privileges.

By the way, I need to double check if RO DB's are supported or not, if I remember well I think that the remote copies of the DB is not supported but only the production DB's to be backed up. I'll get back to you shortly.

Thank you.

Carlos.

Hi Carlos

Thanks a lot Carlos and Zlakto

Atleast i am able to run manuals from client side using the same user id (which i used in remote user id place backup did complete)

Issue with the schedule backups only

I am login as administrator to NW server and starting a test DB backup do i need to login as the same user id i am using in client properties to make this DB backup work?

2. I do have windows cluster (Vnode name,PnodeA,pnode B,pnodec)

Sql clusters are (Pnodea and Pnodeb where as Pnode c is stand alone DR,read only DB server since its a SQl 2012 )hadron environment

i configured standalone Db backups and manula from client side is running but schedule is failing with

Computer Name: xxx

User Name:xxxx

37981:(pid 2572): Cannot connect to resdb database: Program not registered

85555:(pid 2572):Unable to fetch Application Information from resdb database

29336:(pid 2572):Cannot connect to resdb database

43709:(pid 2572):Stop time: Thu Feb 28 15:49:04 2013

3- i am not able to configure DB backups to Pnode a nor pnode b nor vnode how can i do that ?

When i try to use client configuration its not going farword after i pick SQL on those server

Can you guys help me.

Thank you