Virtual client create problem with Networker 7.3.2

Question

I'm trying to create a virtualclient and new networker gives
me error

"An alias of this client is already an alias for client
This is not recommended
Re-apply only if client is in a cluster configuration"

Now where I can re-apply ? Just pressing OK and OK again
won't help.

amediratta · Accepted Answer

Update your /etc/hosts & DNS with an entry for the Virtual Client. Test ping this. Recheck all physical client resources, they are having the virtual name somewhere in the network. Check IPs for them as well.

Then try and create the client resource for the virtual client.

ble1 · Answer

Do you have physical clients defined? What are their names and aliases defined? Then what is the name and alias defined of virtual client?

amediratta · Answer

One of the physical client resoruces defined by you would be having the virtual client name as Aliases.

Also check if your /etc/hosts have the virtual client name against the IP of one of the physical client.

Piippu · Answer

Physical node's name aresaps001.ad1.internal (alias saps001 and saps001.ad1.internal)saps002.ad1.internal (alias saps002 and saps002.ad1.internal)Virtual node I'm creating has namesaperpdb.ad1.internaltried with aliases saperpdb, saps001.ad1.internal, saps002.ad1.internal, saps001, saps002. Also tried without aliases ...Message was edited by: Timo Piiparinen

Piippu · Answer

I've got both physical cluster node's configured.

Backup of physical cluster node's works ok.

Adding virtual name (IP is in DNS and I've also used local hosts file)
gives that error. It says that I should re-apply if it's a cluster node but
there's no re-apply button, just OK. If I press OK and OK to
're-apply' changes I get same error again. So I'm in loop
of OK's.

ble1 · Answer

Virtual name should have no aliases of physical ones.

Physical clients should be defined before you try to create virtual one.

If on UNIX, run networker.cluster script before running the backup of virtual one.

Virtual one should have both physiscal ones in remote access list.

Above would would be correct NW part of configuration. You may wish to insprect name resolution as well as Anuj already suggested just to make sure that something from physical world is not defined in virtual one.

Piippu · Answer

My problem was that Networker server connected via public IP to
cluster where networker server was defined in hosts file with
Backup network address. This lead to probe job failure,
which I tried to correct by setting cluster name into
Networker hosts file with physical node's backup network
address, which lead that I couldn't create virtual client
since physical node had already same address and
it was defined as client.

So resolution was:
- removed all entries from hosts files -> could create virtual client
-> connect to client goes through public network but when I
have Networker servers backup network defined in client
attributes, backup data goes through backup network.

NetWorker

Virtual client create problem with Networker 7.3.2

Was this post helpful?