Best Practices for Configuring and Using the SAN

If you have two partner storage servers in a high load environments, you may wish to incorporate some of the practices outlined below to optimize the performance of your SAN, as well as the management of your SAN in the event of failure, or when upgrading or modifying your configuration.

Environment

  • Your storage servers should be dedicated to only running SANmelody software. Do not use them for any other purpose.

  • If using storage server partners for high availability, design your SAN network so that all storage devices (physical storage, storage servers, switch fabrics) allow for the shutdown of a complete storage path from application server through physical disk without impacting other paths. This allows for the event (upgrade, failure, addition, and so forth) to occur with minimal impact.

  • Label cables and host bus adapters (HBAs).

  • Separation of components leads to a higher degree of availability because they are not in the same environment.

    • Keep storage servers out of the public network.

    • Separate servers from storage racks.  

    • Keep switches in separate racks.

    • Do not take power from the same grid (if possible).

 

Hardware Configuration

  • Calculate I/Ops required by the application server layer and then decide on the number of application server ports to use. Alternatively, the following handles average traffic:

    • Two storage server target-only ports

    • Two unidirectional dedicated mirror ports

    • Two storage server initiator ports

  • Physical storage performance is a key factor to overall system performance, particularly in high load environments.

  • DataCore storage servers implement a RAID1 mirror when synchronous (secondary) mirroring is used with multipathing.

  • Application vendors’ recommendations for separate disks translates directly to separate pools for virtual disk sources.

 

High Availability Configuration

  • Use LUN distribution if your storage controller supports an active/active configuration. LUN distribution requires TRUE active/active functionality from the storage subsystem with multiple controllers.

  • If you intend on setting up the Windows application server for HA using MPIO, then install MPIO before mapping third party AP volumes to the application server.

  • Paths from each application server to each storage server should be physically independent. This means physically separating switches for Fibre Channel (FC) and independent subnets and switches for iSCSI provide the highest level of availability.

  • If using iSCSI. refer to Best Practices for iSCSI High Availability.

  • If mapping the same virtual volume to multiple application servers, refer to LUN Numbering Consistency.

 

Related Topics:

Planning for AIM

Best Practices for Mirroring

Best Practices for Configuring and Using the SAN