MS Cluster clients filesystem backups are failing

[JohnPlayerSpecial]

Hi,

This problem started week ago. Before that backups were running normally without errors. All the SAP backups are running normally. Problem is on the both cluster nodes.

I have checked the normal "connection refused" checklist: Services, name resoluiton and ports but everything is as it should be. Lisencing is ok.

Platform:

Clients:Windows 2003 Enterprise SP1, MS Clustered. Networker 7.21 client+SAP/R3 module 3.02

Server: Solaris 9 with Networker 7.22

This is what is on the client side daemon.log

12/11/06 13:31:28 nsrexecd: SYSTEM error: Software caused connection abort

... and this is what is on the server side daemon.log

* b-xxxsapr3p01:C:\ 12/10/06 11:06:37 nsrexec: SYSTEM error: Connection refused
12/10/06 11:06:37 savegrp: b-xxxsapr3p01:C:\ will retry 1 more time(s)
12/10/06 11:06:37 savegrp: command 'save -s backup3 -g Windows_filesystem -LL -f - -m b-xxxsapr3p01 -l full -q -W 78 -N H:\ H:\ ' for client b-xxxsapr3p01 exited with return code 1.

 

[NWNinja]

Hi John!
You should check that the NetWorker services on the client are running with a user that has sufficient privileges to the filesystem.

Also, are you using DNS or hosts files for the name resolution? If you are using DNS, please verify the name resolution using nslookup from client to server and server to client. Make sure that the responses are correct, and that the servers file on the client contains both short and FQDN name for the backup server. And check that the Aliases attribute on the client definition contains the short and FQDN name of the client.

If you are using hosts files, please check those and make sure they contain the correct info. Is there a firewall involved by any chance?

Cheers!
Maverick

 

[JohnPlayerSpecial]

Hi,

We are using host files and I have checked those several times. Also services are ok.

These backups were running normally like two months and suddenly started to fail. Strange thing is all SAP DB backups are succesful, so this problem only affects filesystem backups.

 

[605]

As NWNinja explained already - have a look at your file /nsr/res servers. Correct it and restart the services.