Promise VTrak: Configuring for Optimal Performance (E5000 Series)
Configure Promise VTrak RAIDs for best performance using the guidelines in this article.
These scripts are inteded to be used for Xsan and Quantum StorNext Deployments
- For the Promise VTrak E5000 series, the scripted options below are now built into the Promise WebPAM PROe. interface.
- For the Promise VTrak E5000 & J5000 Series, create and import the desired script, as described below.
- Some of the configuration scripts configure Global or Dedicated Revertible Spare Drives. In the event that a drive is replaced, data will be migrated from the Spare Drive to the replacement drive. Performance may be impacted for the duration of the migration procedure.
Note: All these scripts have ALUA (Asymmetric Logical Unit Access) enabled by default. If all your host's operating systems are ALUA compliant; you may leave ALUA enabled.
In the case that you need to disable ALUA due to your operating system's non-compliancy, following the instructions below.
Locatealua=enable:
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
Modify the alua variable in the script before importing:
ctrl -a mod -s "lunaffinity=enable, alua=disable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
Note – Please ensure that you use our default 64KB stripe size when creating and configuring your LUNs for optimal performance. Write performance may be affected if the administrator deviates from using a 64KB stripe size for their data LUNs for Xsan or Stornext.
Configure via Script
Configures a RAID Controller that will be used as an Xsan or StorNext Volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.
RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + J5600s
Configures a RAID Controller and SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, one scratch LUN, and three spares. Each Xsan or StorNext volume must contain one metadata LUN.
RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + (3) J5600s
Configures a RAID Controller and (3) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, eight data LUNs, three scratch LUNs, and five spares. Each Xsan or StorNext volume must contain one metadata LUN.
RAID Controller: Xsan (Metadata and Data) - E5800f
RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5320f + (2) J5600s
Configures a RAID Controller and (2) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, six data LUNs, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.
