UNSOLVED

MichaelFongemie

updated

14 years ago

0

1711

November 26th, 2012 21:00

VNXe to VNX Replication, Fan In Limits

I have a customer that needs to replicate 30 small remote office's content back to a central datacenter. The remote offices are too small for VNX so I'm looking to replicate iSCSI VNXe to VNX. I found the whitepaper that talks about this and it provides a good step by step but doesn't discuss fan in limits. Does anyone know what the limit is going to be to fan in replicate to a central VNX?   Thanks.

  • JonK1

    2 Intern

    •

    247 Posts

    555

    0

    Posted November 27th, 2012 00:00

    As far as the target storage system is concerned, SAN copy mimics a host. Therefore, SAN Copy does not have any fan-in limitations; only fan-out limitations. Do be aware of the maximum amount of initiators: 30x4 connections is 120 initiators on your target storage. Depending on your other hosts that are connected to this storage system, you could run into problems here

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    555

    0

    Posted November 27th, 2012 03:00

    That should be in the VNXe Simple Support Matrix

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    555

    0

    Posted November 27th, 2012 11:00

    yes

  • 555

    0

    Posted November 27th, 2012 11:00

    Some helpful information in the Simple Support Matrix about number of replication sessions supported but not specifically about fan-in. The simple support matrix was from August and says an RPQ would be necessary to replicate from VNXe to VNX iSCSI. Is this still the case?  Thanks.

  • christopher_ime

    6 Operator

    •

    1962 Posts

    555

    0

    Posted December 14th, 2012 22:00

    MARKYL,

    Firstly, welcome to the forums and thank you for being an EMC customer.

    To answer your question, in regards to the VNX as being the target (many-to-one configuration), the fan-in limit we advertise for Replicator is not in respect to the number of arrays but instead the limit is capped by the maximum number of filesystems and replication sessions.

    Search for the "Using VNX Replicator" document for your version of VNX OE for File on support.emc.com.  You will find the following statement:

    "The number of inbound replications supported on the target VNX is limited only by the file system and replication session limits."

    As for those limits, review the "VNX Operating Environment for File Release Notes" (also on support.emc.com).  For instance, as an exercise for the reader, look for the following (of course compare in relation to your model and version of VNX OE for File):

    1) Maximum number of filesystems per cabinet (note the footnote about what this consists of such as PFS, chkpts, etc)

    2) Maximum number of filesystems per data mover (note the footnote about what this consists of such as PFS, chkpts, etc)

    3) Maximum number of replication sessions per data mover

    4) Maximum number of active replication sessions (anything over that will be queued)

    5) Maximum number of active initial copies (not in the release notes but you'll find that listed in the Using VNX Replicator paper)

    Finally, as for a good walk-through on setting up replication between a VNXe and VNX, use the following (older) paper as a foundation:

    https://support.emc.com/docu34515_Replicating-VNXe-CIFS-NFS-Shared-Folders-to-VNX-—-Technical-Notes.pdf

  • 555

    0

    Posted December 16th, 2012 09:00

    Still requires a painful RPQ?

    Michael Fongemie

  • christopher_ime

    6 Operator

    •

    1962 Posts

    555

    0

    Posted December 16th, 2012 11:00

    No not for MARKYL's situation where is he is using Replicator (to/from VNXe and VNX data movers) to protect CIFS shares and/or NFS exports.  The RPQ mentioned previously is only required when the configuration requires iSCSI LUNs from the data movers (not SP's) of the VNX which is the configuration required to protect iSCSI LUNs from a VNXe.  Just to mention it, this is true with or without Replicator.