Unsolved
This post is more than 5 years old
15 Posts
0
1175
Celerra to VNX F/S replication
Hello,
I have a bunch of F/S created as Mixed and Mixed_compat, which needs to be replicated/migrated to VNX7600. All the F/S is mounted on a Datamover (server_2), can I use Celerra Replicator or is there any EMC recommended tool? Please let me know, Thank you!
rbhat23
15 Posts
0
November 19th, 2013 07:00
Thanks a lot Karl. Right now the F/S is mounted on DM(Server_2) can I create a VDM and mount the F/S on VDM after replication/switch over? And when it comes to CIFS share permission I need to copy manually right?
Also since this is a mixed protocol when I perform switch over should I switchover the NFS first then CIFS? Is there any specific order I need to follow?
Thanks again!
/Rags
umichklewis
1.2K Posts
0
November 19th, 2013 07:00
Hello!
Celerra Replicator is by far your best option. If you're using Mixed mode, due to specific settings in your environment, you'll want to make sure the destination filesystems on the VNX are mounted in the same fashion after the migration is complete. You can accomplish this by creating your filesystem in advance and mounting it with the same options, or by re-mounting after the migration is done.
If you're not licensed for Replicator on both systems, your EMC Sales Team can assist by procuring a one-time license for the duration migration.
Let us know if that helps!
Karl
Rainer_EMC
8.6K Posts
0
November 19th, 2013 08:00
If your CIFS server is on a VDM and you are replicating the VDM then shares and share permission will migrate as well
If not then you are using a different CIFS server on the dst than the source and will of course have to do that manually
maniemc
169 Posts
0
November 20th, 2013 13:00
VNX File Replication is designed mainly for DR (can be used for migrations too). It is best to keep both NFS and CIFS under VDM and replicate all the file systems and its associated VDM to the DR.
Only thing to remember is, on the destination keep the network interfaces for the data mover same name as source (IP addresses can be different).
During switchover (or failover), CIFS Servers/shares and NFS exports will automatically start on the DR. CIFS Servers will even auto register on the DNS after the failover (if your domain supports dynamic DNS - which is widely used) to make the failover transparent for cifs servers (NFS is manual).
You can refer man nas_replicate on the control station for CLI usage/ switchover-failover explation , or the Replicator Manual.
rbhat23
15 Posts
0
November 21st, 2013 06:00
My environment is different. I have a CX4-960 with NS2, all the F/S in the environment are of Mixed protocol (CIFS & NFS) and all the F/S are currently mounted on DM(server_2). I need to migrate all the F/S, shares to VNX7600.
Since it's a multi protocol, do I need to take any special caution during replication and while I switchover F/S to destination?
Thank you!
Rainer_EMC
8.6K Posts
0
November 21st, 2013 06:00
As usual you need to make sure that the dst is similarly configured to be able to provide the same service
There are several parameter and config items that aren’t replicated as part of the VDM
When in doubt create a small test files and try it before switching over production data
maniemc
169 Posts
0
November 21st, 2013 12:00
Like Rainer said, some manual config required, but in short,
1) If your NS2 runs latest VNX code, best is to migrate them to a vdm first before replicating as VDM can replicate the CIFS/NFS settings also to the VNX7600
2) If it is running ol celerra code which doest not support NFS on vdm, then on VNX7600 - you would setup corresponding CIFS server (best is to setup this via a new vdm on the VNX7600) and join to the same AD domain as in NS2
3) Once above done, you can replicate the file systems to the VNX and schedule a cut off (or test via a small test FS first like Rainer said)
4) Reverse the replication when full syncs done to make VNX7600 primary - and ensure the network is working as per your expectation and export manually as you want (This activity need an outage)