Last year we decommissioned a physical Avamar grid in London because it was both out-of-support and the location was about to close down. The Avamar was however still being used for desktop/laptop (dt/lt) backups. A separate project was taking care of replacing those laptops, but in the meantime we needed to keep the Avamar backup service running.
We did a quick calculation on the required capacity and deployed 4 new Avamar virtual editions in our central VMware farm. After configuring them and connecting them to the Avamar Enterprise Manager dashboard, we were able to move the majority of clients over.
Now, almost a year later, many of those laptops have been replaced and are no longer backed up by these 4 new Avamars. Which clearly shows in the utilization, as you can see. Three out of four systems are <10% utilized. Since these Avamars claim a fair bit of resources from the VMware farm, I set out to consolidate the systems into the first virtual Avamar. Thus, reclaiming 75% of the resources.
Cleaning up old backup clients
First off all, a lot of backup clients no longer exist. To clean up the overview and to get a better sense of the active clients, I started with deleting all clients that haven’t contacted the Avamar systems in the last month. First step is to list all applicable clients. The easiest way to do that is to dive into the CLI and run the following commands:
psql -p 5555 mcdb
SELECT full_domain_name, checkin_ts FROM v_clients where (checkin_ts < ‘2019-05-01’ AND checkin_ts > ‘1970-01-01’) ORDER BY full_domain_name;
You can then exit the psql terminal with \q
Dump this output into Excel or Notepad++ and clean it up until you end up with the client name (e.g. /clients/laptop-1234).
Next, we’re going to delete these specific clients. The CLI command syntax is: mccli client delete –name=/domain/client. Again, you can probably best use Excel or Notepad++ to get the commands sorted. I ‘only’ had 200 clients per Avamar to clean up, so this manual method works reasonably well. If you have thousands of clients to clean up, you might want to make a proper script out of it.
Consolidating clients on the first Avamar
Once all the garbage clients have been cleaned up, the next step is moving clients over to the first Avamar. The EMC Avamar client manager works well here:
Select a few clients on the old Avamar, and click move. Then, select the recipient Avamar and domain, and click Next. In the next screen, select the recipient group. You’ll have an option whether to replicate the existing backup history. In our case, we’ll replicate the existing backups to ensure we can actually restore something if a user deletes everything tomorrow.
Lastly, insert the password for the repluser on both the source and target Avamar. In our case, these are the same. If you lost this password, you can bypass this by NOT replicating existing backups.
Next, track progress either in the client manager, or in the Avamar client itself. Both should show you a number of replication jobs:
Lastly, check whether the move job actually completed correctly:
You will see a few possible outcomes here:
- The client moved successfully. In that case, no further action is required, other than maybe kicking of a manual backup to check everything.
- All move tasks except activation completed successfully. In practice however, this client often activated correctly and a test backup succeeds, so this could be a false alarm. Check for registered (not activated) clients though, and retry activation where necessary.
- Or the client is not on-line and the move doesn’t go through. In that case, the Avamars will not replicate the backup history and the client will remain on the old Avamar. Try again later!
That’s it. Since we cleaned up the old, stale registrations beforehand, any clients that experience problems during the move should pop up in respective client categories. Rinse, repeat and fix issues along the way. Once the old Avamars are empty, decommission them!
My thoughts on Avamar client management
Unfortunately, Avamar does not have a standing “please vacate this Avamar and move to that other one” order. Clients need to be online for these move actions to succeed. With servers, that’s not so much of a problem as they should be online 24/7. Laptops are a bigger problem, as users can have different working hours depending on their geographical location, work schedules and potential holiday absence. In my opinion, this is a major caveat in Avamar functionality.
If you have sufficient time, you could periodically retry these moves over a few weeks. However, there will always be a few clients that can’t be moved because the user is out of office or the laptop is only used for a few hours every month. These clients will have to typically be hunted down by Local IT and migrated manually. Maybe this has been improved in newer versions of Avamar; do let me know if you have better experiences with it!
All in all though: if your clients are online, this process works well. Good luck!