Avamar restores

As long as the systems have different DNS names, you will be able to restore the previous backups. In order to restore from the old grid, you will have to temporarily activate the client back to the old grid.

If the client accounts are being migrated using root-to-root replication (regardless of whether the backups associated with the accounts are replicated), the client IDs (CIDs) for the clients will be preserved and you will just have to reactivate the client back to the old grid to perform a restore. The exception to this rule is that CIDs for clients activated in the root domain (the / domain) are not preserved during migration so if you have any clients activated in the root domain, be sure to move or retire them before the migration.

If instead the clients are just being activated to a new, clean system, in order to recover a backup from the old grid, you will have to activate the client back to the old grid, then perform a redirected restore. In this case, you might be better off retiring the clients on the old grid once the new system is up and running because Avamar forbids duplicate client names. Retiring a client will append the date it was retired to its name which will prevent the conflict. You could also set up a specific domain for activating clients you need to restore to avoid the name conflict, or change the MCS configuration parameter "allow_duplicate_client_names".

To change the configuration parameter, log into the Avamar server as the admin user, make a backup copy of the file /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml, edit the file to change the configuration parameter from false to true, then restart the MCS by running:

dpnctl stop mcs dpnctl start mcs

Please be aware that restarting MCS will clear the GUI's activity monitor. If you're not comfortable working with Avamar at the command line, support can assist you with this.