Field

Description

Name

Name given to the virtual volume. This name can be changed in this dialog box or by using the Rename option if the virtual volume is not mapped. (Traveller rollback virtual volumes names cannot be changed.)

Model

Return string from a SCSI Inquiry of the virtual volume. The default is DataCore (vendor) SANsymphony (product ID). You can customize fields for vendor, product ID, and revision by selecting Custom from the pull-down menu and then clicking Custom Model…. Enter the information in the Custom Model dialog box that opens and click OK when finished.  

Logical Size

Size of the LUN  that application servers discover when the virtual volume is mapped. This size cannot be changed when virtual volumes are mapped. The maximum size (following) is the largest valid size.

Reducing the logical size when data exists on the virtual volume, will not remove data, but the application server will not be able to access any data past the new smaller size.

When the logical size is enlarged, file systems on the virtual volume will not be extended, only the size of the mapped LUN is enlarged.

Resizing is also not available with Mapstore or Snapshot virtual volumes.

Maximum Size

Logical size of the smallest volume comprising the virtual volume. This is the maximum logical size allowed and cannot be changed.

Write Through Mode

When enabled, all writes sent to the virtual volume will no longer use cache on the storage server and are sent directly to storage. Although performance may be affected, this feature is recommended for AIM destination virtual volumes.

Replace Volume on Failure

Select this option to flag all volumes within a virtual volume for replacement by a hot spare in the event that any of the volumes fail.  When a failure occurs, the bad volume is automatically swapped with a previously created hot spare. This feature is unavailable for linear virtual volumes.

Refer to Configuring Hot Spare Replacements for more information.

Allow Unaligned Sizes

Enable this option to accommodate volume size differences that may occur in certain situations:

• The default size of NMVs created in SANsymphony software prior to version 5.1 were larger than the default size used in 5.1 and later. Snapshot and AIM require destination virtual volumes equal to or greater than the source, so if the possibility exists that NMVs created prior to the 5.1 release could be used as source virtual volumes, enable this option to accommodate the differences.

• Proxy volumes may exist that have sizes that are not aligned on 512MB boundaries.

This option is automatically enabled when the system detects the creation of a virtual volume with volumes that are not on 512MB boundaries so their sizes will remain unchanged.

Secondary is Preferred Path

This option only applies to virtual volumes being mapped to application servers using DataCore Alternate Pathing (AP) and DataCore MPIO (3PAP) products. By default, the preferred path to use is the path to the primary volume. Enable this option to use the path to the secondary volume as the preferred path to use for I/O.

Persistent Reserve

When enabled, the virtual volume can support the SCSI-3 Persistent Reserve commands. Automatically enabled and locked when Asymmetric Logical Unit Access (ALUA) is enabled.

Note: Enable the option before mapping the virtual volume. Persistent Reserve cannot be enabled after the virtual volume is mapped.

Asymmetric Logical Unit Access

When checked, enables support of SCSI-3 target port group commands (ALUA).

Note: Enable the option before mapping the virtual volume. ALUA cannot be enabled after the virtual volume is mapped.

Mirroring Area

Path Options

Selections provide the type of mirror mappings to create.

Alternate Path (AP)

Select this option when mapping to application servers running DataCore Alternate Pathing.

Bootable - Select this option when the virtual volume is to be used for booting from the SAN.

Manual Failback - Select this option when you do not want the application server to automatically failback to the preferred path. Once healthy, the path can be switched back manually via the Failback to Primary Path feature, available from the virtual volume context menu in SANcentral Status tab.

 3rd Party AP / MPIO (3PAP)

Select this option when mapping to application servers running DataCore MPIO or a third party multipathing software.

Cluster Path  / Manual Mappings (CP)

Select this option when mapping to Windows servers running Microsoft Clusters that only have a single Fibre Channel or iSCSI connection are not using the options for DataCore Alternate Pathing or DataCore MPIO.

Standard

Select this option when application servers only have direct access to the primary storage server (no direct access to the secondary server). For this mirror type, data is transferred to the primary, and then mirrored to the secondary. Standard mirrors can be split while mapped, refer to Splitting a Mirror.

Primary Storage Domain Server

The primary storage server is the storage server whose volume was used to initially create the virtual volume. The mirror is provided by the secondary storage server and, if available,  the tertiary server provides an additional mirror (I/O direct from the primary). By default, for application servers running DataCore Alternate Pathing or DataCore MPIO, the primary storage server is considered the preferred path.

Recovery Priority

Allows you to designate mirror recovery. According to importance, select the recovery priority— from 0 (low) to 3 (high). The default is 0. Refer to Setting Mirror Recovery Priority.

Mappings Area

Mapping Type

Types include Mirror, Primary, or Secondary. For mapping icon information, refer to the Mappings icons in SANmanager Icons.

Initiator Channel

Alias of the channel sending data to the storage server.

Target Channel

Alias of the channel receiving data during the transfer.

LUN

SCSI identifier of a logical unit (corresponding to a virtual disk) of a storage device. Can be changed in Mapping Properties dialog box.

Access Rights

Access rights of the volume include Read-Only or Read-Write. Rights can be changed in the Mapping Properties dialog box. Refer to Mapping Properties.

Note: Some application servers cannot use a Read-Only volume,  i.e., Windows NT.