Video Screencast Help

Using DeDuplication in a DR senario.

Created: 18 Jun 2012 • Updated: 03 Jul 2012 | 5 comments
This issue has been solved. See solution.


I'm looking for advice for setting up our backup exec solution for our DR plans.

We currently have a Central Admin Server at one site, and a Media Server at another. The Media Server has a DeDuplication backup to disk folder and a tape drive connected.

The catalogs are replicated between both servers.

The CAS controls all the backups, but the MS actually performs the jobs.

The DeDuplication storage area is a windows volume on our SAN that is replicated accross both sites.

If we were to lose the Media Server and San on one site, would the CAS be able to connect to the replicated DeDuplication area and perform restores? Or is a DeDuplication area lost once the server that created it is lost?

Thanks in advance


Comments 5 CommentsJump to latest comment

CraigV's picture


If the CASO is set up correctly, and is duplicating properly, then the remote MMS already has a dedupe folder defined within BE.

In this case, you should be able to catalog the data on the remote dedupe folder, and would see the data available for restore.

You just need to set up your catalogs correctly. I seem to remember that Symantec (in the case of BE 2012) recommend replicated catalogs. If you localise them on the MMS for instance, then the CASO will play no role's simply a reporting tool in this case.

Here are a couple of TNs below to reference:


Alternative ways to access Backup Exec Technical Support:

leeweedon's picture

Hi, Thanks for the reply.

I may have mis-led you slightly.

The MMS has a DeDupe folder, it is setup on itself.

The CAS does NOT have a DeDupe folder.

We lose the MMS and its connected SAN (DeDupe Area)

So the senario is we need to attached the SAN replicated area to the CAS then do a restore from there.



Colin Weaver's picture

Did you replucate the Dedup folder using Optimized Duplication within Backup Exec and separate DeDuplication folders on both sites?


using some form of external replication technology?

Basically if you are using some form of external replication technology then you are probably using a completely untested scenario and the official line for recovery would be restore/rebuild your MMS and attach it back to the Deduplication store location in the same way you would if you were moving the deduplication configuration to new path on the same server. Note however if your replication technology might in any way not keep a consistent copy of the DeDuplication data then you might still have problems and not be officially supported for DR from the replica.

leeweedon's picture

We are using SAN side replication, we can almost gaurentee that the data is consistant, but it is an external way of doing things.

I will go away and investigate using Optimized Duplication through BKExec,

Thanks for your help.



teiva-boy's picture

If using SAN replication for the dedupe folder, I can guarantee that while *maybe* consistent, no way is it supported in any form from Symantec.

The only way it's supported to work, is when you configure optimized duplication, where you are replicating between two media servers, controlled via CASO.  The dedupe option would handle the duplication, and acctually be more efficient to replicate than SAN replication.  Not to mention, the maintenance tasks play havoc on SAN replication.

There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) "We backup data to restore, we don't backup data just to back it up."