How to enable multiple activations for single machine (Agentless and Agent based)

Hello Ian, I am having the same challenge where I cannot add a VM that was added with the agent (see error attached).  Can you please let me know what the commands are to enable the "allow_duplicate_names" options, and how to add a VM client via the mccli?

The domain name specified in avregister should not have a leading slash.

Ian, thank you!! All good now ... Here are the details on  the fix.

Modified this guy: /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml

This line: 

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. 

Once the services restarted, I was then able to the following command and it actually worked:

mccli client add --type=vmachine --name=VM_Name --datacenter=My_DataCenter --domain=/My_VCenter_Domain/VirtualMachines

After this though I was not able successfully run backups on these all VMs related to this VCenter.  It just sat there with a status "Waiting for client".

I may have taken the long route, but ultimately what did the trick is to delete the proxy and re-register it to the Avamar server.

Here is what I did for troubleshooting steps:

1. Re-synced the VCenter server in Avamar GUI | No luck
2. Deleted all VMs and VCenter Server (Domain) - I had to deleted and recreate the backup policy.
3. I re-added the VCenter Server and its VMs, re-create the policy. | No luck

Finally this is what got it working.

1. Deleted all VMs and VCenter Server (Domain) - I had to deleted and recreate the backup policy.
2. I re-added the VCenter Server.
3. I deleted the Avamar Proxy and re-registered.  I logged into the proxy and ran the following command:  /usr/local/avamarclient/etc/initproxyappliance.sh register

  Just follow the prompts.

4.     I re-added the VMs that needed protection.

5.  Re-created the policy.

6.  I ran a test job on one of the VM and SUCCESS!!

IMPORTANT:  If you run into this issue after modifying the "allow_duplicates..." option .  I would just delete the proxy from the /clients domain and register.  I bet that was all I had to do. Good learning experience though.

Thanks for the guidance!!

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.

Agreed!  Take a checkpoint, in case you need to revert back.  In my case, I stopped all services since, dpnctl stop mcs was giving me an error.  Thanks again for the help!

Hello Ian, its is posible to register an avamar client , with multiple avamar servers?, or a way to make this process possible, we have a custumer that has backups with an avamar server , and algo does backups with an avamar with datadomain integration, at the moment they have to register manualy the agent each time to store the backups on both systems, replication from one to another could be an option but then they will have to buy a datadomain on the site that has a single node of avamar.

Best regards

Thanks Ian.