Unsolved
This post is more than 5 years old
2 Intern
•
236 Posts
0
1353
February 3rd, 2015 07:00
How to configure managed file replication on BE2014?
Hi Everyone,
Can anybody provide exact steps (with screenshots, if possible) for configuring managed file replication on BE2014? EMC does not seem to have any kind of more or less comprehensive documentation on it.
Any input is appreciated.
No Events found!
ble1
4 Operator
•
14.3K Posts
0
February 5th, 2015 06:00
Configuring DDBoost with BackupExec should be in Symantec docs, right?
Nayaks1
77 Posts
0
February 5th, 2015 23:00
I don't know backup exec at all, I'm more of an avamar guy. If I want to configure replication among 2 DDs in 2 separate sites managed by the respective avamar boxes then I would look for Avamar documentation to configure replication. I'm sure you would need a replication license of DD too.
paul_aviles
31 Posts
0
August 23rd, 2015 09:00
It is not that complicated. From the BE server you need to have both DD units defined as storage OST devices. Create an MTREE on each DD unit for each for example:
On the Local Unit create an MTREE with DDBoost called like:
DD-UNIT-A
On the Remote Unit create an MTREE with DDBoost called like:
DD-UNIT-A-REP
This way you know the DD-UNIT-A-REP is the replicate of the other unit.
On the BE server mount each as an OST device. This means that both DD units must be visible on the network from each other, preferable on alternate NICs than the regular management interface.
When creating a backup job on the BE unit there is an option to clone after backup and that select DD_UNIT-A-REP as the storage location and you will accomplish this tasks. It is very easy and efficient this way and the performance is phenomenal.
Keep in mind now that for every job performed with a clone you will have two locations to pull the data from and you can tell from which is comes based on the storage name. You will also need to called the job name a bit different. If the server being backup is called EXCHANGE for example, call the clone job something like EXCHANGE-REP. Also, this is the preferred way of doing this as BE will take care of managing the replication automatically after the first job and the catalog will be in sync. If you ever lose site A completely (nothing is left at SITE A, burned completely, no BE and no DD server) you will need to recreate the BE at site A, point to OST storage at remote site and scan the catalog and you will have all the data available to restore immediately.
I have done this very same setup using two BE and two DD in replication for two sites, but can be expanded to support multiple site to site replication and hub-spoke so all your data is replicated always.
If you have any questions let me know.
Paul Aviles