SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4

Hello Obesa,

Have you typed the credentials in the "Remote User" field of the clients configuration?

Have you created the client using the NMC wizard or manually?

What is the Application Information field options you have set?

Thank you,

Carlos

Hello Carlos

Thank you for the quick Reply.

>Have you typed the credentials in the "Remote User" field of the clients configuration?

Not yet, but now I will try.

Have you created the client using the NMC wizard or manually?

I installed the Client with the wizard.

>What is the Application Information field options you have set?

Where can I find this information ?

Thank you

Sascha

Von: CarlosRojas

Gesendet: Freitag, 3. Mai 2013 11:08

An: Oberhofer Sascha, FD ICT/IEO/IEN/DBE

Betreff: New message: "SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4"

EMC Community Network

SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4

reply from CarlosRojas in NetWorker Support Forum - View the full discussion

This are the Versions:

Client:

NMM 2.4 SP1

NW80 SP1

Server:

8.0.1.3.Build.155

The nsrsqlsv.raw wasn’t updated.

Von: CarlosRojas

Gesendet: Freitag, 3. Mai 2013 14:27

An: Oberhofer Sascha, FD ICT/IEO/IEN/DBE

Betreff: New message: "SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4"

EMC Community Network

SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4

reply from CarlosRojas in NetWorker Support Forum - View the full discussion

Hi Sasha,

Could you check if the file nsrsqlsv,raw was updated on the SQL server, under /nsr/applogs?

Also, what NW server and NW client on the SQL do you have installed?

Thank you,

Carlos

Hi Carlos

I got these settings in Apps & Modules:

Remote User: domain\admin account

PW: ******

Backup Command: nsrsqlsv –A Servername

Proxy Backup:None

All other settings are empty.

When I run with these settings the backup, I get this error.

Hi Sasha,

For SQL 2012 is mandatory to type the credentials with SQL privileges, it is in the documentation I believe.

The Application Information you can find it in the client, open the properties, and go to "Apps and Modules" tab, then you will see the Application Information field.

Thank you,

Carlos.

Can you please run this command and send me the output? (run it on NW server):

savegrp -D1vvv -c client_name group_name > C:\output.out

Where client_name is the name of the client you are trying to backup and Group name (with no dash in front of it) is the group where that client is included.

Redirect the output of any file in any location and attach the output.

Thank you,

Carlos

Hi Carlos

Here’s the output:

savegrp -D1vvv -c SQLServer.root.Domain.ch > /tmp/output.txt

84078:savegrp: command 'savefs -s NWSServer.root.Domain2.ch -c SQLServer.root.Domain.ch -g Default -p -l full -R -v -F MSSQL:model' for client SQLServer.root.Domain.ch exited with return code 76

90491:savegrp: SQLServer.root.Domain.ch:savefs unexpectedly exited.

90492:savegrp: SQLServer.root.Domain.ch:savefs will retry 1 more time(s).

83647:savegrp: Default SQLServer.root.Domain.ch:savefs See the file /nsr/logs/sg/Default/669093 for command output

84078:savegrp: command 'savefs -s NWSServer.root.Domain2.ch -c SQLServer.root.Domain.ch -g Default -p -l full -R -v -F MSSQL:model' for client SQLServer.root.Domain.ch exited with return code 76

90491:savegrp: SQLServer.root.Domain.ch:savefs unexpectedly exited.

83647:savegrp: Default SQLServer.root.Domain.ch:savefs See the file /nsr/logs/sg/Default/669094 for command output

89713:savegrp: The save set SQLServer.root.Domain.ch:MSSQL:model abandoned because of savefs probe failure.

77562:savegrp: job (669095) host: SQLServer.root.Domain.ch savepoint: MSSQL:model had ERROR indication(s) at completion

90491:savegrp: SQLServer.root.Domain.ch:MSSQL:model abandoned.

7241:savegrp: nsrim run recently, skipping

#

# pwd

/nsr/logs/sg/Default

# ls -ltr

total 12

-rw-rr 1 root root 64 May 3 17:42 669093

-rw-rr 1 root root 64 May 3 17:42 669094

-rw-rr 1 root root 331 May 3 17:43 669096

# cat 669096

86705:save: Successfully established DFA session with adv_file device for save-set ID '2877545198' (NWSServer.root.Domain2.ch:index:ba533543-00000004-517f8d5d-51822016-68ec4a3c-2415f992).

NWSServer.root.Domain2.ch: index:SQLServer.root.Domain.ch level=9, 0 KB 00:00:31 0 files

completed savetime=1367595789

#

Hi Sasha,

I think the problem here is related to name resolution for he virtual SQL name:

Invalid SQL virtual server name servername.

Error code 76 usually indicates that either binaries are missing, don't have set the right permission or that simply cannot find the path for the binary of the command sent so, in this case, as NW is not able to resolve the name of the virtual SQL resource, cannot start the command in this case nsrsqlsv.exe).

Please ensure that name resolution works fine and that the client name specified is the correct one.

Thank you,

Carlos

I'm a bit confused by this output; we are talking about SQL backup, but I see failure for savefs which to my knowledge should be there for SQL backups at all.  I also don't see group name specified (which may explain why Default was used).

Hello Carlos

Still no luck with NMM for Backup the Availabillity Groups.

We will try tomorrow with a new Installation of SQL 2012.

Could there be a problem with NMM on Virtual Machines on VMWARE ?

Von: CarlosRojas

Gesendet: Mittwoch, 22. Mai 2013 15:15

An: Oberhofer Sascha, FD ICT/IEO/IEN/DBE

Betreff: Re: - SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4

ECN

SQL 2012 AlwaysON Availability Groups Backup with NMM 2.4

reply from CarlosRojas in NetWorker Support Forum - View the full discussion

Hi Hrvoje,

Yes, savefs is always ran when there is modules involved.

Sasha, any luck with the SQL backups yet?

Thank you,

Carlos

Hi Sasha,

No problem with VMWARE that I'm aware of.

I think more about a name resolution or configuration issue.

Thank you,

Carlos

Hi Umran,

-A servername is required in virtual environments so that the index get created for the virtual resource rather than the physical nodes.

Thank you,

Carlos

Hi

have you tried removing the "-A servername" from the backup command

try the backup with just the nsrsqlsv command in there

also check if client direct is enabled for the client