Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5002

August 16th, 2017 08:00

Data Domain migration from DD990 to DD9300

We are in plan of replacing the Data Domain from DD990 to DD9300. We have Networker as major backup tool through DDBoost and one VTL for AS400 BRMS backup.

We have 40% (150 TB) of our backups with more than a month retention and we can keep the old DD (DD990) for a month.

We have replication happening to 2 DD's from the primary DD. One locally and one to remote DD through WAN.

We don't have a option to get more than 8 hours of downtime.

Usable capacity is 401 TB and Max used is 350 TB.

We have 4x10Gb/s network connection.

Considering all these factors I wanted to know what would be the best approach to migrate the data from old DD to new DD.

Moderator

 • 

41 Posts

August 28th, 2017 13:00

This is a great question.  Hrvoje way will work just fine.  I have not gone that route but we have had many customers that have followed that way.  With really large Data Domains collection based replication is the fastest way to migrate to a new system.  This is the way I have performed migrations with most of my customers.  It is also my preferred way to move to a new Data Domain.  If you are going to use collection based replication here are a few things you need to look at.

1. You will need the two systems on the same version of code.

2. Since you have a 990 you probably have a robust network.  I still recommend that you do a direct cross connect between the two systems.  If you can't do that it is fine but I find that it is best to do the direct connect.

3. Collection replication will copy the all of the users to the new dd but it will not do the following.

     a. copy the ddboost config  IE you will need to manually recreate the ifgroups and set the mtree's as ddboost storage units.  To set the mtrees that are the boost storage units you will need to use the ddboost storage-unit modify command.

     b. copy the vtl config

     c. copy the nfs mount points or the cifs config

4. If you have mtree replication you can follow the following KB I have written to help in converting them once collection repl is done.  ( How to convert collection replication to mtree replication https://support.emc.com/kb/498373)

I hope to have a new kb out soon to cover this process.  I know it sounds hard and complicated but it is fairly easy to do. 

1 Rookie

 • 

14.3K Posts

August 28th, 2017 07:00

You could use DDBoost for NW based backups to make them aware on the new targets.  Actually, I believe for NW this is what I would do; create backup pool on it and have nsrclone -m to migrate them from old DD to new one in bathes.

I'm not familiar with AS400 BRMS backup so I have no idea how I would handle that part.

August 28th, 2017 09:00

How about performing whole DD replication using collection replication? If I do collection replication and then shutdown the old DD and then rename the new DD with the old IP and name, will there is any issues with networker? Will networker recognize all the backups?

1 Rookie

 • 

14.3K Posts

August 28th, 2017 12:00

I don't know as I never tried that...

5 Posts

January 15th, 2018 11:00

If opting for professional services - We at DSI offer Data Migration services based on the non-invasive offline technology and unique processes ensuring zero downtime and migration on any scale. Can share our collateral, project references ponnappa@go-dsi.com

1 Rookie

 • 

20.4K Posts

January 16th, 2018 04:00

this is a support forum, not a "sell my company services" board.

No Events found!

Top