Sometimes this error could come if Aliases field is not properly updated for the client. Aliases should have the hostname, IP & FQDN for the client.

Check aliases and also update the hosts file on both the server & the client with IP, HN & FQDN of each other.

If this does not work, post the exact error you are getting.

From what you have said you do not get any error which may indicate that:
a) client is busy preparing VSS snapshot
b) firewall is blocking connection

I would suggest in future to use NetWorker forum instead of lite users area - I assume you are EMC user and as such you can access those areas.

I've moved this thread from the Lite Users area to networker forum, thanks Hrvoje - I was unsure about what product this one would be.
Julie
Forums Admin

Getting an error like " Backup group contains no enabled clients , Enable one or more clients then restart the backup operations " .
But i configured correctly , the same configuration works on linux . Kindly help me out .

What NW version are you using and what are the OS for the backup server and the client? If it is Linux server and windows client with pre-NW 7.3.4, you need clientpak license.

This error could also come if you have added the client in the group but not check marked on the scheduled option for the client in the group.

Please check. I would still recommend running save -s command from the client to help get a clearer error message.

As Julie suggested, mark Correct/Helpful to response that you get so that we know we were of any help to you.

Looks like you haven't enabled the "scheduled backup" check box in your client configuration. That's why you would get the message "Backup group contains no enabled clients ...." Check the "scheduled backup" check box for the client and retry your backup

And also an another error i am getting is , 39078:save: RPC error : program not registered . while executing save -s command

Sounds like your server is not able to resolve that IP. Place it into local hosts table.

The next thing you should do is to make sure that your hosts file is updated with IP, hn & fqdn. On client, have the entry for the server. On server, have the entry for the client. Aliases filed in the client resource should have all three for the client and Server Network Interface field in the client resource should have either of these three.

Basically, you are not able to resolve the hostname. NW first checks on the hosts file and if the tnries are there, it should be able to resolve and backup else you need to get your network people involved and see what is going wrong on the DNS level.

The Networker Version is 7.4 and the error which i am getting while executing save -s command is IP address for he host could not determined through DNS .

But if i run from the Networker user , i can able to take a backup .

I missed on the fact that Networker user is able to run the backup. Check when you open Networker user, it shows the hostname or fqdn if the server in the bottom strip of the screen. Use that in save command. What you are currently using in save command is what is not getting resolved. Please check.

You did not tell the NW server version. sve command is the manual backup command from the client. It is run as :

save -s backupserver C:

where backupserver is the hostname of the backup server & C: is the folder you want to backup. You can alternatively use Networker User also. Open, Click at Backup, select a folder and Start. save.exe would exist in the bin forlder of the client folder installation path.

I am usinf SUSE enterprise as a Networker server and installed the client int he linux and as well as Windows , From the networker i can able to take a backup of linux client but not the windows and fromt eh windows client if i give the bcakup form windows not from networker , it is taking backup .
And sorry you said to run save -s command , I am not aware of that , Can you explain me that .

Thank You Friends for your help , The problem got resolved , What happened was as you said it was the hostname entry problem , Infact i changed the hostname and made an correct entry but still the networker taking the old entry becuase the entry was registered in the windows registry , What didi i done is i just uninstall the Netwoker client and reinstall and made all teh changes , then it is working fine . Still now i didnt get any problem ,hopefully this problem wont come further . Once again thanks to all . If any other problem i faced , i will let you know