Forum Discussion

paolocorsini's avatar
paolocorsini
Level 2
5 days ago

Data replication to Cloud

Hi all, my customer is willing to setup a Disaster Recovery solution.

The source environment is based on Netbackup + DataDomain using DDBoost. Customer would like to replicate to cloud without using DELL DDVE, but he'd rather prefer to use standard blob storage in Azure.

Can this be achieved using native NetBackup replication features, or do we need to stop using DDBoost on the source environment and start using a different deduplication tool?

I've been given the attached high level architecture, but colleagues state that DDBoost must be disabled in order to use MSDP-C for replication.

Blob
Blobstorage
DataDomain
DDBOOST
DDVE
Replication

3 Replies

  • StefanosM's avatar
    StefanosM
    Level 6
    5 days ago

    By saying “disable DD Boost,” do you mean to stop using Data Domain?
    Because you cannot use Data Domain without DD Boost. 

    What you describe in the PDF is doable — I’ve done it once or twice myself.
    However, I have to point out that, unless the customer environment is small, the time and resource penalty of rehydration and re-deduplication will be significant. Exactly how big is hard to predict.

    It’s quite easy to configure a media server with MSDP (~2 TB) + MSPD-C and test it.
    Again, if the customer’s environment is small, you can use the same media server to perform both DD and MSDP deduplication.

    Also, the cloud storage can be cold as well.

    Of course, the recommended approach is to discontinue the use of Data Domain, deploy a media server with MSDP storage, and leverage NetBackup Optimized Duplication to replicate your backups to MSDP-C.

     

    • paolocorsini's avatar
      paolocorsini
      Level 2
      5 days ago

      Hi Stefanos and thank you for your answer!

      With "Disable DDBoost", I mean stop using DDBoost and replace it with MSDP, as my colleagues state that the two are mutually exclusive (I'm not an expert, so please forgive me if I write something wrong!).

      You mean that we should restore (on physical disks?) and then compress/dedupe again before sending data to the cloud? Can't we perform such process "on the fly"?

  • anthonyyy's avatar
    anthonyyy
    Level 3
    20 hours ago

    Hello,

    I believe that your colleagues suggest to stop ddboost and use MSDP instead in order to avoid re-hydration of backup images.

    As first location (datadomain) and second location (MSDP-C) are two different technologies, you'll send the real amount of datas in the cloud (and not the deduplicated ones).

    Doing what you propose with your current infra is feasible, but not optimal because you will lose the benefit of the deduplication in the cloud. Duplication will take much more time (up to some days depending on your infra). If you have a full MSDP infra then you'll be able to sent deduplicated datas to cloud.