2 Intern

 • 

152 Posts

April 16th, 2009 12:00

Thanks very much for the info .

9 Legend

 • 

20.4K Posts

April 16th, 2009 12:00

i would definitely use replicator. You have an good fail back plan if migration goes south, you don't need to rely on your tape/cdl infrastructure, it's just going to be so much faster.

9 Legend

 • 

20.4K Posts

April 16th, 2009 12:00

for migration purposes i would use replicator as it would allow you to migrate a lot of internal configuration that otherwise would have to be re-created manually. What are you migration CIFS/NFS/iSCSI ? What model/code are source and target Celerra's ?

2 Intern

 • 

152 Posts

April 16th, 2009 12:00

Only NFS . Source celerra is 5.5.29 and Destination is 5.5.38 .

4 Operator

 • 

1.5K Posts

April 16th, 2009 12:00

Celerra Replicator (with fs_copy) will be option to go with your case - it will be the Replicator V1 as you are running 5.5 code.

Since it is only NFS - the migration will be bit easier - migrate the data (file systems) and then re-create the export lists on the new. "dynamox" just replied to another thread - please allow me to post that link -

http://forums.emc.com/forums/thread.jspa?forumID=86&threadID=115197

Cheers, :)
Sandip

2 Intern

 • 

152 Posts

April 16th, 2009 12:00

source and destination are NSX models.
No Events found!

Top