We would recommend that you bond the eth ports and drop a new dedicated switch 
between the old DD and the new and then setup replication and migrate, in the 
past we have installed 10g cards for migration and it might also be worth 
performing some house-keeping before you do this.  As an example, remove old, 
incomplete,, suspect savesets and run nsrim -XM on the NW server then start a 
DD clean. It might save a few hours of replication time.

Regards

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of bingo
Sent: 04 April 2013 15:48
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Migration

Of course you could do that. However, my concern would be whether this is 
really necessary.

Considering disks to be 'short-term' backup media the question is how long and 
how much data has to be stored on disk at all. 
We are backing up about 120TB/month to 2 DD880s. Retention of these backups is 
1 month. After that, all data is gone.

To provide some type of 'versioning' we also clone the fulls created during the 
first 8 days/month ... on tape (ret = 18months).

Unless the retention policy of your DD save sets is significantly longer than 1 
month (which IMHO is not a good idea), the effort does not rectify the result.
I would just add the new DD and set the volumes on the old one to read-only and 
let them expire.

Of course, if you really use a DD as 'long-term' storage, then you might not 
have a choice.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------