How can I configure my two VNXe systems to replicate?
I have tho VNXe 3100 storage systems, one for production and one for DR. I have installed Replication Manager server on a host, and the production host connected via iSCSI to the production VNXe. The production host has PowerPath, Unisphere server agent and Replication manager host installed. I have read several documents about Replication Manager but I have not found how to configure the ports that each VNXe will use for replication purposes. Which VNXe ethernet ports should I configure for replication? I have a total of six ethernet ports on each SP, two of them on each SP are being used for iSCSI conectivity.
We do the same thing EXCEPT we use NFS instead of iSCSI. For ours i have grouped the 4 nics on the expansion card together and grouped the 2 built-in nics together. I use the 4 aggregate NIC as the NFS traffic ports and the 2 aggregate NIC as the Replication traffic ports. The Replication aggregate is in a seperate vLan as well.
I use NFS instead of iSCSI so i do not have to use replication manager so the steps may be a little different but i would think the Network config would still be the same (but i could be wront there too). The overhead for iSCSI replication is ridiculously high. Make sure you have twice the amount of space you need to use availble for the iSCSI replication.
You can go to "Settings - More Configuration - Advanced Configuration" to aggregate the nics.
Then with NFS you would go to "Settings - Share Folder Server Settings" to create the rest....as for iSCSI im sure it would be different at this step.
Would you care to share you replication strategy with us?
I will be looking to do some DR implementation in the coming year, and I am only using NFS for my VM's. I understand that Replication Manager is really only needed if you are using iSCSI, but I can't get a concrete answer from my vendor as to what I would need to do in my environment. Any insight would be greatly appreciated.
Thanks a lot for the comments all of you. The video shows all the configuration that must take place for using Replication Manager for the VNXe. Some aditional information a can share of what I have done so far is in this documents that helped me a lot: Replicaton Manager Administrators Guide and product guide EMC® VNXe™ Series Using a VNXe System with Generic iSCSI Storage.
This tech note discusses the steps required to implement and configure remote replication between a VNXe system and a VNX system, including the steps to initiate a switchover and failover.
July 12, 2011 | English | pdf | 6.0 MB | White Paper
You DO NOT need Replication Manager if you are only replicating NFS (or CIFS). You can replicate NFS directly thru the VNXe3100 itself which is nice. In our environment i have it set up like this (Each of our VNXe3100s have dual SPs):
I have each SP with the 4-port nic Aggregated and the built-in 2 port Aggregated (you can not Aggregate the Built-in nics with the add-on Nic ports...which is really a shame). I have both aggregates setup with vlan tagging. This allows me to set the 4-port aggregate to the NFS vlan and the 2 port aggregate with the Replication vlan. The VMWare hosts ONLY seee the 4 port aggregate (which is the NFS vlan) and only the two VNXe3100s see the the 2-port aggregate (which is Replication vlan). This gives us a 4gb channel to our VMware hosts so we have plenty of bandwidth for them and keeps the replication traffic seperate.
Then you will create a "Shared Folder Server" for the NFS storage for each SP. So in my case i have a shared storage server for SPA and SPB (each of course with diffrent IPs on the NFS vlan). Then i created another shared storage server for each SP that used the Replication vlan IP
Example of Shared Folder Servers:
PRIMARY SYSTEM
SPA_NFS (10.0.1.1) - Part of 4-port Aggregate
SPA_REP_NFS (10.0.2.1) - Part of 2-port Aggregate
SPB_NFS (10.0.1.2) - Part of 4-port Aggregate
SPB_REP_NFS (10.0.2.2) - Part of 2-port Aggregate
SECONDARY SYSTEM
SPA_NFS (10.0.1.3) - Part of 4-port Aggregate
SPA_REP_NFS (10.0.2.3) - Part of 2-port Aggregate
SPB_NFS (10.0.1.4) - Part of 4-port Aggregate
SPB_REP_NFS (10.0.2.4) - Part of 2-port Aggregate
With he above layout you can create multiple NFS storage and assign them to either SPA or SPB to load ballance the system...so the first NFS storage would go to SPA_NFS, the second to SPB_NFS, the third to SPA_NFS, the fouth to SPB_NFS....and so on to laod balance the SPs.
For replication you would assign an SPA NFS share to replicate between the Primary system SPA_REP_NFS to the secondary system on SPA_REP_NFS......for an SPB NFS share you would set the replication to go from Primary system SPB_REP_NFS to the secondary system SPB_REP_NFS
fishermc-woffor
61 Posts
1247
1
Posted December 8th, 2011 08:00
We do the same thing EXCEPT we use NFS instead of iSCSI. For ours i have grouped the 4 nics on the expansion card together and grouped the 2 built-in nics together. I use the 4 aggregate NIC as the NFS traffic ports and the 2 aggregate NIC as the Replication traffic ports. The Replication aggregate is in a seperate vLan as well.
I use NFS instead of iSCSI so i do not have to use replication manager so the steps may be a little different but i would think the Network config would still be the same (but i could be wront there too). The overhead for iSCSI replication is ridiculously high. Make sure you have twice the amount of space you need to use availble for the iSCSI replication.
You can go to "Settings - More Configuration - Advanced Configuration" to aggregate the nics.
Then with NFS you would go to "Settings - Share Folder Server Settings" to create the rest....as for iSCSI im sure it would be different at this step.