MSSQL backup is failing with SaveFS can not run ;No error

Question

Hi,

The MSSQL backup of DMZ server in Workgroup is failing with Savefs can not run where as the Filesystem backup of the same server is running fine which means the Communication is not a problem.

Secondly we have run Client initiated SQL backup using nsrsqlsv command which is also completing okay. I have verified the permission given in the remote user and has all sysadmin permission & part of local administrator on the server. UAC is disabled.

When I run in Debug and probe mode from the savegrp command then I am getting client exited with return code 76.

11/06/16 10:38:05.058199 -- completion attributes --

completion status: succeeded;

failed clients list: ;

succeeded clients list: XXXXX;

unresolved clients list: ;

warning clients list: ;

11/06/16 10:38:05.089451 --------------

11/06/16 10:38:05.105077 Received job completion attributes message

11/06/16 10:38:05.105077 -- job_compattrs_handler - 350855

completion severity: 50;

completion status: unexpectedly exited;

job output: "Cannot run savefs: No error";

I have tried with all the alias name as well as using backup command nsqlsqlsv -A.

Can anyone please advice what should be done to narrow down this problem as i am getting the same error on the multiple client servers.

Regards

bingo.1 · Answer

I want to argue carefully as we do not use NMM for SQL backups. However I think there is some logic behind my thoughts:

- If the file system backup works for itself, the client is properly configured ... for file system backups.

- If nsrsqlsv from the client runs fine, NMM is also installed fine and working.

This line worries me: job output: "Cannot run savefs: No error";

To me it shows as if you did forget to enter "nsrsqlsv" as backup command in the client resource which is in change of backing up the SQL DB. Only if this is missing, a client would use the standard file system commands (savefs & save) which of course are incorrect if you do an online backup of a database.

ble1 · Answer

Is this cluster?  Does file system backup work ok for it?

mkeil · Answer

Hi,

which ports are open? When using NMM in a firewall environment additional ports are needed:

TCP

6278 (Control port)

6279 (Data port)

You can find this in the Security Configuration Guide.

Kind regards

mkeil

Edit: 6275+6279 are the default ports which can be changed.

BIKU_Tech · Answer

Thanks for your reply. No this is not cluster Standalone DMZ Workgroup server.

BIKU_Tech · Answer

Thanks for your reply. The Required ports are open.

BIKU_Tech · Answer

Thanks for your reply, But command is mentioned correctly.

mkeil · Answer

Hi,

which versions are you using?

Maybe that's an idea:

1. Open the Local Security Policy (secpol.msc) on the client.

2. Go to Local Policies > User Rights Assignment.

3. Ensure that the Windows user or associated group has the Log on as a batch job

privilege.

The user has all necessary permissions (SQL Server, Windows host and NetWorker)?

Have you checked your firewall logs? Maybe there are some other ports blocked.

ble1 · Answer

Is your backup server also in DMZ?  Fact that it can't run savefs may indicate something else.  I also didn't see clear confirmation of file system backup working...

BIKU_Tech · Answer

Thanks for your reply. The backup Server is not in DMZ and Filesystem backup is runing fine

ble1 · Answer

In that case, can you check firewall log to rule out that some funny port is not used and connection dropped?  Since client is in DMZ it is possible that this initial connection is blocked as error is also something that you would get typically under such conditions.

ledugarte · Answer

Maybe you are having trouble with NAT. If your client is in a DMZ, surely there is a NAT and your networker server sees the client with a different IP address.

nmearnsdd · Answer

Had the same issue myself, resolved this by making sure that the client had entries for the nsrserverhost and the storage nodes under the Client Properties Global (2of2) section.

Ran the backup fine after i made this change

NetWorker

MSSQL backup is failing with SaveFS can not run ;No error

Was this post helpful?