I'm having some issues regarding replication and can't seem to find answer for this. As I understand it below is the supported Replication methods supported by Avamar
I my case I'm having some issue regarding the chain replication. It looks like when Avamar server A replicates to Avamar B, it's created under Avamar B /REPLICATE domain which is how it works. My problem is that the customer want's everything from Avamar B replicated to Avamar C but it doesn't look like the data in Avamar B /REPLICATE domain is included in this replication to Avamar C.
Is there any was of getting data in the /REPLICATE domain replicated to another /REPLICATE domain. Root2Root is not an option in this scenario.
A quick word of warning: In chain replication you have to be very careful not to reverse the direction of replication or replicate from Avamar C to Avamar A. If this happens -- either by error or intent -- the customer will be spending a week on the phone with support getting client accounts put back in the right places.
Chain replication needs to be set up like a root-to-root, except you specify --srcpath and --dstpath to override the source and destination paths. For example:
Note that I have specifically left out the flag that triggers root-to-root because I don't want somebody inexperienced or poorly trained to read this post and shoot themselves in the foot. If you're a partner, you should have access to the documentation required to finish the configuration.
ok, so lets say that C was Replication target for various Avamar nodes. Can you do more than on Root2Root to the same Avamar grid?
Another issue I have is that I need to replicate backups already in a /REPLICATE domain on a Avamar grid to the same /REPLICATE domain but on another Avamar grid. The reason is that customer bought another larger grid as replication target since the old one was very highly utilizied = 99.9% full. We couldn't do a root2root on this grid since replication was not running to the old replication grid and therefore we had to point all the remote nodes to the new replication grid so the customer could start replication again
I have tried with the various commands but either I get the error that source cannot be /REPLICATE or destination cannot be /REPLICATE
ERROR: Destination path cannot contain /REPLICATE for restore!
So the big question here is: Is it possible somehow to replicate backups from /REPLICATE domain to a /REPLICATE domainwith doing Root2Root?
I already have PS involved but they haven't given me a straight answer yet
I appreciate any guidance or input you might have. Just for the record, I know that I have to be very carefull and therefore everthing is being tested in a test enviroment.:-)
Yes, it is possible to replicate from /REPLICATE but as I mentioned, it's potentially dangerous so I'm not willing to post instructions in a public forum. Please send me an e-mail at firstname.lastname@emc.com and we can discuss offline.
All kinds of replication is possible. You can replicate from A to C to a non replicate domain. I would advise to involve professional services to perform the task.
ionthegeek
2 Intern
•
2049 Posts
828
1
Posted March 29th, 2016 06:00
A quick word of warning: In chain replication you have to be very careful not to reverse the direction of replication or replicate from Avamar C to Avamar A. If this happens -- either by error or intent -- the customer will be spending a week on the phone with support getting client accounts put back in the right places.
Chain replication needs to be set up like a root-to-root, except you specify --srcpath and --dstpath to override the source and destination paths. For example:
replicate --srcpath=/ --dstpath=/REPLICATE/AvamarB
Note that I have specifically left out the flag that triggers root-to-root because I don't want somebody inexperienced or poorly trained to read this post and shoot themselves in the foot. If you're a partner, you should have access to the documentation required to finish the configuration.