Thanks a ton Karl.

3.  The Datamover Interconnect only requires the IPs to be in the same VLAN for replication purposes.  For example, if the primary VNX has interfaces on VLANs 10, 20 and 30, the secondary VNX needs to have an interface on only one of those VLANs for replication to work.  HOWEVER, if your clients expect to reach your secondary VNX on the same VLANs (IPs), you will need to provide the same VLAN to the secondary VNX.  So, in your example, if your NFS exports are on VLAN A, your secondary VNX needs a port on VLAN A to offer them up to clients on the same IP addresses.  However, if you intend to update DNS or you have static /etc/hosts files on your clients, you may not need to provide those VLANs.

From the above i have question to ask,

So does it mean "IP address" on local side of interconnect and "IP address" on peer side of interconnect need to be on same VLAN but can be on any VLAN?

For example : On the primary VNX we have interfaces on VLANs 46 and 47 and also secondary VNX has interfaces on VLANs 46 and 47, my question is related to replication session, can the Ip addresss on local side of interconnect and peer side of interconnect be on VLAN 100 or it has to be on either 46 or 47 for replication to take place?

There are two sides to this.

For just the pure data replication to work it is only necessary that:

- Control station on one side can talk via IP to the other control station for replication control

- Data mover on the one side can talk via IP to the other side data mover for data transfer

For this it doesn’t matter whether they are on the same VLAN or not.

Of course if also want to be able to failover then your DR system must be configured so that your clients are able to access it.

Whether that is on the same VLAN or not doesn’t matter.

IF you need that transparent (without having to reconfigure the clients) then you need extra care.

I would suggest for first take a look at the Replicator manual

Thanks Rainer_EMC

In our case, already 2 network interfaces have been created on secondary VNX with IP's on the same VLAN as of primary VNX to export NFS

I was asking for pure replication purpose... you explained it very clearly thanks

I have worked on File System Replication and everything looks good, now my question is, during replication is in progress, how NFS exports to be created & maintained on the secondary system? such that during a Failover or Switchover of a filesystem the clients can access the destination object immediately.

In simple how the NFS exports properties should be on secondary system while replication of file system is active??

Thanks in advance

Dino

If you use VDM based NFS exports they get replicated with the VDM

If not you have to do it yourself.

Keep in mind the regular Replicator failover will not transfer IP addresses – so might have to re-mount on the clients as well.

It is not a VDM based NFS exports,

So if i have to create the NFS exports on the secondary system, shall i give a dummy Path and rest all the fields (DATA MOVER, FILE SYSTEM, IP ADDRESSES OF READ/WRITE HOSTS) same as the primary one. So that during a switchover or failover just "Path" field alone can be modified. Will this approach on NFS export work??

Thanks

You don’t need dummy path – the file system are there on the secondary but readonly

I would create a script

You need to test it and work out the procedures.

Also keep in mind that the file handles most likely change so a client NFS remount is necessary.

If you need more you can engage your local resources or professional service for procedures and workaround.

Sorry for the late reply, first of all thanks.

Yes, i created a replication session for a file system followed with NFS export creation on the secondary side. Now, I tested by mounting the NFS export from the secondary side using one of its interface to a local server and i was able to see all the files been replicated and also it was a R/O file system.

Here is one more Question,

We know the Checkpoints will be created on both ends of the array on the pool we choose, my question is the checkpoint space occupied in the pool during replication session creation will remain constant thereafter or it will vary ?

it will very depending on change rate and size, as you know check points are used to provide point in time recovery.