celerra Data migration

check nas_replicate

There are a few ways to accomplish this.  One way would be to create filesystem replications from the DMX_pool to the VMAX_pool.  During a downtime window, you would stop filesharing from the affected filesystems, execute a "nas_replicate -switchover" to make the new filesystems read-write, then change the CIFS and NFS exports to point at filesystems on the VMAX_pool.  The downtime would be pretty brief, especially if you scripted your switchover and changes to exports.

Let us know if that helps!

Karl

Hello Karl,

Thanks for the update.

I hope this will work on DM level or can we get this on the VDM level

also, as we do have multiple VDM hosted on the the physical DM

Thanks & Regards,

Srikar R Deshpande

Professional Storage Administration

CSC

Building 4, Mindspace IT Park, Hyderabad, 500 081, India .

Desk No: Switzerland 0848-000-066 Extn.746412 | US: +1-302-781-1020

Extn.746412

Mobile: +91-9642990214 | sdeshpande9@csc.com

Manager Name: Vineet K Arora

Advance Out of Office Notification: None

CSC • This is a PRIVATE message. If you are not the intended recipient,

please delete without copying and kindly advise us by e-mail of the

mistake in delivery. NOTE: Regardless of content, this e-mail shall not

operate to bind CSC to any order or other contract unless pursuant to

explicit written agreement or government initiative expressly permitting

the use of e-mail for such purpose • Computer Sciences Corporation India

Private Limited • 7th, Floor, Block 1B, DLF IT Park, Sivaji Garden,

Moonlight Stop, Nandambakkam Post, Ramapuram, Chennai-600 089. Registered

in India, CIN: U60231TN1996PTC070000

you can replicate file systems and VDMs

In reply to castleknock - it's the same Celerra, so #5 shouldn't be needed

when you are doing this ( nas_replicate is the way to go );

1. NFS exports need to be noted and regenerated at destination

2. FS alerts if they are being replicated need to be done manually.

3. snapshot schedules if they are being replicated need to be done manually. Do not delete the source fs until after full snapshot cycle has occured to ensure you have snapshot coverage.

4. Check that VDM's are named the same under unix ( root_vdm_x ) so NFS clients do not need path changes

5. Use DNS alias of source to destination IP to avoid NFS path change.

me bad