Unsolved
This post is more than 5 years old
89 Posts
0
983
Replication target question
I was curious, I've never managed Avamar replication before. I was wondering, when an object, in this case a domain/container, is deleted on the source, when should it disappear on the target side when I look in the REPLICATE domain? I was trying to to understand how things removed from the source end up disappearing on the target side.
ionthegeek
2K Posts
0
October 20th, 2016 10:00
Replication in Avamar is additive - deletions should never be replicated. If you have backups, clients or domains disappearing form the replication target (Edit: other than because of normal backup expiration) please get in touch with support.
ionthegeek
2K Posts
0
October 20th, 2016 11:00
You can delete things from the replication target in the usual way. However, If a client still has backups on the source, they will be re-replicated which will re-create the domain(s) and client account(s).
Sorry, my reply was probably a bit misleading -- client accounts will stick around until they are deleted or retired even if they have no backups. They will not be automatically moved or removed.
Clarkson14
89 Posts
0
October 20th, 2016 11:00
Ok, so it's not a "synch" type thing. If I wanted to remove, say a really old domain/container, or say one I created and decided the next day I misspelled it or something, can you just delete that from the target side? How does a deleted client on the source handled, is that where it hits it's backup expiration and disappears. I guess in a sense it sounds like you wouldn't normally be messing with anything in the /REPLICATE container on the target side unless doing a restore?
ionthegeek
2K Posts
0
October 21st, 2016 10:00
Avamar does not replicate deletions. This is to protect you from potentially destructive "Oops" moments.
Clarkson14
89 Posts
0
October 21st, 2016 10:00
On that last part, when you say client accounts stick around until deleted or retired, is that deleted or retired from the source, those changes replicate over? I just want to make sure I don't have to remember to clean things up on the target side of things when I'm deleting/retiring things on the source.
I was mainly thinking about things in regards to annoying admins that like to change their vm names, if in those cases when I do a retire on the old name and re-add the new vm with the old name, that takes care of itself during replication.
Thanks again.
Clarkson14
89 Posts
0
October 21st, 2016 10:00
So how does that work in a situation where say, a vm, server1.local.net gets cloned to server1.local.net-new, and then a week later server1.local.net gets deleted and server1.local.net-new gets renamed to the original name, server1.local.net? Or even on a rename where you'd end up with the original server1.local.net being renamed to server1.local.net-old and server1.local.net-new renamed to the original name of server1.local.net? That's where I get confused, if you end up having to go the the target /REPLICATE for a restore what that looks like.