Netbackup duplication/migration between Datadomains

[sesha]

Hi All, 

We are currnetly running Netbackup 7.6.0.4  with Datadomain as the  storage unit. We use ddboost for backups. 

We have to migrate our backup environment  to a new datacenter which will also have datadomain. What is the best possible way to do the migration  ? I hav few options but have questions on the optimized duplication and th best approaches and problems 

Facts : 

• Our catalog is 800+GB.
• We dont intend to do catalog recovery. Our Catalog sits on SAN disk and will be SRDF to destionation . The Master /media server will be  physically lifted and shifted to destination.
• The totoal data on DD is about 260TB ( compressed ). the uncompressed netbackup images sizes totals to about 2.4+ PB

Option 1 :  

UseVault duplication feature or mannual image duplication to  duplicate the old backup images as copy2 to the new DD. (We are using DDbost to connect to DDs which means the current Media server will talk to both DDs). Then after migration is over, move the Master /media servers to new DC. Catalog sits on SAN disk and will replicated to destionation via Storage SRDF and will be mounted on master after server is moved 

In  this case of duplication, will optimized duplication occur  -or-  will the data be rehydreated  ? 

Option 2 : 

perform DD to DD MTREE replication (Netbackup is not aware of the 2 copy) , then move the servers to new location, Add host entries on Master server such that the Datadomain IP resolves to old Datadomain name. 

Is option 2 viable,  will  the DD media id be different at the destination in netbackup when we do  this (If that is the case we will have to  do catalog manipulation ?  Can catalog manipulation be done with the images in Netbackup 7.6.0.4 to change the ddboost media  ids  ?) 

Please advise the best method .

[sdo]

Good post Sesha - nice clarity.

My immediate reaction is to ask how long is the longest retention on the current DD?

[sdo]

I think option 1 is do-able by you.  Whereas option 2 sounds like it may require a CatMan specialist even if it is possible (which is as yet unknown).

With a 2.4PB to 0.3PB dedupe ratio then I would have thought that you'd see some great optimized duplication rates for backup duplication - but it depends upon the result of:  size of backup and and the actual dedupe rate achieved, and thus the resultant size/volume/quantity of actual bits/bytes/blocks to duplicate and thus whether your LAN/WAN/SAN links are capable of achieving a full set of duplication before the next set has to start again.  Do you see how you might never be able to catch up, and always fall further and further behind?

I'm wondering whether, because you have such good de-dupe rates, whether there's a possibility of just duplicating a few days/weeks of backups across an then doing a lift and shift and point backups to the new DD because they should de-dupe quite nicely against a semi-populated new DD.

Hmmm, where are the clients in all this?  Remaining at the original site, or moving too?  How many clients?  All moving/migrating at the same time too?

[sesha]

Thank you SDO for your inputs. 

Longest retention is 7 years.

We need to migrate only  7 years retention backups from previous years. We are not going to  duplicate or migrate any ongoing backups or daily backups as they have a short retention of  few weeks. 

The clients are being move to new DC and added on a seperate Netbackup domain already. 

We need all the old long term retention images to be duplicated only for any furture restores ( When a restore is requested the client software on client will be repointed to old env ) 

So you say ,  that the netbackup Vault duplication or image duplication will  do optimized duplication between DDs across the WAN  and will not cause the data to be rehydrated . is this correct ?  if yes,  then we only have to duplicate less 260TB of data  across the sites ? 

Is my understanding correct ? 

[sdo]

You/we need to check the HCL for "OptDup" capability between the two models of DD h/w and f/w and OST version. Can anyone confirm whether Vault will use "OptDup" if it sees that it can? Or confirm whether "OptDup" is only available for SLP based duplications? I have a nagging doubt about Vault.