Reg - Single Node Avamar System recovery

Hi Ravi,

I´ve been implementing Root-to-Root Replication a few times with Avamar Version 6.x and it´s quit easy. All Data will be replicated 1:1 and all other information like datasets, clients, groups is provided within the Postgres Database.

After you import the MC Database with the command "mcserver.sh –restore –restoretype=new-system" on the destination system you´ve got the everything there like on the source system. The only thing to mention is, that the Hostname and IP´s are different. Like i said before, you can redirect the old Hostname via DNS to the new IP Adress and it will become completely transparent to any User.

If you also want to get the original IP´s and Hostname you have to reconfigure Avamar like written in the Guide:

"https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-007-539.pdf"

Hope all your questions are answered

Regards,

Andreas

Here you can find a link:

http://www.emc.com/collateral/software/white-papers/h8245-avamar-replication-wp.pdf

Hi,

To prepare againt DR it is recommended to have at least two Avamar Systems on different Locations which are doing replication between both systems. It is called root-to-root replication which allows you to fully replicate all data including MC database information to the second Avamar node. In the worst case you only have to startup the other node and have to change the host and ip or only point the old hostname via DNS to the new System on the DR side.

Hope it helps.

Regards,

Andreas

From the Avamar 6.0 Administrator guide, page 340:

What data is replicated?
To fully replicate an Avamar server, all of the following data must be copied from the source server to the destination server during each replication operation:

• Client backups
• Domains, clients, and users
• Groups, datasets, schedules, and retention policies
• State of the server (for example, contents of the activity monitor and
server monitor databases at the time of the last MCS backup or “flush”)

Also, root-to-root replication is defined as:

Full root-to-root replication.

Full root-to-root replication is a kind of replication that creates a complete logical copy of an entire source server on the destination server. Furthermore, the replicated data is not copied to the REPLICATE domain, it is added directly to the root domain just as if source clients had registered with the destination server. Also, source server data replicated in this manner can be changed on the destination server.

Documentation for Avamar is located on Powerlink  (http://powerlink.emc.com).  Once logged in, selecet

Support > Technical Documentation and Advisories > Software ~ A-B ~ Documentation > Avamar

Then in the left column, expand Avamar Software and click on 6.0  (or 5.0, depending on you installation).  There are many documents there for download, including the Administrators guide, VMware guide, Security guide, etc.

Technical documentation is available by click on the link in left hand column.

Mark

Thanks Mark for the useful info and link.

Hi, I have a couple of questions regarding root - to - root replication.

1. can you schedule root - to - root replication or is it only manual? If possible how do you schedule it?

2. If you have a DataDomain backend and all your backups go to the DataDomain connected to Avamar how will this affect in case of a breakdown on Avamar server A. Let's say that you have a replicated Avamar setup but only a DataDomain on the primary system. When the Avamar server A goes down and you bring Avamar server B online via a root - to - root replicated "backup" will you be able to do backup/restore from the DataDomain system connected to Avamar server A. I couldn't see why this shouldn't work but I'm not sure