Celerra Backend disk migration

It is not that simple - I would strongly suggest to talk to your EMC professional services people

Thank you for responding. I will be using the fs_copy approach.

Are you just going to be adding VMAX luns to your existing NS80g as a new pool?  If so you can just add the luns, create the new pool, make the file systems, mount it read only, and use nas_replicate to create an ongoing replication session... then when you are ready to cutover break the replication.. mount read write... create your exports... bam...

Yes, but this way the control (boot) LUNs are still on the old array

Excellent point,  I just presumed it was a multi array environment where the root vol was on a cx or vnx... must be what i'm just used to!

Rainer_EMC wrote: Yes, but this way the control (boot) LUNs are still on the old array

Many thanks to all for taking time to help me out, here is a breakdown of

my goals:

What is my system: Celerra NS-G8

What my Version: 6.0.61-0

What is my backend: DMX4

This NAS has two backend arrays both are DMX4, one of which is coming up

for decommission and will be migrated off to new V-Max 40K. I need to

migrate only those file system that have storage from decommissioning

array to new V-Max. Control or root devices both are on the second array,

which is not yet ready for decommission, therefore; may not need to move

those at this time.

Base on the recommendation is received, you suggested to:

1- Create new Storage pool from New Array V-Max 40k

2- Create new File System with same capacity, using V-Max 40k Storage.

3- Mount new File Systems as RO.

4- Use Celerra Replicator to copy data over to new File system.

5- Umount both File Systems.

6- Rename source File System.

7- Rename target File system to = original source name.

8- Mount Now new File system as RW.

9- Release to production.

Regards

Carlos Velasco

Contractor to Pwc - US IT Storage

Cell:813-442-2500

Office Phone813-348-7796

Building LP1 6th WorkSpace:06015.5

carlos.velasco@us.pwc.com

From: mmay

To: Carlos A Velasco/US/Visitor/PwC@Americas-US

Date: 02/28/2013 10:44 AM

Subject: New message: "Celerra Backend disk

migration"

EMC Community Network

Re: Celerra Backend disk migration

created by mmay in Celerra Support Forum - View the full discussion

Excellent point, I just presumed it was a multi array environment where

the root vol was on a cx or vnx... must be what i'm just used to!

Thanks, we are only migrating back-end, we are not making any changes to

VM's or CIFS servers.

Regards

Carlos Velasco

Contractor to Pwc - US IT Storage

Cell:813-442-2500

Office Phone813-348-7796

Building LP1 6th WorkSpace:06015.5

carlos.velasco@us.pwc.com

From:  Rainer <emc-community-network@emc.com>

To:    Carlos A Velasco/US/Visitor/PwC@Americas-US

Date:  02/28/2013 02:04 PM

Subject:        https://community.emc.com/Celerra Support Forum New message: "Celerra Backend disk

migration"

EMC Community Network

Re: Celerra Backend disk migration

created by Rainer  in Celerra Support Forum - View the full

discussion

Sounds ok

You can also just do a failover ? renaming the fs isnt necessary ? the

file system name is just internal

If you have CIFS servers you want to migrate them as well ? easiest way is

with VDMs

Any checkpoints and schedules will have to be re-created

Once you are done and removed the old DMX4 ask your local support guy to

dialin and cleanup old devices or SCSI bindings

Reply to this message by replying to this email -or- go to the message on

ECN

Start a new discussion in Celerra Support Forum by email or at ECN

Sounds ok

You can also just do a failover – renaming the fs isnt necessary – the file system name is just internal

If you have CIFS servers you want to migrate them as well – easiest way is with VDMs

Any checkpoints and schedules will have to be re-created

Once you are done and removed the old DMX4 ask your local support guy to dialin and cleanup old devices or SCSI bindings

Check which DMX your data mover root or VDM file systems are on