Manually Modify the Storage Manager Configuration
StorNext employs global parameters that define the Storage Manager configuration. Although the default values in these files are sufficient for most installations, you can edit the files to customize the StorNext software for your specific installation. This section provides a procedure that can be used to modify the following StorNext configuration files:
/usr/adic/TSM/config/fs_sysparm_override
/usr/adic/TSM/config/filesize.config
/usr/adic/TSM/logs/log_params
The fs_sysparm_override configuration file is used to tune items related to system administration, drives and media, media manager interface, and other miscellaneous items. For more information about the parameters that can be placed into the fs_sysparm_override configuration file, refer to the fs_sysparm.README file.
Caution: Incorrect modification of the fs_sysparm_override configuration file can cause a serious, adverse effect on StorNext functionality. Before modifying this file, Quantum recommends that you contact Quantum Global Services.
Caution: If you have files larger than 100GB and are using LTO2 media, the MED_SEG_OVER_LTO parameter may be modified to a value less than or equal to 190G to reduce file fragmentation. This has the adverse effect of reducing the potential for parallel I/O for multiple file segments. Setting the MED_SEG_OVER_LTO parameter to a value larger than 190GB may result in allocation failures that prevent file movement to tape.
The filesize.config configuration file is used to control the file steering feature and has these characteristics:
- Allows the placement of files on different media types, based on the size of the files
- Specifies which drive pool a policy class should use when storing data
- Contains specific syntax and usage information
- Enables the system administrator to make changes without recycling the Tertiary Manager software
- Read the instructions in the
filesize.config.default
file for usage and syntax information.
The log_params configuration file is used to control various levels of trace logging. The file specifies each log level and how to enable and/or disable it.
Note: The default logging configuration saves data for approximately one month, depending on activity levels. Quantum recommends that you keep your log data for a minimum of two years. See Log Rolling to configure the log rolling cron job to back up rolled log files.
Use the following procedure to modify the fs_sysparm_override, filesize.config, or log_params configuration files.
-
Use a text editor to open one of the following configuration files:
- /usr/adic/TSM/config/fs_sysparm_override
- /usr/adic/TSM/config/filesize.config
- /usr/adic/TSM/logs/log_params
- Locate the parameter you want to modify and replace the setting with a new, valid value. When editing a file, be sure to follow the format used by entries in the file. For example, in the fs_sysparm_override, or log_params files, all entries must be in the format: name=value;
- Restart the Tertiary Manager software.
- Stop the software by typing TSM_control stop.
- Restart the software by typing TSM_control start.