Hi,

If you have time to wait for migration to finish, I would use the DD data migration process.

Once the replication of all data is finished, you can start using the destination DD.

First unmount all devices in Networker and then change the device access information to reflect the new Data Domain name.

Regards

Magnus

I can only think of setting up a staging process for all save sets of each DDBoost device.

Collection replication would be best option. With this method, an image is taken from the source Data Domain and copied to the target Data Domain system. In a collection replication pair, the destination system is an exact copy of the source, including all user account and password information. The entire /data/col1/ area is replicated making collection replication a mirror of the original. Collection replication performs whole-system mirroring in a one-to-one topology, continuously transferring changes in the underlying collection, including all of the logical directories and files of the  Data Domain file system .

Do a cut over and provide same host name to new DD once collection replication is completed.

Thanks for sharing this. Quick question, once the collection replication has completed, do you mind listing the steps to perform a cutover on networker so it can see old save sets via the same dd boost devices?

Does it need to have all existing ddboost devices unmounted -> Change data domain name under "Device Access Information" for all devices -> Mount them and resume operations?

We are planning to change the hostname of the new Data Domain. Many thanks.

once the replication is completed break the context and to make the destination DD writable. Then as you gave already mentioned the device access information for each of the DDBoost device has to be edited to put in the new DD's hostname. And yes this has to be done to each one of the devices, no short cuts unfortunately.