CENTERA Recall (Migration Process)

UHAC (production) - 1TB Data Celerra (NSG or Integrated or Unified) / CENTERA Gen3 or 4

Objective - Migrate data to any other target storage (not EMC). Decomission existing celerra and Centera.
Checkpoint / Red Flag- archived data in centera and how to recall those data.

Best Approach
option (A)
(1) Break connection from Celerra using fs_dhsm command (Centera connection) -
***Prerequisite - equal amount of free space is required in Celerra when you recall the data from Centera***
(2) Once all data recalled; complete migration using host based migration tool or backup/restore option **prerequisite - dedicated Windows host with high end configuration and domain admin access **

option (B)
(1) Use host based migration tool like emcopy or xcopy or robocopy **prerequisite - dedicated Windows host with high end configuration and domain admin access**
(2) map target drive or assign lun to target drive
(3) migrate data (while migrating data; it will recall the data from Centera during read and copy process; and it will copy the entire content of the file system)

option (C)
Working directly with SDK API's of centera (the SNIA XAM protocol *used by Interlock or any other vendor using this migration approach*).

option (D)
(1) break connection from celerra to centera
(2) take backup of stub files/and entire file system contents
(3) restore in new target storage (with same config of CIFS/fs)
(4) create new connection like in celerra (from new storage to centera)
(5) recall data from new storage
(6) once all data recalled; decomission centera
Note: this will depend on the compatibility of CENTERA with new target storage.

Option C is much faster than any other options.
option A and B are a best approach if customer has any financial constraints