If Second DataDomain is going to be attached to the existing Avamar System then you will have to go through the route of deleting the Cache files for you too perform a Full backup.
If it is going to be a new Avamar+DataDomain system then you can choose the migrate one backup from the existing setup to the new setup.
If the new DD is completely unused, you can do a collection replication from the current DD to new DD, then do a DNS name swap, where the new DD assumes the name of the old DD.
Avamar creates a unique mtree (using it's System ID) on DD when you first configure a DD as a target. This mtree name must be preserved moving forward.
gautamgp
226 Posts
0
April 28th, 2016 20:00
If Second DataDomain is going to be attached to the existing Avamar System then you will have to go through the route of deleting the Cache files for you too perform a Full backup.
If it is going to be a new Avamar+DataDomain system then you can choose the migrate one backup from the existing setup to the new setup.
frank_grimes
5 Posts
0
April 29th, 2016 05:00
Would that still be the case if we did DD MTree replication to the new DD then updated the DD in Avamar to use the new FQDN?
umichklewis
3 Apprentice
•
1.2K Posts
0
April 29th, 2016 09:00
If the new DD is completely unused, you can do a collection replication from the current DD to new DD, then do a DNS name swap, where the new DD assumes the name of the old DD.
Avamar creates a unique mtree (using it's System ID) on DD when you first configure a DD as a target. This mtree name must be preserved moving forward.