If one of those DDs is to be decommissioned, what is a method to move backups already stored on it to any of the other 2 DD systems? (if there is any).
ANSWER: There is no way to migrate backups from one data domain to another data domain while keeping the metadata on the same Avamar server. You could "replicate" the backups to another Avamar server which has the other two data domains attached to it as a work around.
In a different scenario, Can multiple AVAMAR servers write to the same DD system? What can be done to make sure that one AVAMAR server will write data through DDBoost to a different MTree than the other AVAMAR server?
ANSWER: Yes multiple Avamar servers can share the same DD system. When the integration is put in place a unique mtree is created based on the "hfscreate time" (install date in unix timestamp format) of the Avamar system. Each Avamar server will write into its associated mtree and nowhere else.
Does EMC support having the AVAMAR server and the DD system in 2 different sites? connectivity will use dark fiber.
when you say " You could "replicate" the backups to another Avamar server which has the other two data domains attached to it as a work around."
Did you mean replicate to another "Data Domain" through AVAMAR and not to another AVAMAR server...
If that is what you mean then it might be something that I can do, so are you saying that I can replicate all existing backups on the DD in site A to an AVAMAR - Data domain system in site B?
Yes that is what I meant.You can replicate the backups to another Avamar / DD pair either on the same site or on a remote site.
To go even further once replicated to another Avamar / DD pair, you can then replicate them BACK to the original Avamar / DD, but direct the backups to a different DD... I believe that is the only way to achieve what you want to do.
I think original OP was if i have 1 Avamar grid and two DD (let's say DD880 and DD890).
DD880 is coming of maintenance so i buy more capacity for DD890 and now need to migrated the data that was backed up by Avamar from DD880 to DD890. Is that possible ?
There is no way to migrate backups from one data domain to another data domain while keeping the metadata on the same Avamar server.
The only way to move backups from one DD to another DD is via replication, the replicaiton is managed by Avamar and an Avamar server cannot replicate to itself. This means the only way to move the backup to another DD is to replicate to another Avamar / DD pair.
Thanks Adam, any plans to add "loopback" replication so that migration process is an option. I was thinking of a scenario where Avamar Grid was purchased on a different maintenance cycle from the DD. At some point in the product life you need to replace the DD because its maintenance is up but the grid still has a few years on pre-paid maintenance. Right now i would not have a choice but to buy brand new grid and DD.
Can I replicate "existing backups" to another AVAMAR-DD site but point the clients to backup to a local DD?
To make things clear,
Site A has avamarA, DD1 and DD2
Site B has avamarB, DD3 and DD4
DD1 will be decommed, there are 50 clients that use DD1.
I need to replicate the "existing backups" of those 50 clients to site B and then replicate them back to Site A DD2. but those 50 clients will be configured to backup to DD2 while the replication in and out is taking place so I do not have to write backups over the WAN as ddboost over WAN is still not supported by EMC as far as I know.
We do actually support backups to DD over the WAN from Avamar 7.1.
However, if you want to change the target DD for your backups on avamarA you just need to change the name of the DD system used in dataset of the client under ""Use data domain system":
I am not sure what the plans are for "loopback" replication in order to migrate backups between two Data Domain systems attached to the same Avamar.
For questions about future features or possible issues with the "migration" process I would contact your local team or sales teams as they have different options available to cover these scenarios.
Thanks for the response but how to point a client to a different DD system wasnt exactly my question!
I will be decommissioning a DD system (DD1), will replicate the data to another site (site B) and then BACK to the same site (Site A) to a different DD system (DD2). My question is "can clients that currently write to the DD that will be decommissioned (DD1) be pointed to the other DD in the same site (DD2) BUT have their previous backups replicated out and back in to two different DDs (out from DD1 to DD3 and back from DD3 to DD2)?"
Yes clients that currently write to DD1 can be pointed to DD2 AND have their previous backups replicated out and back in to two different DDs. Backup destination is independent to the replication destination:
The backup destination is set up in the dataset
The replication destination is set up in the "storage mapping" tab of the "Replication" window.
I have been thinking about this somewhat but have not had a chance to do any testing, this may require some advanced configuration that may require a professional services engagement, so if you run into issues this may be worthwhile discussing with someone from your local EMC team.
clevya
117 Posts
0
December 29th, 2014 02:00
Hello,
If one of those DDs is to be decommissioned, what is a method to move backups already stored on it to any of the other 2 DD systems? (if there is any).
ANSWER: There is no way to migrate backups from one data domain to another data domain while keeping the metadata on the same Avamar server. You could "replicate" the backups to another Avamar server which has the other two data domains attached to it as a work around.
In a different scenario, Can multiple AVAMAR servers write to the same DD system? What can be done to make sure that one AVAMAR server will write data through DDBoost to a different MTree than the other AVAMAR server?
ANSWER: Yes multiple Avamar servers can share the same DD system. When the integration is put in place a unique mtree is created based on the "hfscreate time" (install date in unix timestamp format) of the Avamar system. Each Avamar server will write into its associated mtree and nowhere else.
Does EMC support having the AVAMAR server and the DD system in 2 different sites? connectivity will use dark fiber.
ANSWER:
This is NOT supported in Avamar 7.0 and earlier as per 7.0 Avamar / DD integration guide page 23:
This IS supported under in some cases, if network connectivity is sufficient from Avamar 7.1 - Avamar 7.1 DD / Avamar integration guide page 24:
I hope that answers your questions?
Regards,
Adam
maxsven
1 Rookie
•
23 Posts
0
December 29th, 2014 04:00
Hi Adam,
when you say " You could "replicate" the backups to another Avamar server which has the other two data domains attached to it as a work around."
Did you mean replicate to another "Data Domain" through AVAMAR and not to another AVAMAR server...
If that is what you mean then it might be something that I can do, so are you saying that I can replicate all existing backups on the DD in site A to an AVAMAR - Data domain system in site B?
clevya
117 Posts
0
December 30th, 2014 05:00
Hi,
Yes that is what I meant.You can replicate the backups to another Avamar / DD pair either on the same site or on a remote site.
To go even further once replicated to another Avamar / DD pair, you can then replicate them BACK to the original Avamar / DD, but direct the backups to a different DD... I believe that is the only way to achieve what you want to do.
Regards,
Adam
dynamox
9 Legend
•
20.4K Posts
0
December 30th, 2014 06:00
Adam,
I think original OP was if i have 1 Avamar grid and two DD (let's say DD880 and DD890).
DD880 is coming of maintenance so i buy more capacity for DD890 and now need to migrated the data that was backed up by Avamar from DD880 to DD890. Is that possible ?
Thank you
clevya
117 Posts
0
December 30th, 2014 07:00
Hi
That is not possible:
The only way to move backups from one DD to another DD is via replication, the replicaiton is managed by Avamar and an Avamar server cannot replicate to itself. This means the only way to move the backup to another DD is to replicate to another Avamar / DD pair.
Hope that clarifies my previous answers?
Regards,
Adam
dynamox
9 Legend
•
20.4K Posts
0
December 31st, 2014 06:00
Thanks Adam, any plans to add "loopback" replication so that migration process is an option. I was thinking of a scenario where Avamar Grid was purchased on a different maintenance cycle from the DD. At some point in the product life you need to replace the DD because its maintenance is up but the grid still has a few years on pre-paid maintenance. Right now i would not have a choice but to buy brand new grid and DD.
maxsven
1 Rookie
•
23 Posts
0
January 2nd, 2015 04:00
Hi Adam,
Can I replicate "existing backups" to another AVAMAR-DD site but point the clients to backup to a local DD?
To make things clear,
Site A has avamarA, DD1 and DD2
Site B has avamarB, DD3 and DD4
DD1 will be decommed, there are 50 clients that use DD1.
I need to replicate the "existing backups" of those 50 clients to site B and then replicate them back to Site A DD2. but those 50 clients will be configured to backup to DD2 while the replication in and out is taking place so I do not have to write backups over the WAN as ddboost over WAN is still not supported by EMC as far as I know.
Is that possible?
clevya
117 Posts
0
January 4th, 2015 23:00
Maxsven,
We do actually support backups to DD over the WAN from Avamar 7.1.
However, if you want to change the target DD for your backups on avamarA you just need to change the name of the DD system used in dataset of the client under ""Use data domain system":
Hope that helps,
Regards,
Adam
clevya
117 Posts
0
January 4th, 2015 23:00
Dynamox,
I am not sure what the plans are for "loopback" replication in order to migrate backups between two Data Domain systems attached to the same Avamar.
For questions about future features or possible issues with the "migration" process I would contact your local team or sales teams as they have different options available to cover these scenarios.
Regards,
Adam
maxsven
1 Rookie
•
23 Posts
0
January 5th, 2015 05:00
Hi Adam,
Thanks for the response but how to point a client to a different DD system wasnt exactly my question!
I will be decommissioning a DD system (DD1), will replicate the data to another site (site B) and then BACK to the same site (Site A) to a different DD system (DD2). My question is "can clients that currently write to the DD that will be decommissioned (DD1) be pointed to the other DD in the same site (DD2) BUT have their previous backups replicated out and back in to two different DDs (out from DD1 to DD3 and back from DD3 to DD2)?"
clevya
117 Posts
1
January 6th, 2015 23:00
Maxsven,
Yes clients that currently write to DD1 can be pointed to DD2 AND have their previous backups replicated out and back in to two different DDs. Backup destination is independent to the replication destination:
I have been thinking about this somewhat but have not had a chance to do any testing, this may require some advanced configuration that may require a professional services engagement, so if you run into issues this may be worthwhile discussing with someone from your local EMC team.
Regards,
Adam