The virtual client should not use a NetWorker cluster client connection, but I have seen cases when this happens. I have also seen that just entering all the virtual clients and the physical nodes on both physical nodes /etc/hosts file seems to resolve this issue (regardless if DNS seems to be working fine).
So my suggestion is, repeat the same procedure you did about deleting and recreating the physical and the virtual clients, and update the /etc/hosts files for all physical nodes with the virtual client and the physical clients.
To make it work you must make sure that both server and client in cluster are on 7.4SP2. Otherwise (in mixed cases) you won't see it working - at least that was what I saw.
Delete all the licenses applied and reapply them, this should fix your problem. For deleting the licenses you can follow the standard document available or else for your reference:
1. Stop networker services 2. sudo /usr/sbin/nsr/nsradmin -d /nsr/res/nsrdb (Path may vary depending on OS type) 3. . type: nsr license 4. delete
Note: before deleting the licenses pls note them as you will need to reapply them.
nsoto
16 Posts
0
August 25th, 2008 13:00
So my suggestion is, repeat the same procedure you did about deleting and recreating the physical and the virtual clients, and update the /etc/hosts files for all physical nodes with the virtual client and the physical clients.
equintana2
38 Posts
0
September 1st, 2008 08:00
I have done it but this isn´t ok. do you have another workaround?
Regards
Edgar
ble1
4 Operator
•
14.4K Posts
0
September 9th, 2008 00:00
mridulsingh
41 Posts
0
September 9th, 2008 08:00
Delete all the licenses applied and reapply them, this should fix your problem. For deleting the licenses you can follow the standard document available or else for your reference:
1. Stop networker services
2. sudo /usr/sbin/nsr/nsradmin -d /nsr/res/nsrdb (Path may vary depending on OS type)
3. . type: nsr license
4. delete
Note: before deleting the licenses pls note them as you will need to reapply them.