Configuring StorNext File System on Windows
To configure StorNext File System or the StorNext client on Windows operating systems, use the Windows configuration utilities. The configuration utilities let you set up a Windows-based Metadata Controller, configure a StorNext client, and work with StorNext file systems.
This section contains the required steps to configure StorNext, and also provides a description of all the other configuration utilities that StorNext provides.
Once you have installed StorNext, follow these steps to configure StorNext. These steps are all covered in this section.
1. | Obtaining and Installing a Permanent License |
2. | Configuring Name Servers |
3. | Labeling Disk Drives |
4. | Configuring a Server (Advanced) |
5. | Configuring the Client |
This section covers the above configuration utilities plus all of the additional Windows configuration utilities. See:
Available Configuration Utilities
Accessing the Configuration Utilities
Available Configuration Utilities
The following configuration utilities are accessible from the Windows Start menu (Start > All Programs > StorNext File System).
For more information on using these utilities, see the online help accessible from Start > All Programs > StorNext File System > StorNext Help.
Configuring the Client : Use this utility to view and modify properties for the StorNext client software.
Labeling Disk Drives: Formats hard disks so they can be used by StorNext.
Configuring a Server (Advanced): Allows you to configure StorNext file systems. This tool provides access to advanced features of StorNext File Systems. It is assumed that you are familiar with individual features available in the File System Cfg File (.cfg).
Configuring the File System Startup List: Allows you to check StorNext file system health status while the file system is active. You can note changes but not commit them in read-only mode. You can also list all of the existing files and their pertinent statistics, such as inode number, size, file type and location in the file system.
Repairing a File System: Allows you to check file system health and repair metadata corruption. You can also list all of the existing files and their pertinent statistics, such as inode number, size, file type and location in the file system.
Re-initializing a File System: Allows you to re-initialize an existing file system or initialize a file system for the first time.
Caution: Use extreme caution when using this tool. This will destroy all data on the selected file system.
Configuring the File System Startup List: Allows you to define which File System Manager (FSM) daemons to start.
Retrieving the Host License Identifier: Use this utility to display the host license identifier. The host license identifier is required to obtain a permanent license for StorNext.
Obtaining and Installing a Permanent License: Allows you to import StorNext licenses.
Editing Drive Mapping: Specifies the name server(s) used by StorNext File System services.
Server Administration: Allows you to look at the current status of file systems and to start, stop and perform basic file system administration tasks (similar to the cvadmin CLI).
Starting File System Services: Use this utility to start all StorNext services on an MDC or StorNext client.
Obtaining Version Information: Use this utility to stop all StorNext services on an MDC or StorNext client.
Stopping and Removing File System Services: Use this utility to stop all StorNext services on an MDC or StorNext client, and also remove registry entries that automatically start the services on bootup.
StorNext Help: View StorNext help for these utilities and other commands.
Obtaining Version Information: View information about the currently installed version of the StorNext server and/or client software, such as the version number, build number, and platform.
Accessing the Configuration Utilities
There are two ways to access the configuration utilities:
Using the StorNext Configuration Window
Using the StorNext Configuration Window
As soon as you finish installing StorNext, the StorNext Installation window remains open (see Figure 9). If you wish to begin configuring immediately, click the Configure StorNext button to open the StorNext Configuration window (Figure 1).
You can return to the StorNext Configuration window at any time by double-clicking the file named SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit systems) and then clicking the Configure StorNext button.
Figure 1: StorNext Configuration
The StorNext Configuration window provides buttons to access several of the most common configuration utilities:
Name Servers — See Editing Drive Mapping.
Label Disk Drives — (Not available for client-only configurations.) See Labeling Disk Drives.
Import/Export Client Settings — See Restoring a Previous StorNext or StorNext FX Client Configuration.
Client Configuration — See Configuring the Client .
Using the Windows Start Menu
You can access all of the configuration utilities, along with several others, from the Windows Start menu.
To run a configuration utility from the Windows Start menu, click Start > All Programs > StorNext File System, and then click the utility.
Retrieving the Host License Identifier
Use the License Identifier utility to display the host license identifier. The host license identifier is required to obtain a permanent license for StorNext.
To run the License Identifier utility, on the Windows Start menu, click All Programs > StorNext File System > License Identifier. A dialog box displays the host license identifier. Record this information.
Obtaining and Installing a Permanent License
To obtain StorNext component and feature licenses, see the “Obtaining Licenses” section in the StorNext Licensing Guide. After following those steps, you will receive a license.dat file from Quantum.
To install the license:
1. | Copy the file to the C:\Program Files\StorNext\config directory. (If there is a temporary license file, rename the file or move it to a backup location.) |
Note: To prevent accidentally losing a valid license, be sure to back up or rename any existing license.dat files.
2. | Install StorNext File System (see Installing StorNext File System on Windows MDCs). Licenses can be installed as part of the installation process or later if desired. |
3. | If installing licenses after the initial install, click Start > All Programs > StorNext File System > Licenses. |
The StorNext License screen displays (see Figure 2).
4. | Click Import License File. |
The License Import File window opens (see Figure 3).
Figure 3: License Import File Window
5. | Browse to the license file location and click Open. |
The licenses are installed and a confirmation dialog box displays.
6. | Click OK. |
The StorNext License screen displays again.
7. | Close the window by clicking the X in the upper right corner. |
The Installation Complete dialog box displays (see Figure 4).
Figure 4: Installation Complete
8. | Click OK in the Installation Complete dialog box. |
9. | Reboot the system if instructed to do so. |
Configuring Name Servers
The purpose of a File System Name Server is to track the IP addresses of StorNext component servers, such as file system servers and gateways. StorNext SAN clients and LAN clients query name servers to locate appropriate services. The name server is a critical component for handing failover.
Every computer running StorNext components must have an fsnameservers file. The default location is:
Program Files\StorNext\config\fsnameservers
At least one, but preferably two of the systems that have StorNext Server installed must be designated as a StorNext Name Server. The Name Server and Metadata Controller (MDC) can be the same machine.
Note: The Name Servers configuration (including the ordering) must be identical on every computer running StorNext.
StorNext name servers can be added as either IP addresses or computer names, but when possible you should use IP addresses to avoid ambiguity.
Follow these steps to add a name server:
1. | Access the name servers utility from the Windows Start menu (Start > All Programs > StorNext File System > Name Servers). |
Note: You may also access the name servers utility from the StorNext configuration window (see Using the StorNext Configuration Window).
The StorNext Name Servers window appears (Figure 5).
Figure 5: StorNext Name Servers Window
2. | Enter the IP address, and then click Add. The IP address will be added to the list on the left side of the window. |
3. | If desired, manipulate the order by selecting a name server and then clicking Move Up or Move Down. Name servers will be used in the order specified. |
Note: The Name Servers configuration (including the ordering) must be identical on all computers running StorNext.
4. | To remove a name server, click the name server you want to remove and then click Remove. Confirm the deletion when prompted. |
5. | When you are finished adding name servers, click OK. |
Labeling Disk Drives
(Not available for client-only configurations.) The Disk Labeler lets you configure StorNext File System storage area network (SAN) disks. Each disk that is to be used in the file system must have a StorNext File System Label. The Disk Device Label Tool formats the disk so it can be used by StorNext. Use the Disk Device Labeler to create a list of disk labels, associated device names, and (optional) the sectors to use.
Run the Disk Device Labeler on a system that has visibility to all disk devices on the SAN.
Caution: Use extreme caution when labeling your storage area network disk devices. Inadvertently labeling a Windows system disk will cause irreparable harm to your system and/or loss of data! Only label disk devices that are intended for use with the StorNext File System SAN.
The file system uses the volume labels to determine which disk drives to use. The label name written to a disk device must match the disk name specified in the Server Configuration utility (see Configuring a Server (Advanced)).
Follow these steps to label disks:
1. | Access the disk labeler from the Windows Start menu (Start > All Programs > StorNext File System > Disk Labeler). |
Note: You may also access the disk labeler from the StorNext configuration window (see Using the StorNext Configuration Window).
The StorNext File System Disk Labeler window appears (Figure 6). All disk devices are scanned for labels, and those devices with labels are displayed.
Note: The label type “NotVerified” is used for disks that are unusable or represent a secondary (passive) path to a disk that appears elsewhere in the list. The label type “TooLarge” is used for disks that have valid StorNext labels, but are not usable on this system without re-labeling, because the system SCSI driver cannot access disk blocks beyond block number 4294967295.
Figure 6: File System Disk Labeler
2. | Do one of the following: |
Click Label to write a volume label to the selected device(s) (see Labeling Disks below).
Click UnLabel to remove the existing volume label from the selected device(s).
Click Exit to quit the Disk Device Labeler utility.
Click Probe Disk(s) to pulse the activity light of the selected device(s). Use this feature to correctly identify disks before labeling them.
Click Clear Selections to deselect all devices in the list.
Labeling Disks
Follow these steps to label a disk:
1. | Select the disks you wish to label. (If desired, verify that the disks selected are the correct ones by pressing the Probe Disk(s) button. The activity light on selected disks will pulse, allowing visual verification that the correct disk drives are selected. This procedure will continue until you click the Stop button.) |
2. | After you have verified that the correct disk devices are selected, press the Label button. |
A confirmation screen appears asking if you are sure you want to proceed.
3. | Click OK to continue. |
4. | A properties screen (Figure 7) for each disk appears, one at a time. This screen allows you to name the disk and assign the configured number of sectors to use on the disk. |
Figure 7: Disk Labeler Properties
5. | Enter the following fields: |
New Disk Label: The label you want to give the disk.
New Sectors: The number in 512-byte sectors you will use in the DiskType configuration during file system configuration.
Normally you will use the default number of new sectors provided by the tool. However, some disks must be configured smaller than their actual size. For example, MPIRE video disks must be under-configured to eliminate using the last zone of the disk.
6. | Press the Create Label button to commit the label to the disk device. If more than one disk was selected, a properties screen for the next device will appear until all of the selected devices are completed. (Pressing Skip Disk allows you to not write a label to the disk and instead proceed to the next selected disk.) |
Configuring a Server (Advanced)
(Not available for client-only configurations.) The Advanced Server Configuration utility lets you view and modify properties for an MDC. Use this utility to create a new server configuration or modify an existing configuration. This tool provides access to advanced features of StorNext File Systems. It is assumed that you are familiar with individual features available in the File System Cfg File (.cfg).
1. | Access the advanced server configuration utility from the Windows Start menu (Start > All Programs > StorNext File System > File System Cfg (Advanced)). |
The File System Configuration window displays (Figure 8).
Figure 8: Configuration Administrator
2. | Do one of the following: |
Click the Create New Configuration button to create a new configuration file.
Select an existing file and click the Open Existing Configuration button to edit an existing configuration file.
The Properties window displays (see Figure 9). This window includes four tabs:
3. | Click a tab to view or modify StorNext File System properties. After making changes on one or more tabs, click OK to save the changes. Specify a name and a location for the *.cfg file, and then click Save. |
Note: Before configuring a file system, you should label disk devices. For more information, see Labeling Disk Drives.
Global Settings
Use the Global Settings tab (Figure 9) to specify general file system properties. Table 1 describes the fields on the Global Settings tab.
Figure 9: Properties: Global Settings
Table 1: Server Configuration: Global Settings
Field/Button |
Description |
Disk |
|
Allocation Strategy |
Select the method of allocation for new disk blocks: Round: Alternate between similar stripe groups. (Default) Fill: Use the stripe group with the least amount of free space (that can accommodate the file) before using the stripe group with the next smallest amount of free space. Balance: Use the stripe group with the most free space. |
Inode Stripe Width |
(Optional) Specify a value in MB. This feature defines how a file is striped across the file system’s data stripe groups. See the Windows on‑line help for additional information. |
Allocation Session Reservation Size |
(Optional) Specify the size (in MB) this feature should use when allocating segments for a session. This features allows a file system to benefit from optimized allocation behavior for certain rich media streaming applications, and potentially other workloads. The feature also focuses on reducing free space fragmentation. This feature is disabled by default; a value of 0 is the default value, which means the feature is turned off. When enabled, the value can range from 128 MB (134217728) to 1 TB (1099511627776); the largest value would indicate segments are 1 TB in size, which is extremely large. |
Journal Size |
Type the maximum size (in MB) for the journal. |
Max Debug Log Size |
Type the maximum size (in MB) for the debug log. |
Memory |
|
Inode Cache Size |
Type the number of entries in the inode cache. |
Buffer Cache Size |
Type the amount of memory (in MB) used for general metadata information caching. |
Performance |
|
Cluster File Locking |
(Optional) Select to send a warning when a user attempts to access a file that is locked or already in use. |
Security |
|
Global Superuser |
(Optional) Select to allow a user with superuser privileges to have global access rights on the file system. |
Windows Security |
(Optional) Select to use Windows Security Reference Monitor (ACLs) on Windows clients. |
Use Active Directory SFU |
(Optional) Select to enable or disable the use of Microsoft’s Active Directory Services for UNIX (SFU) on Windows based SNFS clients. Always use Active Directory SFU in a mixed Windows/Unix environment, or if there is a possibility in the future of moving to a mixed environment. If Use Active Directory SFU is disabled, files created on Windows based SNFS clients will always have their UID and GID set to NOBODY with default permissions. |
Global ShareMode |
(Optional) Select to enable or disable the enforcement of Windows Share Modes across StorNext clients. This feature is limited to StorNext clients running on Microsoft Windows platforms. See the Windows CreateFile documentation for the details on the behavior of share modes. When enabled, sharing violations will be detected between processes on different StorNext clients accessing the same file. Otherwise, sharing violations will only be detected between processes on the same system. |
XSAN Client Behavior |
|
Xsan Named Streams |
(Optional) Select to enable or disable support for Apple Named Streams. Named Streams are utilized by Apple Xsan clients. Enabling Named Streams support on a file system is a permanent change. It cannot be disabled once enabled. Only Apple Xsan clients should be used with named streams enabled file systems. Use of clients other than Apple Xsan may result in loss of named streams data. |
Enforce ACLs |
(Optional) Select to enable Access Control List enforcement on XSan clients. On non-XSan MDCs, Windows Security should also be enabled for this feature to work with XSan clients. |
Default Unix User Mapping |
|
"Nobody" UID |
Type the Windows user ID to use when no user ID can be found using Active Directory. |
"Nobody" GID |
Type the Windows group ID to use when no group ID can be found using Active Directory. |
Default File Mode |
Type the permission mode to use when creating files. |
Default Directory Mode |
Type the permission mode to use when creating directories. |
Use Fabricated IDs |
Select if the Metadata Controller is running on Apple MacOS X. |
Quotas |
|
Use Quotas |
(Optional) Select to enforce file system quotas and track storage usage for individual users and groups. |
Duration of Quota Logs |
Type the duration (in days) of the system quota logs. |
File Size Dynamic Expansion |
|
Minimum |
(Deprecated) Type the minimum number (in blocks) to allocate when a file is created. |
Increment |
(Deprecated) Type the initial increment (in blocks) by which a file is expanded. |
Maximum |
(Deprecated) Type the maximum increment (in blocks) by which a file is expanded. |
Disk Types
Use the Disk Types tab (Figure 10) to define disk types used in the file system.
Figure 10: Server Configuration: Disk Types
On the Disk Types tab, do one of the following:
To add a new disk type, click New.
To modify a disk type, select the disk type in the list and click Edit.
To delete a disk type, select it in the list and click Delete.
When you add or modify a disk type, the Disk Type Editor dialog box appears (Figure 11). Table 2 describes the fields on the Enter New Disk Type dialog box.
Note: The Sectors and Sector Size fields are populated with values from the Disk Labeler utility. For more information, see Labeling Disk Drives.
Figure 11: Server Configuration: Enter New Disk Type
Table 2: Server Configuration: Enter New Disk Type
Field / Button |
Description |
Disk Type |
Type a descriptive name for the disk. |
Sectors |
Type the number of physical sectors on the disk. |
Sector Size |
Type the size of sectors on the disk. |
OK |
Click to create the new disk type with the specified properties. |
Cancel |
Click to close the Disk Type Editor dialog box without saving changes. |
Disk Definitions
Use the Disk Definitions tab (Figure 12) to create disk definitions and modify disk specifications. Table 3 describes the fields on the Disk Definitions tab.
Figure 12: Server Configuration: Disk Definitions
Table 3: Server Configuration: Disk Definitions
Field / Button |
Description |
Disks Available - New |
Click to create a new disk definition. Type a name for the disk and click OK. |
Disks Available - Delete |
Click to delete the selected disk definition. |
Status: Up |
Select to enable the selected disk definition. When enabled, the defined disk is available to the configured file system for I/O. |
Disk Type |
Select a disk type for the selected disk definition. (Disk types are defined on the Disk Types tab.) |
Device Names - New |
Click to add a device name to the disk definition. Type a device name and click OK. |
Device Names - Delete |
Click to delete the selected device name. |
Stripe Groups
Use the Stripe Groups tab (Figure 13) to define stripe groups. (A stripe group is a logical storage unit consisting of one or more disk drives.) Table 4 describes the fields on the Stripe Groups tab.
Figure 13: Server Configuration: Stripe Groups
Table 4: Server Configuration: Stripe Groups
Field / Button |
Description |
Stripe Groups Available - New |
Click to create a new stripe group. Type a name for the stripe group and click OK. |
Stripe Groups Available - Delete |
Click to delete the selected stripe group. |
Status: Up |
Select to enable the selected stripe group. When enabled, the stripe group is available to the configured file system for I/O. |
Exclusive |
Select to allow only file types associated with the affinities specified under Affinities to be stored on the stripe group. |
MetaData |
Select to allow file system metadata to be stored on the stripe group. |
Journal |
Select to allow the file system logging journal to be stored on the stripe group. |
Stripe Breadth (Blocks) |
Describes the number of file system blocks that are appended to a file before switching to the next disk in the stripe group. |
Affinities - New |
Click to add a new affinity to the stripe group. Type the name of the new affinity and click OK. (Affinity names cannot be longer than eight characters.) |
Affinities - Delete |
Click to the delete the selected affinity. |
Pathing Method |
Select a method for how the file system accesses the disk: Rotate: Chooses an I/O path based on load. Static: Always uses the same I/O path. Sticky: Chooses an I/O path based on the identity of the target file. |
Rtios |
Type the maximum number of disk I/O operations per second available to real-time applications using the Quality of Service (QOS) API. |
RtiosReserve |
Type the minimum number of disk I/O operations per second reserved for non-real-time applications. |
RtTokenTimeout |
Type the number of seconds to wait for clients to respond to a token callback. |
Rtmb |
Type the maximum number of MBs per second available to real-time applications using the Quality of Service (QOS) API. |
RtmbReserve |
Type the minimum number of MBs per second reserved for non-real-time applications. |
Modify Drive List |
Click to add or remove disks for the selected stripe group. Use the left and right arrows to add or remove disks in the Primary Disks list, and then click OK. |
Caution: When adding a disk to an existing stripe group, make sure the disk is added to the bottom of the Drive List. If the disk is inserted in the middle of the list, the file system behaves as if files on the file system are corrupted.
Importing and Exporting Client Settings
This feature is described in Restoring a Previous StorNext or StorNext FX Client Configuration.
Configuring the Client
In order for a client to access a StorNext file system, the file system must be mapped to a folder or drive letter. The Client Configuration Tool maps a StorNext file system to a Windows drive letter or folder and controls various configuration settings.
The values for the Client Configuration are stored in the Windows Registry and are referenced by StorNext when the file system is mounted.
Follow these steps to configure the client:
1. | Access the client configuration utility from the Windows Start menu (Start > All Programs > StorNext File System > Client Configuration). |
Note: You may also access the client configuration utility from the StorNext configuration window (see Using the StorNext Configuration Window).
The Client Configuration window appears (Figure 14). Displayed under the File System column heading are all file systems advertised by the name server, and currently mapped StorNext file systems found in the Windows registry.
Figure 14: Client Configuration Window
The Client Configuration screen includes the following functions:
Mapping a Drive: Map a StorNext file system to a folder or drive letter.
Unmapping a Drive: Unmap a StorNext file system from a folder or drive letter.
Editing Drive Mapping: Change the drive mapping.
Configuring Name Servers: Edit, add or remove name servers.
Configuring LAN Clients and Gateway Servers
Mapping a Drive
To map a StorNext file system to a folder or drive letter, double-click the desired file system (or select it and click the Map Drive icon or Tools > Map Drive). The Client Properties screen appears.
Use the Mount Point tab (Figure 15) to specify drive mappings. Table 5 describes the fields on the Mount Point tab.
If your file systems are not displayed, check the status bar at the bottom. The most common problems are:
- An incorrect Name Server Configuration.
- Network problems.
- The file system is not running.
- The StorNext Services are not running.
StorNext file systems can be mapped to a drive letter or to a folder. When mapping to a folder, the following conditions must be met:
- The folder must be empty or non-existent.
- The folder must exist on an NTFS file system volume, for example:
C:\Mount\MySnfs
. - The NTFS volume must be a local volume. In other words, StorNext cannot be mounted in a folder on a Cluster Shared Volume.
Note: Verify the fsnameservers configuration is the same for all clients on the SAN. An incorrect or incomplete fsnameservers configuration may prevent the client from connecting to the file system.
Figure 15: Client Configuration: Mount Point
Table 5: Client Configuration: Mount Point
Field / Button |
Description |
Map to Drive Letter |
Select Map to Drive Letter to map the drive to a specific drive letter. |
Drive (Letter) |
Select the desired drive letter. |
Map to Directory |
Instead of selecting Map to Drive Letter, select Map to Directory. Enter a directory path, or click Browse to navigate to the directory path. |
Note: If this is a LAN client or gateway, be sure to enter the parameters on the Distributed LAN tab (see Configuring LAN Clients and Gateway Servers).
Unmapping a Drive
Select the file system you want to unmap and then click the Unmap Drive icon or select Unmap Drive from the Tools menu. You must close all applications (included Windows Explorer) which might be using the file system. If the file system is busy, you will not be allowed to unmap the drive.
Note: In order to unmap a drive, you must have Administrator rights on the local computer, and you must have read/write access to root of the StorNext file system.
Editing Drive Mapping
Once a file system is mapped, you can change the mapping by double-click the file system. Alternatively, select the file system and click the Properties button, or select the file system and click Tools > Edit Drive Mapping. This opens the Properties window where you can change drive mapping. See Mapping a Drive for instructions.
Configuring Name Servers
Click the Edit Name Servers icon or choose Configure Name Servers from the Tools menu. Follow the instructions in Configuring Name Servers.
Configuring LAN Clients and Gateway Servers
To configure StorNext LAN clients and gateway servers, double-click the desired file system (or select it and click the Properties icon). The Properties screen appears.
Note: Do not enable gateway functionality for MDCs, connected to Lattus systems.
Use the Distributed LAN tab to enable and configure StorNext LAN clients and gateway servers for a file system. The Enable Client and Enable Server radio buttons determine whether the system is a LAN client or gateway Server. Note that separate licensing is required for LAN clients.
StorNext LAN clients provide the same functionality as StorNext SAN clients but do not need to be connected directly to the SAN. They instead send I/O via the TCP/IP network through a gateway server - a StorNext SAN client enabled as a gateway server. Metadata is sent over the TCP/IP network directly to the File System Metadata Controller (Server/MDC).
LAN Clients request the location of gateway servers via the Name Server.
Gateway Server: A gateway server has direct access to data disks (using fibre channel) and makes the shared storage pool available to distributed LAN clients over a network.
LAN Client: A StorNext LAN client does not have direct access to data disks and instead accesses the shared storage pool by connecting to a gateway server over a network. (LAN clients have full StorNext client functionality.)
Note: A StorNext SAN client configured as a gateway server requires a dedicated system. Do not run other applications or services on a system configured as a gateway server.
Use the Distributed LAN tab (Figure 16) to configure a gateway server or a LAN client. Table 6 describes the fields on the Distributed LAN tab.
Figure 16: Client Configuration: Distributed LAN
Table 6: Client Configuration: Distributed LAN
Field / Button |
Description |
Disable |
Select this option to disable the StorNext client as a StorNext LAN client or gateway server. |
Enable Client |
Select to configure the StorNext client as a LAN client. The StorNext client will connect to all available gateway servers. (If you select this check box, all other fields on the tab become unavailable.) |
Enable Server |
Select to configure the StorNext SAN client as a gateway server. The StorNext client will make the disks for this file system available to LAN clients over the specified LAN. |
Read Timeout (sec) |
Specify how long the LAN client will wait for a read operation to complete before retrying it on a different gateway server. |
Write Timeout (sec) |
Specify how long the LAN client will wait for a write operation to complete before retrying it on a different gateway server. |
Number of Transfer Buffers |
Specify the number of socket transfer buffers used for LAN client I/O. |
Transfer Buffer Size (kb) |
Specify the size in kilobytes of the socket transfer buffers used for LAN client I/O. |
TCP Window Size (kb) |
Specify the size in kilobytes of the TCP window used for LAN client I/O connections. |
Max Threads |
Specify the number of kernel threads that will be used to service LAN client I/O requests. |
Server Interfaces |
To complete gateway server configuration, select one or more network interfaces to be used for LAN client traffic. |
Configuring Logging Options
From the Client Configuration screen, select Tools Global Options. The Global Client Options window displays (Figure 17).
Figure 17: Global Client Options
Select the level of logging you want to receive and whether you want to display critical events on your desktop. Log information is available in the Windows Event Viewer.
Field / Button |
Description |
Event Log Level |
Controls how many messages are inserted into the Windows Event Viewer. Critical provides the fewest messages; Debug provides the most. Each level includes all the messages in the levels listed above it. |
Display Critical Events to Desk Top |
Enables a notification of critical events to be sent to work station’s desktop in a message box. If this is not desired, clear the check box. |
Advanced Mount Options
The Mount Options tab (Figure 18) displays the mount options for the drive currently selected on the Drive Mappings tab. Table 6 describes the fields on the Distributed LAN tab.
Caution: Changing the values on the Mount Options tab can affect system performance and stability. Do not change mount options unless instructed to do so by the Quantum Technical Assistance Center.
Figure 18: Client Configuration: Advanced Mount Options
Table 7: Client Configuration: Advanced Mount Options
Field / Button |
Description |
Mount Retransmit Limit |
Specify the number of times the driver will re-transmit a message to the FSM. After a successful connection, this value is no longer used. The default is 1. |
Hard Mount |
When this box is checked, the driver attempts to mount the file system forever. The default is off (Soft Mount). Quantum recommends that Hard Mount NOT be used on Windows systems. |
Allow Diskless Mount |
When this box is checked, the file system can be mounted and accessed without all the disks being accessible in the file system stripe groups. In this mode, file metadata can be viewed and changed, but no data can be accessed. The default is to not allow a file system to be mounted unless all disks are accessible. |
Read Only |
When this box is checked, the file system is mounted in read-only mode. The default is off or not checked. |
Restrict Pre-allocation API |
When set to yes, non-administrator users are unable to use the preallocation ioctl. |
Number of Async |
Specify the number of threads created to be used as asynchronous I/O threads for user applications. The default is 8. The allowed range is 4 to 32. |
Number of System Threads |
Specify the number of threads created for use by the file system. The default value is 16. |
Message TImeout x 1/10th Sec. |
Specify (in tenths of a second) the amount of time before a message to the FSM is timed out. The default is 50 (five seconds). |
Message Retry Count |
Specify the number of attempts to be made for sending a message to the File System Service. The default is 12. |
Retry I/Os Forever or Allow I/O Timeouts |
Choose either Retry I/Os Forever or Allow |
I/O Retry Time Seconds |
When you choose Allow I/O Timouts, this option controls the I/O retry behavior. This parameter establishes the amount of time that may elapse during an I/O retry sequence. An I/O retry sequence consists of the following: Retry an I/O request across all available paths that are currently present. Compare the current time to the Instantiation time of the I/O request, if at least <n> seconds have elapsed, return the I/O request in error, otherwise reset the paths used, and retry again. |
I/O Penalty TIme Seconds |
This option controls the Multi-Path I/O penalty value, where <n> is expressed in seconds with a minimum value of 1 and a maximum value of 15. This parameter establishes the amount of time a Path_In_Error will be bypassed in favor of an Operational Path during a Multi-Path selection sequence. If all paths are currently in the Path_In_Error state, the first available path will be selected, independent of the Path_In_Error state. The default value is 5 seconds. |
Fast Failover Detection |
When this box is checked, the client uses a more aggressive approach to detecting if the FSM has failed. With this option on, the client monitors the FSM heartbeat. If no heartbeat is detected within three (3) seconds, a failover request is initiated. This option is desirable for near realtime activities that cannot sustain more than 10 seconds of access loss to the server. Quantum does not recommend enabling this option for normal file system operations. |
Hard Reconnect |
When this box is checked, the file system attempts to reconnect to the FSM forever. If this option is not enabled, the file system attempts to reconnect to the FSM for the number of times specified at the Mount Retransmit Limit field before failing the request. The default value is off. |
Token Hold Seconds |
The QOS Token Hold Time parameter is applicable only when using the StorNext Quality of Service (QOS) feature for real-time IO. This parameter determines the number of seconds a client stripe group holds on to a non-realtime I/O token during periods of inactivity. If no I/O is performed on a stripe group within the specified number of seconds, the token is released back to the FSM. The default value is 60 seconds. The parameter should be specified in five-second increments; if the parameter is not a multiple of five, it will be rounded up automatically. |
Advanced Cache Options
The Data Buffer Cache keeps the file system data in memory on the local computer to speed up performance for small I/O operations.
The Advanced Cache Options tab (Figure 19) displays performance values that control how many file system lookup names are kept in memory.
Caution: Changing the values on the Advanced Cache Options tab can affect system performance and stability. Do not change cache parameters unless instructed to do so by the Quantum Technical Assistance Center.
Figure 19: Client Configuration: Advanced Cache Options
Table 8: Client Configuration: Advanced Cache Options
Field / Button |
Description |
Enable Data Buffer Cache |
When this box is not checked, the file system will not buffer any data. All files will be read directly into the application's memory using DMA. Requests that are not properly aligned will be read into temporary buffers, then copied to the application's buffer. If Buffer Cache is disabled, the remaining Data Buffer Cache options are ignored. |
Individual Buffer Size |
This option sets the size of each cache buffer. This determines the I/O transfer size used for the buffer cache. To determine optimal performance, try different sizes or contact your RAID vendor. This size must be divisible by the file system block size. The maximum value allowed is 512K and the minimum value allowed is the file system block size. The value default is 64K. |
Minimum Total Cache Size |
This value controls the amount of memory used to cache data from the file system. This parameter is shared by all file systems with the same block size. |
Auto-DMA Read/Write Sizes |
Buffer Cache Auto DMA Read Length and Buffer Cache Auto DMA Write Length control the minimum I/O size for DMA transfers. That is, any smaller transfer will always go through the buffer cache. The default value is 1MB. |
Number of Read-ahead Buffers |
This option controls the size of the read-ahead window used by the buffer cache. The default value is 16 buffers with a maximum of 100. Using a value of 0 disables read-ahead. |
Number of Threads |
This option controls the number of dedicated background threads used by the buffer cache for performing I/O. The default value is 8, with a minimum of 1 and a maximum of 100. Using a larger value can increase I/O concurrency in the buffer cache and therefore improve performance. |
Seconds for Shared/ Non-Shared |
The Attribute Flush Time parameters control the length of time attributes are held on the client before they are flushed back to the FSM (unless there is an explicit attribute request from the FSM). The default values are 30 seconds for non-shared files (Attribute Flush Time, non shared), and 2 seconds for shared files (Attribute Flush Time, shared). Setting these parameters lower will greatly increase the amount of metadata traffic between clients and the FSM. However, in circumstances where files are frequently shared on the SAN, setting the Attribute Flush Time Shared can result in other clients seeing size updates more frequently if a file is being written on one client and read on another. A value of zero is invalid, and will result in using the default setting. |
Delay Atime Updates |
When this box is checked, the file system delays Atime (access time) updates when reading a file to the time when the file is closed. This cuts down on FSM metadata updates at the expense of coherency. |
Low Water Mark |
Metadata Caches contain non-data information such as file names, sizes, update times, etc. Tuning the low and high water marks and the frequency of purge passes can help certain large mix applications. |
High Water Mark |
|
Max. Entries |
|
Purge Period (Seconds) |
|
Minimum Directory Cache Size |
This option sets the size of the directory cache. Directory entries are cached on the client to reduce client-FSM communications during directory reads. The default value is 10 MB. |
Starting File System Services
The Start File System Services utility starts all StorNext services on an MDC or StorNext client.
The StorNext services must be running on the MDC for file systems to be active and available. In addition, the StorNext services must be running to use the StorNext configuration utilities and to mount file systems using the client software.
To start StorNext File System services, on the Windows Start menu, click All Programs > StorNext File System > Services Start.
Stopping File System Services
The Stop File System Services utility stops all StorNext services on an MDC or StorNext client.
To stop StorNext File System services, on the Windows Start menu, click All Programs StorNext File System Services Stop.
To start the StorNext services again, reboot the system or use the Start File System Services utility. For more information, see Starting File System Services.
Stopping and Removing File System Services
The Stop and Remove File System Services utility stops all StorNext services on an MDC or StorNext client, and also removes registry entries that automatically start the services on bootup.
To stop and remove StorNext File System services, on the Windows Start menu, click All Programs > StorNext File System > Services Stop and Remove.
To start the StorNext services again, you must use the Start File System Services utility. Rebooting the system will not restart services. For more information, see Starting File System Services.
Obtaining Version Information
The Version Information utility displays information about the currently installed version of the StorNext server and/or client software, such as the version number, build number, and platform.
To run the Version Information utility, on the Windows Start menu, click All Programs > StorNext File System > Version Information. A dialog box displays version information for the StorNext server and/or client software installed on your system.
Configuring the File System Startup List
The File System Startup List utility lets you modify the File System Manager (FSM) services list and set file system priority.
The File System Manager is a process that manages the name space, allocations, and metadata coherency for a file system. Each file system uses its own FSM process. When there are multiple file systems (and therefore multiple FSM processes), the FSM services list controls which FSM processes are run when the server starts up, and also sets the priority for each file system (for failover configurations).
To run the File System Startup List utility, on the Windows Start menu, click All Programs > StorNext File System > File System Startup List. The File System Startup Editor opens (Figure 20).
Select a file system do any of the following. When finished making changes, select File > Save to save your changes.
Action |
Description |
Action Toggle Startup Type |
Allows you to choose if the file system will start up automatically upon server startup. This action toggles the startup type between automatic and manual. |
Action Priority |
(Optional) Select the priority for the selected file system. This priority is used for failover configurations. 0 is highest priority and 9 is lowest priority. |
Figure 20: File System Startup List
Re-initializing a File System
The Re-initialize a File System utility allows you to initialize an existing file system. Initializing a file system prepares it for use.
Caution: Use extreme caution when using this tool. This will destroy all data on the selected file system.
To initialize a file system, on the Windows Start menu, click All Programs > StorNext File System > Re-initialize a File System. Type the number that corresponds to the file system you want to re-initialize, and then press <Enter>.
Checking a File System (Read-Only)
The File System Check (Read-Only) utility allows you to check a StorNext file system for metadata corruption (due to a system crash, bad disk, or other failure). Run the utility on an MDC that contains the file system you want to check.
To check a file system, on the Windows Start menu, click All Programs > StorNext File System > File System Check (Read-Only). Type the number that corresponds to the file system you want to check, and then press <Enter>.
Because the file system check is run in read-only mode, any problems that exist are not repaired. If the utility identifies errors or corruption in metadata, you must repair the file system (see Repairing a File System).
Repairing a File System
The File System Check (Repair) utility lets you repair corrupted metadata on a file system. Repair a file system if errors were identified when checking the file system (see Checking a File System (Read-Only)).
The file system must be inactive in order to be repaired. To stop a file system, see Stopping File System Services.
To repair a file system, on the Windows Start menu, click All Programs > StorNext File System > File System Check (Repair). Type the number that corresponds to the file system you want to repair, and then press <Enter>.
Note: Multiple repair passes may be needed to fully fix a damaged file system. Run the repair utility repeatedly until no problems are reported by the utility.
Server Administration
The Server Administration utility lets you view and modify stripe group properties and set quotas. A stripe group is a logical storage unit made up of one or more disks. A quota is a space limit that is set for specified users or groups.
To run the Server Administration utility, on the Windows Start menu, click All Programs > StorNext File System > Server Administration. The StorNext Administration window appears.
Figure 21: The StorNext Administration window
In the StorNext Administration window, you may perform one of the following procedures:
Update the List of File Systems
Connect to an MDC
1. | Click Connections, and then click Actions > New. |
2. | Type the host name and click OK. Disks and File Systems are displayed in the left pane. |
Start a File System
1. | Right-click File Systems, and then click Start. |
2. | Enter file system information. For additional details, see To Start a File System. |
Activate a File System
1. | Click File Systems in the left pane. |
2. | Right-click the name of the file system under File Systems, and then click Activate. |
Stop a File System
1. | Click File Systems in the left pane. |
2. | Right-click the name of the file system under File Systems, and then click Stop. |
Update the List of File Systems
Press Ctrl+R, or click View, and then click Refresh.
Create a Connection
You can create a connection to any StorNext client or server.
1. | To create a new connection, click Actions, and then click New. The New Connection dialog box appears. |
Figure 22: The New Connection dialog
2. | In the New Connection dialog, enter the host name or IP address of the computer to add, and then click OK. The new connection information appears (refer to Figure 23). The left pane displays file systems running on the connected MDC. |
Note: Expand a file system to see stripe groups, quotas, and additional file system properties.
Figure 23: New connection information
Close Connection
You can close a connection to any StorNext client or server.
To close an existing connection, right-click the connection, and then click Close (refer to Figure 24.)
Figure 24: Closing an existing connection
Save Connections
You can save the current connections. The next time you open the StorNext Administration utility, the utility will query the saved list to automatically open connections. To save the list, perform the following:
Click Connections (in the left pane.), click Actions on the menu, and then click Save.
File System Tools
The StorNext Administration’s File System Control Dialog
The StorNext Administration's File System Control dialog is used to Start, Stop, Failover and Activate a StorNext file systems. The actions in the File System Control dialog perform actions equivalent to the cvadmin
commands.
Note: To prevent long delays, the StorNext Administration tool does not automatically refresh. After issuing commands from the File System Control dialog, you may need to issue a Refresh before the changes will appear.
To Start a File System
To start a file system, perform the following procedure:
1. | Right-click File Systems, and then click Start. The File System Control dialog displayed (refer to Figure 25). |
2. | Enter the file system name and the IP address of the MDC. |
The File System Name is the name of a file system configuration file without the .cfg/.cfgx file extension.
The Meta-data Controller (MDC) Host or IP is the hostname or IP address of the MDC managing the specified file system.
If Start a Single File System Manager is checked, this will start a single FSM on the specified host. If it is unchecked, it will start FSMs on both HA (High Availability) MDCs if they are an HA pair. Optionally, you may have the dialog wait for the file system to start before returning. Otherwise the request will be issued and return immediately.
Figure 25: The File System Control dialog
Once the file system is started, the file system status is displayed (refer to Figure 26).
The yellow dot indicates the file system is in the standby state.
A green arrow indicates the file system is in the active state.
Figure 26: The File System Status indicator
To Activate a File System
Once the file system is started, perform the following procedure to activate the file system:
1. | Right-click the file system, and then click Activate (refer to Figure 27). The File System Control dialog is displayed (refer to Figure 28) with Initiate Activation Vote checked. |
Initiate Activation Vote will cause a client "vote" to commence and may cause a file system to activate. If an FSM is already active, no action is taken.
2. | Click OK to activate. |
Figure 27: Activating a file system
Figure 28: Initiating Activation Vote
If the file system activates successfully, the File System Control status is updated to display the following (refer to Figure 29).
Figure 29: Active file system display
Other radio buttons in the File System Control specify the following parameters:
Stopping the File System
The Stop File System radio button is used to stop a single FSM or to stop both FSMs, if they are HA pairs. As with the Start File System option, you can have the dialog wait for the command to complete before return control back to you.
Fail-over
This option can be used on a HA MDC. This radio button will cause the file system to fail-over from the active FSM to the standby FSM (regardless of which MDC host is specified.)
File System Displays
Select a file system to display clients, debug options, quality of service, quotas and stripe groups (refer to Figure 30).
Table 9 provides the description of the various fields in the File System Properties display.
Figure 30: File System Properties display
Table 9: Description of fields in the File System display
Name |
Value |
Type |
Clients |
Expandable list of connects to the file system (clients with file system mounts and control connections) and the client properties. |
|
Debug |
None |
Click to expand to a clickable list of debug flags. |
Quality Of Service |
None |
Click to display QOS properties (if QOS is enabled on file system.) |
Quotas |
None |
Click to display Quotas properties (if Quotas are enabled on file system.) |
Stripe Groups |
None |
Expandable list of stripe groups and stripe group properties. |
Host |
IP address of the MDC running the file system. |
|
Percent Free |
Percentage of free space on the file system. |
|
Size |
Size of the file system |
|
State |
Current state of the file system. |
|
Clients Information
To view information about clients connected to the file system, expand a file system in the left pane, and then click Clients. Information about the clients currently connected appears in the right pane (refer to Figure 31).
Figure 31: The File System Clients display
Click on a specific client to see the client’s properties (refer to Figure 32).
Figure 32: The Single Client display
Selecting a specific Client will provide the following information:
Table 10: Description of fields in the Client display
Name |
Value |
Build |
StorNext version |
DLAN Client |
Is it a Distributed LAN Client? |
DLAN Server |
Is it a Distributed LAN Gateway? |
Expires |
When the license expires |
Gateway License |
Distributed LAN Gateway license installed |
Hashed ID |
SNFS Identifier hash value |
ID |
ID or IP address |
IO Test Last |
Last IO Test result |
IO Test Rate |
IO Test rate |
IP Address |
Address of connection |
Local Address |
Alternate local address |
Nbr CPUs |
CPU count on Client |
Ordinal |
FSM Connection number |
Reconnect Cnt |
Number of reconnections |
Type |
Type of connection |
Uptime |
Connection time |
Debugging Information
Click the Debug icon to display the current active debug flags used by the File System Manager (FSM) process (refer to Figure 33). If any of the debug flags are turned on, the debug output is printed to the file:
<StorNext Install Directory>/data/<file system name>/log/cvlog.txt
Caution: Turning on debug flags can severely impact file system performance!
Do not turn on debugging flags unless recommended by Quantum.
Quality of Service Information
The Quality of Service (QOS) pane displays the settings and current metrics (refer to Figure 34). Quality of Service must be enabled on the file system for it to be active. See Quality of Service Feature for additional details.
Figure 34: The Quality of Service display
Quota Properties
Quotas define the amount of storage space a specified user or group is allowed to own. You can set hard or soft quota limits. Quotas must be enabled in the File System Configuration file to be able to set and change quotas.
To view quota properties, expand a file system in the left pane, expand Quotas and then click Directories or Users & Groups.
To change quotas, right click on Directories or Users & Groups.
The User/Group Quota dialog box appears (refer to Figure 35 and Figure 36).
There are three types of quotas you can configure:
Set quotas for users on the User Quotas button.
Set quotas for groups on the Group Quotas button.
Set data or file quotas for directories under the Directory Quotas heading.
Figure 35: The User/Group Quota dialog box
Table 11: Description of fields in User/Group Quota Dialog box
Field / Button |
Description |
User or Group Quota |
Type the name of the user or group for which you want to set a quota. |
Directory Quotas |
|
Set a data size limit on the directory |
|
Set a limit on the number of files under a directory. |
|
Data Limit |
Set the amount of data or number of files (depending on the quota type.) Specify an amount in bytes or with the extensions M (megabytes), G (gigabytes) or T (terabytes). |
This is the maximum amount of space the specified user or group can use. |
|
Once the user or group exceeds this limit, a warning is sent. (Typically, this is set at 80% of the hard limit.) |
|
Time Limit |
Specify the amount of time it takes for the soft limit to turn into a hard limit. |
Figure 36: The Directory Quotas display
Table 12: The description of fields in the Quotas display
Field / Button |
Description |
Name |
The Linux user or group name |
Type |
The type of quota (User or Group) |
Limit Hard |
The absolute maximum amount of data the user or group can consume |
Limit Soft |
The maximum amount of data the user or group can consume. They can exceed this limit for Grace Period amount of time, but cannot exceed the Hard Limit. |
Used |
The amount of data currently consumed. |
Grace Period |
The amount of time the user or group is allowed to exceed the Soft Limit |
Time Remaining |
Amount of time remaining before the user or group cannot allocate any more space in the file system. If the value is negative, the user can no longer allocate any more space. |
Stripe Group Properties
To view stripe group properties, expand a file system in the left pane, click Stripe Groups, and then click the stripe group name in the left pane. The stripe group’s property appears in the right pane (refer to Figure 37). Table 4 describes the fields of the stripe group property display.
Figure 37: The Stripe Group Properties
Table 13: The description of fields in the Stripe Group display
Name |
Value |
Affinity Cnt |
Number of affinities |
Blocks: Free |
Number of blocks free |
Blocks: Reserved |
Number of blocks reserved |
Blocks: Total |
Total number of blocks |
Stripe Breadth |
The number of file system blocks to write before switching to the next disk in the stripe group. |
Stripe Depth |
The number of disks in the stripe group. |
Device Flags |
Read and Write flags |
Exclusive |
Indicates if only specified file types (associated with the stripe group affinities) can be stored on the stripe group. |
Index |
Disk index in configuration |
Journal |
Indicates if the file system logging journal can be stored on the stripe group. |
Metadata |
Indicates if file system metadata can be stored on the stripe group. |
Multi-path |
Indicates the method the file system uses to access the disk: round, static, or sticky. |
Name |
Stripe group name |
Nbr of Disks |
Number of disks in group |
Ordinal |
Internal index |
Realtime |
Uses Real-time IO |
Status |
Current status |
Disk Properties
Click Disks to see all disks visible to the currently selected host. Click a specific disk to display the various attributes of that disk (refer to Figure 38 and Table 14).
Figure 38: The Disks Property display
Table 14: Description of fields in the Disks Property display
Name |
Value |
Controller |
Device driver |
Device (Block) |
The block device |
Device (Raw) |
The Raw Device |
HBA ID |
Host Bus Adapter identifier |
Inquiry |
Manufacturer string |
LUN ID |
Logical Unit Number |
Name |
Disk Label |
Serial Nbr |
Disk's Serial Number |
Size |
Size of the disk |
State |
State of the disk |