Also try running savefs -p  command on both client and provide me with the output you get.

Check if you have an issue with name resolution, can you check forward and  reverse lookups on both client and server (both short name and FQDN)

Additionally, run the command rpcinfo -p clientname , from the backup server to the clients (FQDN and short name) as well as from the clients to the backup server.

Finally check if there is any alias missing either in the hosts file or in the client resource configuration.

Waiting your updates.

Thanks,

Ahmed Bahaa

Hi moin,

Sorry i didnt get what you mean by "Server1v.net is the virtual name of server1n.net and both's IP are diffrent." Is that mean physical and virtual (Cluster scenario ) or you mean physical machine and VM machine.

Are they backing up the same machine, but this machine is multihomed NIC , where there is two IP addresses configured on it ?

Would you please clarify more the configurations , but mainly it seems to be name resolution issue or communication , but i would like to understand firstly the configuration of the two servers and the relationship between them.

Thanks,

Ahmed Bahaa

Hi Moin,

I think the main problem here is the configuration.

It's important that you understand how NetWorker works with clusters, and for that I would recommend you to take a look at the Cluster Installation guide:

     Home >               Support >               Technical Documentation and Advisories >       Software ~ J-O ~ Documentation >               NetWorker Family >               NetWorker >          7.6 & Service Packs

NetWorker 7.6 Service Pack 2 Cluster Installation Guide

Here you will find information about how to install the software and how to configure clustered clients in NetWorker.

Please follow those steps and if you have any further question or issue let us know.

Thank you.

Carlos.

Server1v.net

Server1n.net

Yes it is  the Cluster scenario.

Server1v.net   Virtual server

Server1n.net   Physical Node

Savefs -p from Virtual server:-

C:\>savefs -p 77592:savefs: 'NSR client' resource named 'Server1n.net' not found.

7185:savefs: cannot retrieve client resources

Savefs -p from Physcial node server:-

C:\>savefs -p 77592:savefs: 'NSR client' resource named 'Server1n.net' not found.

7185:savefs: cannot retrieve client resources

forward and  reverse lookups on both client and server are checked it is ok.

rpcinfo working fine:-

bash-3.00$ rpcinfo -p Server1v.net   

program vers proto   port  service    

100000    2   tcp   7938  portmapper    

100000    2   udp   7938  portmapper    

390436    1   tcp   9121    

390435    1   tcp   9626    

390113    1   tcp   7937  nsrexec

bash-3.00$ rpcinfo -p Server1n.net   

program vers proto   port  service    

100000    2   tcp   7938  portmapper    

100000    2   udp   7938  portmapper    

390436    1   tcp   9121    

390435    1   tcp   9626    

390113    1   tcp   7937  nsrexec

Alias in the client resource configuration is ok.

Finally check if there is any alias missing either in the hosts file, >>>added hosts entry and tried to take test backup failed

Hi,

I run the below command.

bash-3.00$ /util/bin/sudo savegrp -pv -c Server1v.net adhoc

32451:savegrp: Server1v.net:All level=full

7235:savegrp: Group will run up to 12 jobs in parallel

32494:savegrp: Server1v.net:probe started

savefs -s "BACKUP SERVER NAME" -c Server1v.net -g adhoc -p -l full -R -v

77561:savegrp: command 'savefs -s "BACKUP SERVER NAME" -c Server1v.net -g adhoc -p -l full -R -v' for client Server1v.net exited with return code 1

77562:savegrp: job (2261075) host: Server1v.net savepoint: Server1v.net:All had ERROR indication(s) at completion 77567:savegrp: adhoc * Server1v.net:All  See the file /nsr/tmp/sg/adhoc/sso.Server1v.net.mFaisi for output of save command.

7341:savegrp: Server1v.net:All failed.

7076:savegrp: --- Probe Summary ---

Server1v.net:All level=full, dn=-1, mx=0, vers=pools, p=1

Server1v.net:All level=full, pool=gold, save as of Wed Mar 28 13:47:49 2012

Server1v.net:index level=full, dn=-1, mx=0, vers=pools, p=1

Server1v.net:index level=full, pool=index, save as of Wed Mar 28 13:47:49 2012 7241:savegrp: nsrim run recently, skipping

Also please provide me the log file output of the following commands:

savegrp -D9 -c Server1v.net adhoc > debug.log

You can attach it here.

Thanks,

Ahmed Bahaa

Hi Moin,

Try to do the following from the backup server to the networker client ( using short name and FQDN name):

• check hosts-file if you can find the client
• ping
• nslookup
• rpcinfo -p

  If this all works perfectly and resolution is good, try to do the following from the client to the backup server ( using short name and FQDN name): 

• check hosts-file if you can find the backup server
• check server file under the nsr directory if the backup server is added there
• ping
• nslookup
• rpcinfo -p

Thanks,

Ahmed Bahaa

Hi,

First thank you very much for reply

savegrp -D9 -c Server1v.net adhoc > debug.log

Above command ouput are attached

I rechecked all below conditions/output are correct:-

networker client ( using short name and FQDN name):

•check hosts-file if you can find the client

•ping

•nslookup

•rpcinfo -p

backup server ( using short name and FQDN name): 

•check hosts-file if you can find the backup server

•check server file under the nsr directory if the backup server is added there

•ping

•nslookup

•rpcinfo -p

Hey Moin,

You are talking about a cluster, but only about one physical node and one virtual node, isn't there a secondary physical node? Otherwise I don't really understand the "cluster" concept in this scenario.

Is it MSCS or Load Balancing?

If it's MSCS cluster, I would like to know why would you like to backup the virtual node instead of the physical nodes. When running backup with saveset "All", the active node owning the clustered disk should be backing up the clustered disks, so no need to backup the virtual node.

Anyway we should know a bit more about the IP/NIC configuration in this environment.

Have you tried to add the IP to the alias field, apart from the short names and FQDN in both, physical and virtual nodes?

Thank you.

Carlos.