Data Domain Replication

Question

Hi everyone, We are trying to achiev a migration and replication of DD, here is our scenario: Production: - DD1: DD2500   OS:5.0.6.5 - 10GB ethernet x2 optical (DDBoost) - 1GB cooper (administration) - 8GB FC (VTL) - VTL and DDBoost configured - Netbackup 7.7 - 2 media servers that manages VTL and DDBOOSt, 1 media servers for other purposes and 1 master. DR Site has a 1GB network and extended SAN over FC we just bought a new DD2500 plus one shelf ES30 (not configured yet) with the same characteristics - DD2: DD2500   OS:5.0.6.5 - 10GB ethernet x2 optical - 1GB cooper - 8GB FC - VTL and DDBoost configured - Netbackup 7.7 So, we want to: 1. Migrate all the data from DD1 to DD2. 2. Set DD2 + shelf for production enviroment 3. Take DD1 to our DR site 4. From this point, we want to set a native replication between DD. This means that all new backup created on DD2(production) have to be replicated/sync to the DD1 (DR site) For the migration we have evaluated using Collection Replication or Mtree Replication . So, we already have read some posts here and guides and we have a couple of questions: - Collection replicacion: Cannot be resynced, It cannot accept any other traffic - no backups, no Mtree replication etc.,Destination DD is read-only. Requires a downtime.           If we use this option to migrate the data from DD1 to DD2, after the migration is finished no more new data can be written to DD2; is           there a way to change this so the DD2 will be my production DD and has to recieve new backups?           As both DD are physically installed in the same rack, can we connect them directly each other?               - Mtree Replication: can be resynced, I understood that doesnt requiere a downtime.           Will the Mtree replication copy the permissions and users (DDBoost user)?           Once the replication is done, will we just have to change the hostname and IP's in order to get the Netbackup recognized this new           DD2 as nothing has changed?           So, if we want to keep it up to date the new data has to be replicated/sync using Mtree replicataion again? if so, can we schedule           this or has to be done manually everytime we want to be sync?           Do I have to format or erase the DD1 in order to recieve new replicated/sync data?           As both DD are physically installed in the same rack, can we connect them directly each other?   Once the data is migrated we want to keep both DD synced        - Netbackup: Has to be done using Duplication option. As we understand it will take more time as the process expand the deduplicated data then it's copied to the destination and deduplicated there.           So we are thinking using Netbackup as we have an Extended SAN, is this a good option or what can we do? Many thanks!

chpstaker1 · Answer

I'd like to know what options exist as well. We have the same scenario. A NBU master/media servers that target Data Domain and we want to refresh the DDs with new hardware. Can we use collection replication (or any DD based replication) or do we need NBU to manage the replication?

The goal is to migrate all existing NBU data that sits on DD1 to the new DD2 and maintain NBU catalog awareness.

Thanks

rugby01 · Answer

So here's your answer...

1) Collection Replication is for 100% DR read only copy of data to allow the swap from Active site to DR site. You can use Collection Replication, and work with support to then turn off replication, make the file system Read/Write, and change the array name and IP to take over as Primary. This is the easy way to swap arrays if that's all you need.

2) Using mtree Replication. You could replicate the existing NetBackup mtree's to the new Data Domain, Then create a new mtree on DD2 for Netbackup, and change all backups to the new mtree/DDR2. You can setup mtree replication from the new DD2 mtree to the old DD1. That would put all new backups on the DD2 data domain and use the global deduplication to reduce the number of blocks moved for backups. Once the data on DD1 is expired, then delete the mtree and replication mtree.

3) The best way would be to just setup the new mtree of DD2 for Netbackup, then setup another pool on DD1 for clones. Netbackup is aware that the clone job from one DDR to another is special and uses DD replication. This method allows you to access both the backups at active and keep different retention. You could keep 60 days on DD1, and only month backups on DDR2 for example. This could double the size of your netbackup catalog, but it's worth it as then you can restore backups from either source.

4) I guess a forth way (that never works in Netbackup) would be to create the new DD2 mtree and pool, and make a second copy. Netbackup is suppose to be able to just select all old backups and make a copy to a new pool. But, I've tried this a few times with much less success it the catalog is big. This is what it says - have Netbackup make a copy and index everything in the catalog.

Data Domain

Was this post helpful?