user_feo! wrote: Restarted the services by running this command:    dpnctl stop   dpnctl start   dpnctl status  | Run this to check that all services are in good order. NOTE:  Stoping and starting the services can take while.

If you are going to restart all the system services, it's always a good idea to take a checkpoint using mccli or the Avamar Administrator GUI before you do so. Since this was just an MCS configuration change, it probably would have been better to use dpnctl stop mcs and dpnctl start mcs instead of shutting down everything. An MCS restart is also significantly faster than restarting all the services.

Could you clarify what you mean by agentless? This could mean differrent things in different contexts.

Thanks Anderson for the reply.  It is in the context of adding vCD vApp VMs using Avamar proxy.

Adding clients under the vCenter configures them for image level (agentless) backups. The procedure for configuring VMware image backups is documented in the Avamar VMware guide.

I don't think I've understood the question.

Then how do I backup the machine at the image level using Proxy from Avamar Admin Console GUI and from MCCLI?  After adding the vCenter I can browse to all the vCenter VMs in the Avamar GUI and be able to add if it is not added already.  For image based, how would I add a machine irrespective of whether it is added at Agentbased level or not?

If you backup a VM using VMWare plugin, you shouldn't need to install the Avamar Client inside the VM.

In some cases, you need to protect also applications inside the VM, like SQL. In that case, you must install the client inside the VM, activate with the server and configure the backup (you don't need filysystem backup here, only the application).

Using the default configuration, Avamar Server will not allow activation of the client within the VM because there's a machine activated with the same name (inside the vcenter domain). You must enable "allow_duplicate_names" to be able to activate the machine.

Open with a text editor mcserver.xlm (/usr/local/avamar/mc/server_data/prefs/mcserver.xml)

find "allow_duplicate_names". Change from "false" to "true"

Restart mcs service (dpnctl mcs restart)

The full process is discribed in "Avamar for VMWare". Take a look.

You do not need to set allow_duplicate_names unless the clients will be activated into the same domain.

admin@testgrid01:~/>: mccli client add --name=clientA --domain=/clients 0,22210,Client added Attribute Value ------------------------------ ---------------------------------------- clientid 149347c646d903c0306e0fb7ce33c36fd2e254ab fullName /clients/clientA admin@testgrid01:~/>: mccli client add --name=clientA --domain=/ 0,22210,Client added Attribute Value ------------------------------ ---------------------------------------- clientid bd4ce86fe9ad3d845f30dc368603550c36185dc2 fullName /clientA admin@testgrid01:~/>: mccli client add --name=clientA --domain=/clients 1,22238,A client with this name already exists and duplicate names are prohibited. Attribute Value --------- ---------------------------------------------------------------------- data      ERROR: Host named: (clientA) is already registered as /clients/clientA

Thanks Anderson for the info.  I think I am getting to it now more closer.

I have two independent  vmware environments with two vcenters and two avamar proxy servers. When registering virtual machines for image level backup (Import Multiple Clients) I cannot add servers with the same vmware name although they are in different vmware vcenters. When one of them is registered the other one is grayed in Select Virtual Machine. I set allow_duplicate_client_names option to "true" but that didn't help.