Unsolved
This post is more than 5 years old
9 Posts
0
1462
Migrating/moving FS on Celerra from CX-700 to CX3-80
Hi
Our current CX-700 Clariion is full and our filesystems are filling up, so we've gotten a new CX3-80 with some additional TB of storage.
Now, what i want to be able to do is basicly move some of the current filesystems residing on the CX-700 to the new CX3-80, with as little downtime and changes as possible. I.e i want the CIFS servers and vdm's to stay the same they are. Preferrably i'd like to let the new filesystems on the CX3 have the same name as the original filesystems (after the move is complete).
So, in short, does the following "plan" make sense ? or am i completely lost....
1) Create a new filesystem on the CX3.
2) Take a checkpoint of the filesystem i want to move/migrate
3) Copy the checkpoint to the new filesystem (I assume the new filesystem can be larger than the old one)
4) Stop access to the old cifs-share/filesystem
5) Take another checkpoint and do an incremental copy
6) Verify that all data is availible on new filesystem
7) remove/rename old filesystem
8) rename new filesystem to same name as old one
9) Make sure new filesystem is mounted at the same place & with same name as the old one.
10) Voila, done, let users access the cifs share(s) again.
And yes, i will talk to our local emc nas guy, but wanted to have a general idea of a sensible way of doing this before i talked alot with them about it.......
Message was edited by:
BjornMartinLarsen
Our current CX-700 Clariion is full and our filesystems are filling up, so we've gotten a new CX3-80 with some additional TB of storage.
Now, what i want to be able to do is basicly move some of the current filesystems residing on the CX-700 to the new CX3-80, with as little downtime and changes as possible. I.e i want the CIFS servers and vdm's to stay the same they are. Preferrably i'd like to let the new filesystems on the CX3 have the same name as the original filesystems (after the move is complete).
So, in short, does the following "plan" make sense ? or am i completely lost....
1) Create a new filesystem on the CX3.
2) Take a checkpoint of the filesystem i want to move/migrate
3) Copy the checkpoint to the new filesystem (I assume the new filesystem can be larger than the old one)
4) Stop access to the old cifs-share/filesystem
5) Take another checkpoint and do an incremental copy
6) Verify that all data is availible on new filesystem
7) remove/rename old filesystem
8) rename new filesystem to same name as old one
9) Make sure new filesystem is mounted at the same place & with same name as the old one.
10) Voila, done, let users access the cifs share(s) again.
And yes, i will talk to our local emc nas guy, but wanted to have a general idea of a sensible way of doing this before i talked alot with them about it.......
Message was edited by:
BjornMartinLarsen
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 22nd, 2007 05:00
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
March 22nd, 2007 05:00
fs46 - source file system on CX700
fs52 - destination file system on DMX3
i am creating fs52 to be the same size as fs46 ..it will be resized later on.
let me know if something does not make sense:
1. Create destination file system with rawfs file system.
nas_fs -name fs52 -type rawfs -create samesize=fs46 pool=symm_std storage=000290100222
2.Mount destination file system read only
server_mount server_3 -option ro fs52 /dmx3
3.Create first ckpt of source file system
fs_ckpt fs46 -name fs46_ckpt1 ¿Create
4.Copy first ckpt of file system to destination file system
fs_copy -start fs46_ckpt1 fs52 -option convert=no
5.Create second ckpt of source file system
fs_ckpt fs46 -name fs46_ckpt2 ¿Create
6.Copy incremental changes between first checkpoint and second checkpoint to destination file system
fs_copy -start fs46_ckpt2 fs52 -fromfs fs46_ckpt1
7.permanently umount and delete migration checkpoints (fs46_ckpt1 and fs46_ckpt2)
nas_fs -delete fs46_ckpt1 -o umount=yes
nas_fs -delete fs46_ckpt2 -o umount=yes
8.permantely umount fs 46
server_umount server_3 -perm fs46
9.permanently umount fs 52 from its temporary mount point
server_umount server_3 -perm fs52
10.mount fs52 with old moutnpoint
Bj_rnMartinLars
9 Posts
0
March 22nd, 2007 05:00
(and the reason i was thinking of renaming the filesystem is to avoid having to update the documentation :p)
Rainer_EMC
8.6K Posts
0
March 23rd, 2007 02:00
If you have the license for Celerra Replicator, you could also do it from the GUI with just a couple of mouse clicks
Just create the new file system, start a replication session and when your clients are ready press failover.
Celerra Replicator does the very same fx_copy steps for its initial data copy and then also copies the changes to the source file system to the destination every couple of minutes using its own deltaset mechanism.
jpmorgan17
51 Posts
0
November 26th, 2008 12:00
Rainer_EMC
8.6K Posts
0
November 26th, 2008 13:00
An easier way would be to ask your sales team if you can use a Replicator license for a couple of weeks
jpmorgan17
51 Posts
0
December 3rd, 2008 13:00
Rainer_EMC
8.6K Posts
0
December 3rd, 2008 15:00
yes, just use switchover, then delete the replication session, the replication interconnect and your old VDMs and file systems.
switchover and reverse do the same things, except that a reserve will as the last step restart the replication session in the other direction
In case you're wondering - failover compared to that will not do any sychronisation and should only be used when the source side is no longer available
Now that you know how easy it is ask your sales guys how much it costs - its really a nice DR or B2D solution and we have pretty small Celerra's these days
Rainer_EMC
8.6K Posts
0
November 19th, 2009 10:00
yes and use the default (no mode option which means both)
mode source or destination are only needed if one side isnt operational
see the man page or Replicator manual for more thorough explanation
moe2197
23 Posts
0
November 19th, 2009 10:00
moe2197
23 Posts
0
November 19th, 2009 10:00
Thanks for the fast reply!
Was the "yes" to run the command from the source (old NS) or the destination (new NS where everything is now running?
moe2197
23 Posts
0
November 19th, 2009 10:00
Rainer_EMC
8.6K Posts
0
November 19th, 2009 10:00
moe2197
23 Posts
0
November 20th, 2009 08:00