Qualified with Mac OS X, Mac OS X Server, and Xsan 2; Apple MPIO capable Warranty Every VTrak E-Class RAID subsystem is backed by the Promise 3-Year Limited Warranty with 24/7 telephone and email support. When Promise support confirms a failure in the field, advanced replacement parts are always available to eliminate downtime. Amazon.com: Promise Technology VTrak E-Class for Mac OS X 3U/16-bay with 4X 1TB Drives Installed TV270VC/A: Computers & Accessories.

Hello Paradeshi:

It is possible to have multiple computers accessing the VTrak at the same time. If you have a dual port card in your Mac, you will need to connect each computer to both controllers in the back of the VTrak. Each controller will have 4 fiber channel ports. This should allow for both computers to see the volume.

NOTE: The VTrak does not control which computer has read and write access to the volume. If both computers have direct access to the volume, it will cause corruption. You will need SAN software to manage write access to the volume to prevent this. A couple of examples for SAN Software are XSan or SANmp.

The other route you can go is to have a volume isolated to each server. This will prevent the computers from overwriting the same areas of data that can cause the corruption.

Promise Vtrak Support

If you would like more information about setting up the VTrak to work with multiple hosts, you can call Promise Technical Support at 1 (408) 228-1500. Our VTrak line is open 24x7.

Best Regards

Kris

Promise Technical Support

Apr 27, 2013 6:01 PM

Promise Vtrak Efd For Macro

P B posted this 18 October 2016 - Last edited 08 May 2019

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 QuantumStorNext 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.

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

Determine which script you should use from the following list, then click the linked article to get the text of the script. Follow the instructions in the linked article to save the script, then return to this article.

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: Xsan (Metadata and Data) - E5600f
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
Efd

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

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, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + J5600s

Configures a RAID Controller and a 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 two spares. Each Xsan or StorNext volume must contain one metadata LUN.

Promise Vtrak Efd For Machine Learning

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + (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, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

Promise Vtrak E830f

Promise Vtrak M500i

RAID Controller: Xsan (Metadata and Data) - E5320fConfigures 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.
Configures a RAID Controller and a 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, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.

Configures a RAID Controller and a 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, and four spares. Each Xsan or StorNext volume must contain one metadata LUN.

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.