I run the exact same scenario. I have a local Avamar Grid and Data Domain...I replicate Data Domain data only to a remote site and have 4 data streams. Just have to configure it in your Replication tab...but be careful with how you attach drives to the servers you backup if you have any storage limitations anywhere. It is easy to forget and attach a NAS to a server (or have someone else do this) that is backed up and replicated...Avamar will see this data and back it up and then replicate it...this is an easy way to fill up a Data Domain by accident. (my remote Data Domain is much smaller and has a shorter retention rate than my local Data Domain so that is part of the reason this is a concern for me).
Do you have simultaneous site to site replication running? I’m looking to have my current replication continue to replicate to my existing remote site data domain, and also have a second replication to my new data domain on my remote site, this will replicate new clients as I add them. I’m not completely sure if just creating a new storage mapping and map to the new Data domain will suffice
That is exactly what I'm trying to figure out sconstable... The Gui doesn't specify but the in Avamar guide it states that the setup is feasible.I want existing clients to continue to replicate to DD 1 on the destination and the new clients go to DD 2 on the destination. Wondering if there is some cli commands that can be utilized to accomplish this. Anyone tested this?
Was any one able to configure many to many replication for avamar dd to destination avamar dd i have the same situation for configuration , my avamar code is avamar 7.1 ?
I read this below , but the process is not very clear , esp the NOTE
If there are multiple destination Data Domain systems, you can control which system receives the data that replicates from the source Data Domain system. To specify the destination Data Domain system, map a domain on the source Avamar server to a destination Data Domain system. If you do not provide a mapping, then Avamar replicates the data from the source Data Domain system to the default destination that you identified in “Setting the default Data Domain destination” on page 53.
Note: You cannot map the domains on the source Avamar server to a destination Data Domain system until after the first replication. During the first replication, the data replicates to the default destination.
I was able to get the one to many and many to many controlled replication to destination scenario sorted out .
So , we know avamar has domains for segregating clients . Domain plays a major role in this scenario.
So , when a customer decides to go for one to many or many to many scenario , plan accordingly .
Have customer create custom domains under root domain or Virtual machines domain first , before even adding any clients.
Then add a single client to a domain like Virtual machines and create a replication policy , run that policy on demand.
At the end when the job completes on the destiantion , we can see client has replicated in MC_Replicate >> Vcenter>>Virtual Machines domain . At the same time Avamar will replicate the custom domain structure .
Now in replication in storage mapping , click on add > then select the custom domain and map it to the DD as destination
Do the same steps on either side for Bi directional replication
jpking18
8 Posts
0
April 22nd, 2016 13:00
I run the exact same scenario. I have a local Avamar Grid and Data Domain...I replicate Data Domain data only to a remote site and have 4 data streams. Just have to configure it in your Replication tab...but be careful with how you attach drives to the servers you backup if you have any storage limitations anywhere. It is easy to forget and attach a NAS to a server (or have someone else do this) that is backed up and replicated...Avamar will see this data and back it up and then replicate it...this is an easy way to fill up a Data Domain by accident. (my remote Data Domain is much smaller and has a shorter retention rate than my local Data Domain so that is part of the reason this is a concern for me).
jpking18
8 Posts
0
April 22nd, 2016 13:00
The link between the two sites and the amount of data you plan to replicate will determine if and how you configure this replication.
theone11
1 Rookie
•
10 Posts
0
April 22nd, 2016 18:00
Thank J
Do you have simultaneous site to site replication running? I’m looking to have my current replication continue to replicate to my existing remote site data domain, and also have a second replication to my new data domain on my remote site, this will replicate new clients as I add them. I’m not completely sure if just creating a new storage mapping and map to the new Data domain will suffice
gautamgp
226 Posts
0
April 24th, 2016 09:00
Hi,
you can add both the grids to the replication list and replicate the backups according to your needs to both the grids.
sconstable
60 Posts
0
April 25th, 2016 10:00
I think the original question is what if the Destination had more than one Data Domain, how to you specify:
"These clients go to Data Domain 1 on the destination" and "These other clients go to Data Domain 2 on the Destination"
the GUI is not clear on how to set this up, and I also would like to understand this.
Has anyone done this?
theone11
1 Rookie
•
10 Posts
0
April 25th, 2016 19:00
That is exactly what I'm trying to figure out sconstable... The Gui doesn't specify but the in Avamar guide it states that the setup is feasible.I want existing clients to continue to replicate to DD 1 on the destination and the new clients go to DD 2 on the destination. Wondering if there is some cli commands that can be utilized to accomplish this. Anyone tested this?
rishi.bhaskar
20 Posts
0
August 31st, 2016 19:00
Was any one able to configure many to many replication for avamar dd to destination avamar dd i have the same situation for configuration , my avamar code is avamar 7.1 ?
I read this below , but the process is not very clear , esp the NOTE
Mapping a domain to a Data Domain system
https://japan.emc.com/collateral/TechnicalDocument/docu53942.pdf
If there are multiple destination Data Domain systems, you can control which system receives the data that replicates from the source Data Domain system. To specify the destination Data Domain system, map a domain on the source Avamar server to a destination Data Domain system. If you do not provide a mapping, then Avamar replicates the data from the source Data Domain system to the default destination that you identified in “Setting the default Data Domain destination” on page 53.
Note: You cannot map the domains on the source Avamar server to a destination Data Domain system until after the first replication. During the first replication, the data replicates to the default destination.
rishi.bhaskar
20 Posts
0
September 1st, 2016 10:00
I was able to get the one to many and many to many controlled replication to destination scenario sorted out .
So , we know avamar has domains for segregating clients . Domain plays a major role in this scenario.
So , when a customer decides to go for one to many or many to many scenario , plan accordingly .
Have customer create custom domains under root domain or Virtual machines domain first , before even adding any clients.
Then add a single client to a domain like Virtual machines and create a replication policy , run that policy on demand.
At the end when the job completes on the destiantion , we can see client has replicated in MC_Replicate >> Vcenter>>Virtual Machines domain . At the same time Avamar will replicate the custom domain structure .
Now in replication in storage mapping , click on add > then select the custom domain and map it to the DD as destination
Do the same steps on either side for Bi directional replication