Tools > Storage Manager > System Parameters
The Tools > Storage Manager > System Parameters page allows you to set and modify a subset of StorNext system parameters for Object Storage.
Note: Below is an example of the information contained in the fs_sysparm.README file. To view the latest and up-to-date information, see the fs_sysparm.README file under the installation directory /usr/adic/TSM/config/.
Example Only of the Information Contained in the fs_sysparm.REAME File
############################################################################
#
# Copyright 1991-2020. Quantum Corporation. All Rights Reserved.
# StorNext is either a trademark or registered trademark of
# Quantum Corporation in the US and/or other countries.
#
############################################################################
# This is the System Parameters file. These parameters are set #
# up as environment variables upon initialization of the software. #
# The parameters in this file are set to appropriate values for the #
# normal operation of a TSM, but can be adjusted as necessary. #
# #
# To change a default, modify the fs_sysparm_override file by adding the #
# parameter to be changed along with its new value, cycle the software #
# and retry the command. #
# #
# The parameter should be added as a separate line to the file in the #
# form of: #
# PARAMETER=value; #
# Each line must be terminated with a semicolon. #
# #
# To enable the parameter change, restart TSM with the following #
# command: #
# # adic_control restart TSM #
# #
# Note: These options are not intended for general use. Only use when #
# recommended by Quantum Support. #
# #
# #
# The fs_sysparm file is grouped into the following categories: #
# 1) System Administration #
# 2) Drive/Media #
# 3) FS Defaults #
# 4) File retention #
# 5) Media Manager #
# 6) Installation #
# 7) Software Maintenance #
# Each category is described further in its respective section. #
# #
# The location of the files used by the software is controlled #
# by the value of the environment variable FS_HOME. This variable must #
# be defined in the environment prior to starting the software or #
# using any of the Tertiary Manager commands. #
# The locations of the various types of files used by the software #
# are derived as follows: #
# #
# 1) LOG FILES -> $FS_HOME/logs - the directory where all of #
# the log message are sent #
# Refer to the log_params #
# file in the directory for #
# more info. #
# 2) INTERNAL FILES -> $FS_HOME/internal - the directory where all #
# TSM internal files and #
# directories are kept. #
# 3) CONFIG FILES -> $FS_HOME/config - the directory where all #
# system parm files are kept.#
# 4) REPORTS DIR -> $FS_HOME/reports - the directory where report #
# formats, label formats, #
# and transmittal letters #
# are located. #
# #
# A "#" symbol in the first column denotes a comment. Each parameter #
# is grouped with related parameters and is first described in comment #
# form. The actual parameter follows, in the form: <name>=<value>; #
# Blanks are NOT permitted within the parameter string and each value must #
# be terminated with a semicolon (;). #
############################################################################
# CHANGE HISTORY #
# #
# $LOG$ #
# #
# $Id: fs_sysparm 9.10 2007/02/23 11:13:00MST Doug Burling (dburling) dev #
# #
############################################################################
############################################################################
# SYSTEM ADMINISTRATION PARAMETERS: #
# #
# These parameters can be changed to tune system performance and tape #
# utilization. Refer to operational documentation for details. #
############################################################################
# FS_STARTUP_TIMEOUT : Time (in seconds) allowed for each TSM #
# daemon to start up or shut down. #
# FS_MAX_ACTIVE_FORMATS : Maximum number drives allowed to perform #
# tape formatting at any one time. #
# FS_MAX_ACTIVE_TAPECOPIES : Maximum number of media copy operations #
# allowed to mount media at one time. Each #
# operation allowed utilizes 2 drives. This #
# parameter also applies to file copies and #
# fsdefrag operations. #
# CONNECT_SLEEP_TIME : Time to wait (in seconds) before the next #
# retry if IPC connect request fails. #
# CONNECT_RETRIES : # retries on IPC connection failure. #
# MAX_READS : # retries on IPC receive failure. #
# MAX_WRITES : # retries on IPC send failure. #
# FSEVENTD_MIN_THREADS : The number of worker threads fs_eventd #
# creates at startup to service file system #
# events. #
# REQUESTD_NUM_REQUEST_THREADS #
# : Number of threads fs_requestd creates #
# at startup to service file store and #
# retrieve requests. #
# REQUESTD_NUM_STORE_RESPONSE_THREADS #
# : Number of threads fs_requestd creates #
# at startup to service responses for file #
# stores. #
# REQUESTD_NUM_RETRIEVE_RESPONSE_THREADS #
# : Number of threads fs_requestd creates #
# at startup to service responses for file #
# retrieves. #
# QUOTA_DAEMON_NOTIFY_STATUS_INTERVAL #
# : Number of seconds that must pass before a #
# QuotaStatus is reported on again. #
# Default=86400 (one day) #
# QUOTA_DAEMON_NOTIFY_STATUS_THRESHOLD #
# : Specifies the minimum quota status for the#
# quota daemon to use when creating interim #
# quota report email attachments. #
# Valid values: good, grace, exceed, none, #
# soft, hard, where soft is an alias for #
# grace, and hard is an alias for exceed. #
# The value 'none' disables the generation #
# of the report files. #
# Default=exceed #
# QUOTA_FEATURE_NOTIFY_STATUS_THRESHOLD #
# : Specifies the minimum quota status for the#
# quota feature to use when creating its #
# quota report email attachments. #
# Valid values: good, grace, exceed, none, #
# soft, hard, where soft is an alias for #
# grace, and hard is an alias for exceed. #
# The value 'none' disables the generation #
# of the report files. #
# Default=grace #
# QUOTA_FEATURE_FILE_STATUS_THRESHOLD #
# : Specifies the minimum quota status for the#
# quota_report feature to use when creating #
# its quota report files. #
# Valid values: good, grace, exceed, none, #
# soft, hard, where soft is an alias for #
# grace, and hard is an alias for exceed. #
# The value 'none' disables the generation #
# of the report files. #
# Default=good #
# QUOTA_UPDATE_QRY_REC_LIMIT #
# : For efficiency reasons, when queries are #
# done that can potentially return large #
# numbers of rows, the queries are done a #
# 'chunk' at a time. This keeps result sets #
# at a manageable size. This parameter is #
# used to control the size of the chunks #
# that are returned. #
# See FS_DB_LARGE_QRY_REC_LIMIT for more #
# details. #
# Default=FS_DB_LARGE_QRY_REC_LIMIT #
# QUOTA_UPDATE_DB_GROUP_COUNT #
# : Number of row inserts/updates on the #
# FilecompQuota table for the quotad #
# daemon's QuotaUpdateThread to perform #
# before committing a transaction. #
# Default=30 #
# QUOTA_HISTORY_DAYS_KEEP : The number of days of quota_history #
# report sub-directories to keep. Each time #
# a quota_report feature runs successfully, #
# it removes older directories with the #
# matching date-range format <YYYY-MM-DD>. #
# The default value is 7. #
# QUOTA_STATUS_CACHE_INTERVAL #
# : Number of seconds before an item is #
# expired from the QuotaStatus cache. #
# Default=30 #
# QUOTA_STATUS_CACHE_SIZE : Number of entries allowed in the #
# QuotaStatus cache. #
# Default=3000 #
# PROJECTDIR_CACHE_INTERVAL : Number of seconds before an item is #
# expired from the Projectdir cache. #
# Default=30 #
# PROJECTDIR_CACHE_SIZE : Number of entries allowed in the #
# Projectdir cache. #
# Default=30000 #
# USAGE_TRACKING : Enables the usage tracking and quota #
# features. If disabled, quota violations #
# are not enforced. #
# This setting is disabled by default. #
# Valid values are true or false. #
# MAX_RETRIEVE_RETRY_COUNT : Maximum file copy number to retry for any #
# failed retrieve operation. If only one #
# copy of a file is stored, then this has no#
# impact. Otherwise, if the retrieve of the#
# primary copy fails, a retrieve for each #
# copy up to the number specified by this #
# will be attempted until one is successful.#
# DRIVE_RETRIES : The number of attempts to retry a retrieve#
# failure for a given copy of a file when a #
# read error is encountered. The media is #
# dismounted prior to the retry, so a new #
# drive may or may not be obtained in the #
# retry attempt #
# MEDIA_RETRIES : The number of attempts to retry a store #
# operation when a write error is #
# encountered. A new media is used for each #
# attempt. #
# MIN_STARVE_TIME : This is the minimum time (in minutes) #
# that resource requests will wait before #
# forcing ejects of media that are in #
# the delayed dismount state. #
# FS_NICE_VALUE : If enabled, resident #
# processes will run with this "nice" #
# value. See setpriority(2) for the value #
# range on your operating system. #
# To disable, specify <n> as the value. #
# To enable, specify the "nice" value. #
# and processes will run with the #
# operating system default priority. #
# LIC_CAPACITY_LVL1 : This the percent of the snsm_capacity #
# license storage capacity at which the #
# first warning is sent. The warning is #
# only sent once. If the used capacity #
# falls below this level and then excedes #
# it again, then the warning will be sent #
# again. Valid values are 0-99.0 percent #
# LIC_CAPACITY_LVL2 : This the percent of the snsm_capacity #
# license storage capacity at which the #
# second warning is sent. Notifications #
# work just like LIC_CAPACITY_LVL1. #
# This value must be greater than the first #
# warning level. #
# Valid values are 1.0-100.0 percent #
# FS_THRESHOLD_INC_NUM : Amount to increment each time a drive #
# device is used with errors encountered. #
# FS_THRESHOLD_DEC_NUM : Amount to decrement each time a drive #
# device is used without errors. #
# FS_DRIVE_ERR_THRESHOLD : Threshold value, which when equaled or #
# surpassed, drives will be taken offline. #
# PERCENT_FULL_TO_MIGRATE : Percentage value used to check against to #
# determine if a medium is full enough to #
# be migrated. #
# MEDIA_SUSPECT_THRESHOLD : This indicates the suspect count value at #
# which a media will no longer be used for #
# writing. The suspect count is typically #
# incremented for I/O errors. #
# SUSPECT_MEDIA_FILELIST_FILE: #
# The name of the report file for the #
# checkMediaAnomalies Health Check. When #
# this value is the empty string, output is #
# sent to stdout. Output is produced only #
# when there are media that meet "error" or #
# "suspect" criteria. #
# The default is: #
# /usr/adic/TSM/reports/MediaAnomalies #
# SUSPECT_MEDIA_FILELIST_FILE_APPEND: #
# Each run of the checkMediaAnomalies #
# health check overwrites the output file #
# unless this parameter is "true", in which #
# case the results are appended to the file.#
# The default is "false". #
# SUSPECT_MEDIA_FILELIST_INACTIVE: #
# Set to true to include inactive file #
# copies in the output of the #
# checkMediaAnomalies Health Check. #
# The default is "false". #
# SUSPECT_MEDIA_FILELIST_RAS: This indicates that a RAS message is to #
# be sent when the checkMediaAnomalies #
# Health Check produces a report file. #
# The default is "true". #
# MAX_MOVERS_PER_RELOCATION_REQUEST: #
# Maximum number of mover threads that #
# will be used for disk-to-disk operations. #
# The default is 8. #
# SNMS_BACKGROUND_FOREIGN_MOVERS : #
# Maximum number of background mover #
# processes that will be used to import the #
# data from the foreign server. #
# In general, it should not be set to more #
# than the number of foreign tape drives #
# available for the migration, unless most #
# of the foreign data is on disk. #
# FS_FIRST_POLICY_AT_LOSPACE: The first policy to be executed when a #
# low-space situation is encountered in a #
# file system. The default is to run a #
# relocation policy first. #
# VALID VALUES: {relocation, truncation} #
# FS_FIRST_POLICY_AT_NOSPACE: The first policy to be executed when a #
# no-space situation is encountered in a #
# file system. The default is to run a #
# truncation policy first. #
# VALID VALUES: {relocation, truncation} #
# CPYRESP_MAXVER_QRY_SECS: The class parameters are periodically #
# checked to see how many versions to keep #
# for files. If a file is stored, and if #
# the class parms have not been checked in #
# the indicated time, they will be #
# re-checked. #
# TSM_IGNORE_TOUCHES: The software now has a "safety check" in #
# place when removing disk blocks for a file#
# that has been stored to tape. If the mod- #
# time in the db does not match that on disk#
# then the operation will be aborted and #
# the file will be marked for re-storing. #
# The unix 'touch' command will update a #
# file mod time without actually changing #
# the data. If a file has been 'touch'ed, #
# that file will be marked for re-storing #
# unnecessarily. In general this should not #
# be a big issue, and the extra safety #
# provided should out weigh the cost of #
# re-storing. If however, in your env a lot #
# of 'touch'es are done operationally, time #
# and tape space can be wasted on these #
# stores. You should set this variable then #
# the modtime "safety check" will be #
# by-passed. #
# OPTIMIZE_RETRIEVE_QUEUE: This parameter is used to select the #
# algorithm to use for inserting retrieve #
# requests into the request queue. #
# true - Insertion based on media index #
# and media position for requests #
# at the same priority. Does not #
# optimize requests that are at #
# maximum priority. #
# false - Insertion based on legacy FIFO #
# order method. #
# BACKUPFS: This is the file system mount point to be #
# used for staging of SNMS backup files #
# BACKUP_GZIP_OPTIONS: This defines the options that will be #
# used by gzip during snbackup #
# BACKUP_GZIP_PATH: This directory is prepended to the PATH #
# in snbackup and is used to indicate where #
# "gzip" is located. #
# FS_BLOCKING_READS: If a non-zero value is present, #
# retrieves of files which would otherwise #
# fail due to lack of disk space will be #
# retried. Retries will be done #
# every 5 minutes until the value in this #
# setting is exceeded. #
# Values entered for this setting are #
# in minutes. #
# A value of 0 will result in no retries. #
# FS_GENERATE_CHECKSUMS: If set to 'y' or 'n', checksum generation #
# is enabled (y) or disabled (n) for all #
# stored files respectively. If set to 'p' #
# (the default), checksum generation is #
# enabled or disabled on a policy-class #
# basis; that is, based on the state of the #
# checksum generation setting in the policy #
# class a stored file belongs to. #
# FS_VALIDATE_CHECKSUMS: If set to 'y' or 'n', checksum validation #
# is enabled (y) or disabled (n) for all #
# retrieved files respectively. If set to #
# 'p' (the default), checksum validation is #
# enabled or disabled on a policy-class #
# basis; that is, based on the state of the #
# checksum validation setting in the policy #
# class a retrieved file belongs to. #
# CLEAN_VERSIONS_EXPIRATION: Used in conjunction with the scheduled #
# clean version task. This feature is used #
# for cleaning old inactive versions of #
# files. When a file is modified or removed,#
# information about that file is kept in #
# the TSM database until cleaned. The clean #
# can be done manually via the fsclean #
# command. If versions are never cleaned #
# manually they will eventually be cleaned #
# by the scheduled clean version task. #
# By default this will clean inactive #
# versions older than 7 years old. This #
# value can be changed by updating this #
# parameter. The parameter is an integer #
# value followed by an optional period #
# indicator. Valid period indicators are: #
# d - days, w - weeks, m - months, y - years#
# Some valid values: #
# 0 - nothing is automatically cleaned #
# 90d - clean older than 90 days #
# 7m - clean older than 7 months #
# 3y - clean older than 3 years #
# 1 - clean older than 1 year (the period #
# defaults to years if not specified) #
# NOTE: Active versions are never #
# automatically cleaned even if they have #
# been unaccessed during the #
# CLEAN_VERSIONS_EXPIRATION time period. #
# FS_DB_LARGE_QRY_REC_LIMIT: For efficiency reasons, when queries are #
# done that can potentially return large #
# numbers of rows, the queries are done a #
# 'chunk' at a time. This keeps result sets #
# at a manageable size. This parameter is #
# used to control the size of the chunks #
# that are returned. #
# NOTE that setting the size too small will #
# result in more queries and hence can hurt #
# the performance of the querying command. #
# Setting the value too large will result #
# in more resource usage for the process #
# and can result in degradation for the #
# system as a whole. The default should #
# not be changed unless directed by #
# support. #
# FS_DB_LARGE_CLN_REC_LIMIT: As with the "large qry rec limit" above #
# this parameter sets the database "chunk" #
# size. (See above description for more on #
# "chunk" management.) In addition to the #
# query size this parameter also affects #
# the number of entries put into the #
# recovery files used to clean up non-tape #
# media. These recovery files contain info #
# about the user files previously stored to #
# that media. This info is needed to do #
# the cleanup of that media. #
# FS_DB_BATCH_INSERT_LIMIT: For efficiency reasons, when inserts are #
# done by batch, this parameter controls #
# how many rows should be inserted at once. #
# The default is 10000. #
# This sysparm currently used only by #
# fsrmversions. #
# POLICYD_NUM_OBJ_DELETE_THREADS: #
# The maximum number of threads used by the #
# fs_policyd process to delete objects from #
# object storage. Each thread will process #
# one recovery file which contains up to #
# FS_DB_LARGE_CLN_REC_LIMIT number of #
# objects. This parameter can be used to #
# adjust the number of concurrent requests #
# issued to the object storage appliance. #
# When adjusting this value, the maximum #
# number of streams configured for the #
# appliance via fsobjcfg should be taken #
# into consideration. The number of streams#
# plus the number of delete threads is the #
# total number requests that could be issued#
# to the appliance at any given point in #
# time, so the appliance client daemons #
# should be configured to handle this many #
# requests. #
# A large number of delete threads could #
# also impact routine store/retrieve #
# processing. When setting this value the #
# frequency of the clean versions task #
# should be taken into account. fsschedule #
# can be used to determine the frequency. #
# POLICYD_NUM_FSYS_CONV_THREADS: #
# The number of threads active within the #
# fs_policyd process that are performing #
# file system upgrade processing. Each #
# thread operates on one file system. #
# FILE SYSTEM UPGRADE (conversion): #
# This is the processing that converts old #
# style managed file systems to the lastest.#
# (The processing that is done on a file #
# system is a per file process and can #
# take some time to complete.) #
# Each of the threads perform some #
# intensive file system and database #
# processing. Caution should be used when #
# considering increasing the number of #
# threads (file system conversions) that #
# are going to be active a once. #
# POLICYD_FSYS_CONV_BATCH_SIZE: #
# The number of files to convert at a time #
# when doing a file system upgrade in the #
# fs_policyd process. #
# POLICYD_FSYS_CONV_BATCH_LOOPS: #
# The number of loops to take in a #
# conversion thread before stopping. #
# A batch of files is processed per loop #
# so this could also be thought of as the #
# number of batches of files to process #
# per conversion thread. #
# #
# MAX_STORE_POLICIES: The maximum number of class based non- #
# emergency store policies that can be run #
# at the same time. If this variable is #
# not set, the default result is a max of #
# two times the number of managed file #
# systems. Do not set this value too high, #
# as that might result in performance #
# degradation. The recommended maximum is #
# two times the number of drives in the #
# system. #
# MAX_STORE_SIZE: If this parameter is non-zero then any #
# files that are larger than this size will #
# not be stored by fspolicy. (Note that #
# these files can still be stored explicitly#
# via the fsstore command.) If the value is #
# zero then there is no limitation. #
# When an attempt to store a file which #
# is larger than this value is made, an #
# admin notification is sent and the file #
# is removed as storage candidate. #
# This parameter can be used as a #
# preventative measure to skip large files #
# that are never intended to be stored, #
# since storing extremely large files will #
# consume many resources and could impact #
# overall performance as well. #
# When specifiying this value provide an #
# integer number and a byte suffix. For #
# example: 200GB or 12TiB #
# Valid byte suffixes: #
# - B: Value in bytes #
# - KB or KiB: Value in kilobytes (10^3) #
# or kibibytes (2^10) #
# - MB or MiB: Value in megabytes (10^6) #
# or mebibytes (2^20) #
# - GB or GiB: Value (10^9) or (2^30) #
# - TB or TiB: Value (10^12) or (2^40) #
# - PB or PiB: Value (10^15) or (2^50) #
# For historical reasons an integer value #
# with no suffix is treated as GB. #
# MAX_SEGMENTS_PER_FILE: If this parameter is non-zero then it #
# represents the maximum number of segments #
# that is allowed for an individual file #
# copy. If a copy of a file exceeds this #
# segment limit, that copy will not be #
# stored. If a file's copies cannot be #
# stored then the file will be removed as #
# a store candidate. #
# If a file cannot be stored due to this #
# segment limit there are two options for #
# getting the file stored: #
# - Adjust MED_SEG_OVER_XXX (for the proper #
# media type) to a larger value so there #
# will be fewer segments generated. #
# (This is the preferred option.) #
# - Adjust MAX_SEGMENTS_PER_FILE to a #
# larger value. #
# After making the sysparm changes, the #
# file will have to be stored manually or #
# wait until the next rebuild again adds #
# the file as a store candidate. #
# FS_DIRECT_STAGE_ENABLE_SIZE: #
# Use a staging file for direct I/O if the #
# request size exceeds the specified size. #
# Value is in bytes. #
# FS_DIRECT_STAGE_DISK: Size of each disk file to use for staging #
# data if it has been enabled. Value is #
# in bytes. #
# MAX_FILES_PER_CLUSTER: The maximum number of files that can be #
# specified per data movement request for #
# tape devices. The default value is 3000. #
# MAX_FILES_PER_CLUSTER_NON_TAPE:
# The maximum number of files that can be #
# specified per data movement request for #
# non-tape devices. #
# The default value is 300. #
# MICRO_RENAME: THIS VALUE IS NOW OBSOLETE. In its place, #
# the 'renameTracking' FS parameter is now #
# recognized in FS configuration files. #
# If set/true, when a file is modified #
# in place (open/write/close) the fsversion #
# command is used for tracking versions of #
# files. Some applications, for example #
# MicroSoft Exel, modify files by renaming #
# existing to a temp name, copying to the #
# new file and removing the temp file when #
# done. For these apps fsversion is of #
# limited use because all files just have #
# one version and the names at remove time #
# are the temp names. If this is the primary#
# type of file updates that are done on the #
# system use this sysparm to adjust rename #
# processing. When a file is renamed it #
# creates and instance of that file with #
# the original name. Instances of a file #
# with a given name can be tracked via the #
# fsrecover command. #
# DAILY_RELOC_START_TIME: This value specifies the starting time #
# for the class-based daily relocation #
# policies run by the fs_tierman process. #
# The value is a time, formatted as HHMM #
# (using a 24-hour clock). #
# For example: #
# 0300 this is 3:00am #
# 1500 this is 3:00pm #
# The default value is 0000 (or midnight). #
# DAILY_TRUNC_START_TIME: This value specifies the starting time #
# for the class-based daily truncation #
# policies run by the fs_tierman process. #
# The value is a time, formatted as HHMM #
# (using a 24-hour clock). #
# For example: #
# 0300 this is 3:00am #
# 1500 this is 3:00pm #
# The default value is 0000 (or midnight). #
# MAX_INPTMPDIR_CLEANTIME: This value specifies the maximum amount #
# of time spent in cleaning the inProgress #
# temporary directory at TSM startup #
# recovery time. When cleanup is done or at #
# expiration of this time, TSM will start #
# processing candidates. #
# The value of: #
# -1 : Do not do any clean up. #
# 0 : Clean up until it is all done #
# >0 : Time in mins to spend cleaning #
# The default is set to 15. The value is in #
# minutes. #
# #
# ACTIVEVAULT_HIGH_USE: Percentage of used licensed capacity at #
# which to begin the Active Vault policy. #
# The default value is 95.0 percent. #
# #
# ACTIVEVAULT_LOW_USE: Percentage of used licensed capacity at #
# which to stop the Active Vault policy. #
# The default value is 90.0 percent. #
# #
# ACTIVEVAULT_FULL_PERCENT: Percentage value used to check against to #
# determine if a medium is full enough for #
# vaulting consideration by Active Vault. #
# The default value is 90.0 percent. #
# #
# SPACE_DMON_POLL_TIME: Time to wait (in seconds) before the space#
# daemon wakes up to check file system fill #
# levels. The default value is 60 seconds. #
# #
# SMSTATSD_UPDATE_TIME: How often does the smstats daemon query #
# the database to update stats. Value is in #
# seconds. Default is 10 mins. NOTE: lower #
# values may result in too much activity to #
# the database. Minimum value allowed is #
# 1 min #
# #
# ALTSTORE_AGENT_PORT_NUMBER: The port number on which the altstore #
# daemon listens for incoming altstore #
# client connections. The default value #
# is 12333. The valid range is 1025-65535 #
# #
# ALTSTORE_TXFR_USERNAME: The user name to use for access to the #
# Alternate Store Location target MDC. #
# This user must exist on the target MDC #
# and is used for the transferring of files #
# to the target MDC staging area. #
# #
# ALTSTORE_POLL_TIME: Time to wait (in seconds) before the #
# altstore daemon wakes up to check for #
# alternate store location candidates. #
# The default value is 60 seconds. The #
# valid range is 60 to 300 seconds. #
# #
# ALTSTORE_NUM_SCRATCHPOOL: This is the number of internal working- #
# queue elements. It should be about 40 #
# times the number of simultaneous #
# transfer streams specified by #
# ALTSTORE_NUM_TXFR_STREAM. #
# #
# ALTSTORE_NUM_TXFR_STREAM: #
# Number of simultaneous transfer streams #
# for on-demand transfers in the Alternate #
# Store Location feature. #
# The optimal number depends on the number #
# of CPU cores in the server computer, the #
# capacity of the network hardware, the #
# ability of the destination computer to #
# handle traffic, and the contention with #
# other services using the network. #
# Testing can help to determine when this #
# number reaches diminishing returns of #
# total throughput. The default value is 5. #
# The valid range is 1 to 30. #
# #
# ALTSTORE_NUM_BG_TXFR_STREAM: #
# Number of simultaneous transfer streams #
# for background transfers in the Alternate #
# Store Location feature. #
# This is the maximum number of transfer #
# streams that can be used for transferring #
# background files when the streams are not #
# being used for on-demand transfers. This #
# ensures that on-demand transfers can be #
# responsive when new transfers are needed. #
# This number must be less than or equal to #
# ALTSTORE_NUM_TXFR_STREAM. #
# #
# ALTSTORE_TXFR_SCRIPT: Pathname of the customizable script for #
# transferring files in the Alternate Store #
# Location feature. #
# #
# ALTSTORE_RTRV_WAIT_COUNT: When retrieving truncated files, the #
# Alternate Store Location feature will #
# wait for this number of retrievable files #
# to accumulate before issuing a retrieve #
# request if the ALTSTORE_RTRV_WAIT_TIME #
# limit does not expire first. The default #
# value is 10. #
# #
# ALTSTORE_RTRV_WAIT_TIME: When retrieving truncated files, the #
# Alternate Store Location feature will #
# wait up to this many seconds for a batch #
# of retrievable files to accumulate if the #
# ALTSTORE_RTRV_WAIT_COUNT is not reached #
# first. The default value is 30 secs. #
# #
# ALTSTORE_VERSIONING: This value is configured on the source #
# MDC and controls the behavior that occurs #
# on the Alternate Store Location target #
# MDC for existing files when they are #
# being updated. #
# 'y' causes the file to be overwritten #
# which creates another Storage Manager #
# version of the file on the target MDC. #
# This option incurs higher CPU overhead. #
# 'n' causes the file to be re-created #
# which creates the first Storage Manager #
# version of a new file on the target MDC. #
# This option incurs lower CPU overhead. #
# #
# ALTSTORE_VERSIONING_TIMEOUT_FACTOR: #
# This value is configured on the source #
# MDC and controls the amount of time that #
# is allowed for file overwrites to occur #
# on the Alternate Store Location target #
# MDC before being considered an error. #
# This value is only applicable when #
# ALTSTORE_VERSIONING is set to 'y'. The #
# versioning timeout factor is specified in #
# seconds per gigabyte of data. This value #
# should be increased if file overwrites #
# are timing out. #
# #
# ALTSTORE_SUPPRESS_ALERTS: Suppress sending admin alerts for #
# Alternate Store Location remote copy #
# failures. #
# #
# ALTSTORE_MAX_CONNECTIONS: Maximum number of connections between a #
# remote-site Altstore daemon and all of #
# the main-site Altstore daemons it serves. #
# For Altstore daemons acting as a #
# remote-site, this value should be equal #
# to or greater than the sum of the values #
# (ALTSTORE_NUM_TXFR_STREAM + 1) for each #
# main-site. For Altstore daemons acting #
# as a main-site only, the default value is #
# recommended. The default value is 31. #
# #
# JOB_STATUS_RETENTION_TIME: This value determines the minium amount #
# of time job status information is #
# retained after the job completes. The #
# default value is 3600 seconds (1 hour). #
# #
# METADB_SM_L1_CACHE_SIZE: This value determines the L1 cache size #
# to be used in connections to the metadb #
# (mdarchive). The value is in MBytes. #
# The L1 cache is used for holding #
# uncompressed metadb index information. #
# #
# METADB_SM_L2_CACHE_SIZE: This value determines the L2 cache size #
# to be used in connections to the metadb #
# (mdarchive). The value is in MBytes. #
# The L2 cache is used for holding metadb #
# tablets. These tablets are general #
# containers which may contain row or #
# index data. #
# #
# METADB_SM_QRY_LIMIT: This value determines the limit on the #
# number of rows that will be returned #
# by most metadb queries. (The conversion #
# task has a different value and some #
# queries do not have a limit.) #
# #
# EXPORT_MAX_FILECOPY_CLUSTERS: This value determines the maximum #
# number of clusters (mover jobs) that an #
# fsexport filecopy operation will submit #
# in one call to the TSM subsystem. This #
# value * MAX_FILES_PER_CLUSTER equals the #
# maximum number of files submitted to TSM. #
# #
# EXPORT_LTFS_MAX_TOTAL_MEMORY_PERCENT: This value [0..100] represents #
# the maximum percent of total resident #
# and swap memory that an LTFS medium is #
# allowed to consume when the LTFS tape #
# filesystem is opened within TSM. #
# #
# FS_MAX_FDS_PER_PROCESS: This value represents the maximum number #
# of file descriptors that any TSM process #
# may have open. Both the soft and hard #
# limits will be increased to this value if #
# their current values are smaller. #
# #
# SHOWC_TRUNC_ESTIMATE: This value represents the number of #
# truncate candidate entries such that #
# showc -t will display only an estimated #
# value. The default value is 1 million. #
# A value of 0 indicates that it should #
# never use the estimated value. #
# NOTE: The larger the value, the longer #
# that the showc -t will take to run #
# An example, if there are greater than #
# 1 million candidates, showc -t will show #
# an estimate only. Anything less than #
# 1 million will be an actual value. #
# #
# DLP_COPY1_DRIVEPOOL_SET #
# ... #
# DLP_COPYn_DRIVEPOOL_SET: A comma-separated list of existing drive #
# pools to be used by the Dynamic Library #
# Pooling (DLP) feature. A list is specified #
# for each copy number up to the max number #
# of copies. TSM will use this list to #
# direct store requests to specific drive #
# pools on a rotating basis if DLP is #
# enabled for the policy class. Example: #
# DLP_COPY1_DRIVEPOOL_SET=pool1,pool2,pool3; #
# #
############################################################################
FS_STARTUP_TIMEOUT=300;
FS_MAX_ACTIVE_FORMATS=1;
FS_MAX_ACTIVE_TAPECOPIES=1;
CONNECT_SLEEP_TIME=1;
CONNECT_RETRIES=120;
MAX_READS=100;
MAX_WRITES=100;
MAX_RETRIEVE_RETRY_COUNT=3;
DRIVE_RETRIES=1;
MEDIA_RETRIES=2;
MIN_STARVE_TIME=5;
FS_NICE_VALUE=0;
LIC_CAPACITY_LVL1=65.0;
LIC_CAPACITY_LVL2=85.0;
MAX_INPTMPDIR_CLEANTIME=15;
#
# Resource Allocation Parameters
#
FS_THRESHOLD_INC_NUM=5;
FS_THRESHOLD_DEC_NUM=1;
FS_DRIVE_ERR_THRESHOLD=20;
PERCENT_FULL_TO_MIGRATE=99.9;
MEDIA_SUSPECT_THRESHOLD=3;
SNMS_BACKGROUND_FOREIGN_MOVERS=5;
FS_FIRST_POLICY_AT_LOSPACE=relocation;
FS_FIRST_POLICY_AT_NOSPACE=truncation;
CPYRESP_MAXVER_QRY_SECS=3600;
TSM_IGNORE_TOUCHES=false;
OPTIMIZE_RETRIEVE_QUEUE=true;
BACKUPFS=/stornext/snfs1;
CLEAN_VERSIONS_EXPIRATION=7y;
#
# Blocking Reads Parameters
#
FS_BLOCKING_READS=0;
#
# Checksum Generate/Validate Parameters
#
FS_GENERATE_CHECKSUMS=p; # default to policy settings
FS_VALIDATE_CHECKSUMS=p; # default to policy settings
#
# Database Parameters
#
FS_DB_LARGE_QRY_REC_LIMIT=10000;
FS_DB_LARGE_CLN_REC_LIMIT=10000;
#
# Policyd Parameters
#
POLICYD_NUM_OBJ_DELETE_THREADS=10;
POLICYD_NUM_FSYS_CONV_THREADS=2;
POLICYD_FSYS_CONV_BATCH_SIZE=5000;
POLICYD_FSYS_CONV_BATCH_LOOPS=5;
#
# Policy Parameters
#
MAX_STORE_SIZE=2000; # in Gigabytes
MAX_FILES_PER_CLUSTER=3000;
MAX_SEGMENTS_PER_FILE=50;
#
# Used by fs_tierman
#
DAILY_RELOC_START_TIME=0000;
DAILY_TRUNC_START_TIME=0000;
#
# Active Vault parameters
#
ACTIVEVAULT_HIGH_USE=95.0;
ACTIVEVAULT_LOW_USE=90.0;
ACTIVEVAULT_FULL_PERCENT=90.0;
#
# Used by fs_space
#
SPACE_DMON_POLL_TIME=60;
#
# Used by fs_smstatsd
#
SMSTATSD_UPDATE_TIME=600;
#
# Used by fs_altstore
#
ALTSTORE_POLL_TIME=60;
ALTSTORE_NUM_SCRATCHPOOL=200;
ALTSTORE_NUM_TXFR_STREAM=5;
ALTSTORE_NUM_BG_TXFR_STREAM=2;
ALTSTORE_TXFR_SCRIPT=/usr/adic/TSM/bin/fs_altstore_transfer;
ALTSTORE_RTRV_WAIT_TIME=30;
ALTSTORE_RTRV_WAIT_COUNT=10;
ALTSTORE_VERSIONING=y;
ALTSTORE_VERSIONING_TIMEOUT_FACTOR=60;
ALTSTORE_MAX_CONNECTIONS=31;
#
# Used by TSM processes connecting to the metadb (mdarchive)
#
METADB_SM_L1_CACHE_SIZE=256;
METADB_SM_L2_CACHE_SIZE=512;
METADB_SM_QRY_LIMIT=25000;
############################################################################
# MEDIA PARAMETERS: #
# #
# These parameters are used to tune how the software works with media. #
# The possible device type values which can be used in place of the XXX #
# can be obtained by running: fstypes -m -f tsm #
############################################################################
# DEFAULT_MEDIA_TYPE : Default media type used with commands #
# with optional media types. #
# #
# DEF_MED_SPC_XXX : Default tape length (in bytes) to use for #
# media XXX when the value can not be #
# determined from the drive. #
# #
# DEF_MED_SPC_LTO_LTFS : The maximum size of a file (in bytes) #
# that can be written to LTFS media. The #
# default is 1400000000000 (1.4TB) which is #
# based on LTO5 media capacity. Use one of #
# the values below based on the minimum LTO #
# generation number that you will support: #
# LTO-5 : 1400000000000 (1.4TB) - default #
# LTO-6 : 2400000000000 (2.4TB) #
# LTO-7 : 6400000000000 (6.4TB) #
# LTO-M8: 9600000000000 (9.6TB) #
# LTO-8 : 12800000000000 (12.8TB) #
# #
# MED_SEG_OVER_XXX : Media segment size overrides. Files larger#
# than this size will be segmented into #
# multiple chunks of this size. Note that #
# the defaults are calculated and the #
# overrides should only be used when #
# recommended by a technical rep. #
# For Lattus, the size must not be greater #
# than the smallest max object size that any#
# of the destination namespaces can support.#
# #
# These are system global parameters. #
# #
# LTFS_COMPRESSION Indicates if the LTFS media should be #
# formatted with or without compression. #
# This setting is used instead of #
# compression settings for the tape drives. #
# true: Compression is turned on #
# false: Compression is turned off #
# Default value is on (true) #
# #
# FS_CLUSTER_LIMIT_XXX : The maximum amount of data that will be #
# included in a cluster of data when #
# multiple files are written as a cluster #
# to a storage device. #
# #
############################################################################
DEFAULT_MEDIA_TYPE=LTO;
DEF_MED_SPC_LTO=800000000000;
DEF_MED_SPC_3592=500000000000;
DEF_MED_SPC_T10K=500000000000;
DEF_MED_SPC_LTOW=400000000000;
DEF_MED_SPC_LTO_LTFS=1400000000000;
# The values listed here are the approximately the values used.
MED_SEG_OVER_LTO=95000000000;
MED_SEG_OVER_3592=57000000000;
MED_SEG_OVER_T10K=114000000000;
MED_SEG_OVER_LTOW=95000000000;
MED_SEG_OVER_LATTUS=137438953472; # 128 GiB
MED_SEG_OVER_S3=137438953472; # 128 GiB
MED_SEG_OVER_GOOGLE=5497558138880; # 5 TiB
MED_SEG_OVER_GOOGLES3=5497558138880; # 5 TiB
MED_SEG_OVER_S3COMPAT=5497558138880; # 5 TiB
MED_SEG_OVER_AWS=5497558138880; # 5 TiB
MED_SEG_OVER_AZURE=5242880000000; # 100 MB X 50,000 blocks = 4.75 TB
# The following values keep the segments aligned on a 256k boundary
MED_SEG_OVER_SDISK=9499836416;
LTFS_COMPRESSION=true;
FS_CLUSTER_LIMIT_LTO=90000000000;
FS_CLUSTER_LIMIT_LTOW=63000000000;
FS_CLUSTER_LIMIT_3592=48000000000;
FS_CLUSTER_LIMIT_T10K=36000000000;
############################################################################
# DEVICE PARAMETERS: #
# #
# These parameters are used to tune how the software works with devices. #
# The possible device type values which can be used in place of the XXX #
# can be obtained by running: fstypes -d -f tsm #
############################################################################
# FS_VS_QUEUE_XXX_THRESHOLD : Mount request threshold value, which when #
# surpassed resource requests will be #
# queued in the software instead of media #
# manager software for the XXX media type. #
# Default: 20 #
# #
# FS_XXX_BLOCK_FACTOR : Number of i/o blocks to use when reading/ #
# writing on device XXX. The default block #
# factor sizes are considered to be optimal #
# for each device type. The i/o size used #
# for a device can by computed by #
# multiplying the block factor by 65536. #
# #
# FS_XXX_LTFS_BLOCK_FACTOR : Number of i/o blocks to use when reading/ #
# writing LTFS format on device XXX. The #
# default block factor sizes are considered #
# to be optimal for each device type. The #
# i/o size used for a device is computed #
# by multiplying the block factor by 65536. #
# The maximum block size for LTFS is 1MB #
# so the valid range for this parameter #
# is 0-16. This parameter is ignored for #
# devices that do not support LTFS label #
# formats. #
# #
# FS_XXX_OPEN_TRIES : Number of times an open will be retried #
# if it fails for device type XXX. #
# #
# FS_XXX_CLEAN_TIME : Maximum time (in seconds) it takes for a #
# cleaning tape of media type XXX to be #
# ejected from the time it is mounted in a #
# drive. #
# #
# FS_XXX_CLEAN_USAGE : Number of times a cleaning tape of media #
# type XXX will be used before the system #
# log message is generated indicating that #
# the cleaning media life expectancy has #
# expired and should be removed from the #
# system. #
# #
# FS_SCSI_RESERVE : Type of SCSI reservations for TSM to use. #
# none - no SCSI reservations #
# scsi2 - SCSI-2 reserve/release #
# reservations #
# scsi3 - SCSI-3 persistent #
# reservations (default) #
# multipath - no SCSI reservations #
# due to third party multipath #
# failover driver being used #
# Note: When DISTRIBUTED_MOVING is enabled, #
# this parm must be set to "scsi3" or #
# "multipath". #
# #
# SCSI_NO_SNS_EW_ERRS : This contains a comma separated list of #
# check conditions associated with the no #
# sense key of 0 which indicate that the #
# tape EOT early warning indicator has been #
# encountered and should be treated as an #
# error. This will result in the tape being #
# reclassified to the appropriate MIGRATE #
# media class so it will no longer be used #
# for storing data. The available space for#
# the media is set to 123 bytes in order to #
# distinguish this condition from EOT which #
# would show available space as 0. #
# This parameter helps with tape drive #
# performance when the drive takes seconds #
# to process writes each time this condition#
# is encountered. If that is not a concern #
# then this parameter can be set to "" #
# in order to utilize the tape until it is #
# full or the PERCENT_FULL_TO_MIGRATE fill #
# level has been reached. #
# The check conditions in the list should be#
# specified as a 4 character hexadecimal #
# value. The first 2 characters will map #
# to the additional sense code value and the#
# last 2 characters will map to the #
# additional sense code qualifier value. #
# Default is "0002,0007" #
# which is based on the 2 early warning #
# conditions defined in SCSI standards: #
# ASC/ASCQ #
# 00/02 END-OF-PARTITION/MEDIUM DETECTED #
# 00/07 PROGRAMMABLE EARLY WARNING DETECTED#
# #
# FS_CLEAN_DRIVES : 'y' indicates an attempt to mount a #
# cleaning media will be done when a drive #
# reports that cleaning is needed. This is #
# the default behavior. #
# 'n' indicates no drive cleaning will be #
# performed. This setting could be useful #
# if the system has no cleaning tapes in #
# order to prevent receiving RAS tickets. #
# #
# FS_OBJSTORAGE_CURL_TIMEOUT :This is a no progress timeout in seconds. #
# If there is 0 bytes transferred within #
# this time, the command will be terminated.#
# This timer restarts everytime forward #
# progress is detected. This is sampled by #
# libcurl every second. #
# Increase this value if there are network #
# issues that are resulting in no progress #
# timeout errors when storing/retrieving #
# files. #
# Default is 300 seconds. #
# FS_OBJSTORAGE_CURL_CONNECT_TIMEOUT : #
# The maximum amount of time in seconds to #
# allow the libcurl connection to #
# complete for delete operations. It is #
# recommended that this timeout be set to #
# a value smaller than the value specified #
# for FS_OBJSTORAGE_CURL_DEL_TIMEOUT. #
# Default is 10 seconds. #
# FS_OBJSTORAGE_CURL_DEL_TIMEOUT : #
# The maximum amount of time in seconds to #
# allow the libcurl delete operation to #
# complete. #
# Default is 60 seconds. #
# FS_OBJSTORAGE_CACERT : File name to a Certificate #
# Authority (CA) certificates. This can be #
# set to override libcurl's configured #
# default. #
# See fsobjcfg man page for libcurl default.#
# FS_OBJSTORAGE_CAPATH : Directory path that contains individual #
# CA certificate files. #
# This can be set to override libcurl's #
# configured default. See fsobjcfg man page #
# for libcurl default. #
# FS_OBJSTORAGE_SSL_VERIFY_PEERHOST : If value is 0, do not verify Peer #
# or Host. If value is 1, verify peer only #
# and if value is 2, verify peer and host. #
# This verification is done during https #
# handshake between Client and Server by #
# OpenSSL. Note that if the hostname used #
# wildcards in the CN of the certificate #
# then Host verification cannot be used. #
# FS_OBJSTORAGE_CURL_TCP_KEEPALIVE : If value is 1 TCP keepalive probes #
# will be sent. #
# FS_OBJSTORAGE_CURL_KEEPIDLE : Sets the delay, in seconds, that the #
# operating system will wait while the #
# connection is idle before sending #
# keepalive probes. #
# FS_OBJSTORAGE_CURL_KEEPINTVL : Sets the interval, in seconds, that the#
# operating system will wait between sending#
# keepalive probes. #
# FS_OBJSTORAGE_CURL_SO_SNDBUF : Sets the TCP socket send buffer size. #
# If value is 0, the system's default is #
# used. The default value is 0. #
# FS_OBJSTORAGE_CURL_SO_RCVBUF : Sets the TCP socket recv buffer size. #
# If value is 0, the system's default is #
# used. The default value is 0. #
# FS_OBJSTORAGE_LATTUS_SSL_CIPHER_LIST : Sets LATTUS SSL cipher list. #
# FS_OBJSTORAGE_QCV1_SSL_CIPHER_LIST : Sets QCV1 SSL cipher list. #
# FS_OBJSTORAGE_AWS_SSL_CIPHER_LIST : Sets AWS SSL cipher list. #
# FS_OBJSTORAGE_GOOGLE_SSL_CIPHER_LIST : Sets GOOGLE SSL cipher list. #
# FS_OBJSTORAGE_GOOGLES3_SSL_CIPHER_LIST : Sets GOOGLES3SSL cipher list.#
# Default "DEFAULT:-AESGCM #
# Disables GCM Cipher because #
# of 64GiB max size for GCM #
# FS_OBJSTORAGE_OPENSSL_NO_COMPRESSION : If value 1 turn OpenSSL #
# compression off. If value is 0, turn #
# OpenSL compression on. #
# FS_OBJSTORAGE_UPLOAD_PARTSIZE : Part size to use when performing #
# multipart upload for S3. Multi-threaded #
# uploading uses its internal calculation #
# to determine a file's upload part size. #
# FS_OBJSTORAGE_AZURE_BLOCK_PARTSIZE : Part size to use when #
# multipart upload for Azure Block Blob. #
# Multi-threaded uploading uses its #
# internal calculation to determine a #
# file's upload part size. #
# FS_OBJSTORAGE_C2S_CAP_HOSTPORT : Connection endpoint for the AWS #
# Commercial Cloud Services (C2S) Access #
# Portal (CAP) server. This has no default #
# value and must be set to use CAP #
# authentication. #
# FS_OBJSTORAGE_CLIENTCERT : Location of the X.509 client certificate #
# installed on the system for the CAP #
# server to authenticate. This has no #
# default value, and must be set to use CAP #
# authentication. #
# FS_OBJSTORAGE_CLIENTKEY : Location of the client private key if the #
# client private key is kept separately #
# from (i.e. not included in) the X.509 #
# client certificate file for CAP #
# authentication. This has no default #
# value, and must be set if required. #
# FS_OBJSTORAGE_CLIENTKEY_PASS : Passphrase for the client private key #
# if the client private key is protected by #
# a passphrase. This has no default value #
# and must be set if required. #
# FS_OBJSTORAGE_SEND_RATELIMIT : Object storage upload rate limit #
# Rate is specified in bytes per second #
# FS_OBJSTORAGE_RECV_RATELIMIT : Object storage download rate limit #
# Rate is specified in bytes per second #
# FS_OBJSTORAGE_FREE_PERCENT :Percentage value used to check against to #
# determine if enough space has been freed #
# from an object storage system to clear #
# the full state of media in that object #
# storage system. #
# Default is .5 percent. #
# FS_MAX_PARALLEL_XFER_IOSIZE : The IO buffer size for multi-threaded #
# parallel transfer. #
# IMP_COPY_NUM_THREADS : The number of threads to use to copy data #
# on file imports using the fsobjimport #
# command. The default value is 5. The #
# valid range is 1 to 50 threads. #
# IMP_DBASE_NUM_THREADS : The number of threads to use to update #
# the database on media imports using the #
# fsobjimport command. The default value is #
# 5. The valid range is 1 to 50 threads. #
# IMP_META_NUM_THREADS : The number of threads to use to create #
# the file metadata on media imports using #
# the fsobjimport command. The default #
# value is 5. The valid range is 1 to 50 #
# threads. #
# IMP_REMOVE_NUM_THREADS : The number of threads to use to remove #
# files or metadata using the fsobjimport #
# command. The default value is 5. The #
# valid range is 1 to 50 threads. #
# FS_OPEN_LTFS_ROOT : Path to the root of the open LTFS package #
# installation. #
# #
############################################################################
FS_VS_QUEUE_LTO_THRESHOLD=20;
FS_VS_QUEUE_3592_THRESHOLD=20;
FS_VS_QUEUE_T10K_THRESHOLD=20;
FS_DISK_BLOCK_FACTOR=10;
FS_LTO_BLOCK_FACTOR=8;
FS_LTO_LTFS_BLOCK_FACTOR=8; # valid range is 0-16
FS_3592_BLOCK_FACTOR=8;
FS_SDISK_BLOCK_FACTOR=4; # Should match the optimal I/O size for storage
FS_LATTUS_BLOCK_FACTOR=10;
FS_T10K_BLOCK_FACTOR=8;
FS_LTO_OPEN_TRIES=210;
FS_3592_OPEN_TRIES=230;
FS_SDISK_OPEN_TRIES=10;
FS_LATTUS_OPEN_TRIES=1; # Does nothing right now. May consider removing later
FS_T10K_OPEN_TRIES=230;
FS_LTO_CLEAN_TIME=120;
FS_3592_CLEAN_TIME=180;
FS_T10K_CLEAN_TIME=180;
FS_LTO_CLEAN_USAGE=50;
FS_3592_CLEAN_USAGE=100;
FS_T10K_CLEAN_USAGE=100;
FS_SCSI_RESERVE=scsi3;
FS_CLEAN_DRIVES=y;
FS_OBJSTORAGE_CURL_TIMEOUT=300;
FS_OBJSTORAGE_SSL_VERIFY_PEERHOST=2;
FS_OBJSTORAGE_CURL_TCP_KEEPALIVE=1;
FS_OBJSTORAGE_CURL_KEEPIDLE=60;
FS_OBJSTORAGE_CURL_KEEPINTVL=1;
FS_OBJSTORAGE_CURL_SO_SNDBUF=0;
FS_OBJSTORAGE_CURL_SO_RCVBUF=0;
FS_OBJSTORAGE_OPENSSL_NO_COMPRESSION=1;
FS_OBJSTORAGE_UPLOAD_PARTSIZE=2147483648;
FS_OBJSTORAGE_AZURE_BLOCK_PARTSIZE=104857600;
FS_OPEN_LTFS_ROOT=/opt/quantum/snltfs;
############################################################################
# TSM DEFAULTS PARAMETERS: #
# #
# These parameters are used with TSM-unique commands that allow defaults #
# (ie, addclass, modclass). #
############################################################################
# CLASS_SOFTLIMIT : Default soft limit for media allocated #
# to class. #
# CLASS_HARDLIMIT : Default hard limit for media allocated #
# to class. (> soft limit) #
# CLASS_MINTIME : Default store min time (in minutes). A #
# file will not be stored before it has #
# remained unmodified on disk for this #
# amount of time. It will eventually be #
# be stored sometime after that time. #
# The minimum allowed value is one minute. #
# (See NOTE on Class_Times below.) #
# CLASS_TIERTIME : Default tier min time (in days). A file #
# will not have its data blocks relocated #
# from one disk to another before it has #
# remained unaccessed on disk for this #
# amount of time. It MAY eventually be #
# relocated sometime after that time. #
# The minimum allowed value is five minutes.#
# (See NOTE on Class_Times below.) #
# CLASS_TRUNCTIME : Default trunc min time (in days). A file #
# will not have its disk blocks truncated #
# before it has remained unaccessed on disk #
# for this amount time. It MAY eventually #
# be truncated sometime after that time. #
# The minimum allowed value is five minutes.#
# (See NOTE on Class_Times below.) #
# #
# NOTE (Class_Times): The class times above (mintime, tiertime #
# and trunctime) can all be specified in #
# minutes, hours or days. A suffix of 'm', #
# 'h' or 'd' is used to indicate minutes, #
# hours or days respectively. If the value #
# is just a number without a suffix the #
# values default as indicated above. #
# Some examples of valid values: #
# 5m - five minutes #
# 3h - three hours #
# 7d - seven days #
# 10 - 10 minutes for mintime, 10 days #
# for tiertime and trunctime #
# #
# CLASS_TRUNCSIZE : Default trunc stub size (in KB). This is #
# the default stub size assigned to a #
# policy class when it is created. It can #
# range from 0 to 2147483647. If a larger #
# value is specified then it will be #
# adjusted back to the maximum value. #
# CLASS_STUB_READ_AHEAD : This indicates if the remainder of a file #
# should be retrieved when the data being #
# accessed is contained within the portion #
# of the file that is already disk resident #
# (referred to as the 'stub file). Control #
# is returned to the application immediately#
# while the rest of file data is retrieved #
# the in the back ground. Valid values are #
# true or false. #
# CLASS_DEF_MEDIA_TYPE : Default media type #
# CLASS_MAX_COPIES : Maximum number of copies allowed including#
# the primary copy. #
# CLASS_DEFAULT_COPIES : Total number of copies to store for each #
# file including the primary copy of the #
# file. Must not exceed CLASS_MAX_COPIES. #
# CLASS_FILE_CLEANUP : Default file cleanup action (I or P). #
# When a file is stored, cleanup may occur #
# immediately (I) after storing the file or #
# at policy application (P). #
# CLASS_MEDIA_CLEANUP : Default media cleanup action (C or S). #
# When a medium becomes logically blank, #
# the medium may return to the class blank #
# media pool (C) or to the system blank #
# media pool (S). #
# CLASS_MEDIA_FORMAT : Default tape media format type (ANTF/LTFS)#
# LTFS is only applicable to LTO media #
# generation 5 and beyond #
# (e.g. LTO-5, LTO-6, etc). #
# CLASS_MAX_VERSIONS : Default maximum number of versions to #
# keep for a file of this class. #
# CLASS_MINSETSIZE : Default minimum set size (in MB) for this #
# class. The store candidates in the class #
# have to add up to this value before any #
# of them can be stored by the policy #
# engine. Setting to zero will disable the #
# check. NOTE: if this is set to zero, then #
# CLASS_MAXSETAGE has to be set to zero as #
# well. #
# CLASS_MAXSETAGE : Default candidate expiration time (in #
# hours). As soon as any file on the store #
# candidate list in the policy class is #
# this value old, all of the files should #
# be stored. Setting to zero will disable #
# the check. #
# CLASS_AUTOSTORE : Default automatic store action (0 or 1). #
# The store daemon is allowed to automatic- #
# ally store the candidates of the class #
# (set to 1) or is not allowed (set to 0). #
# CLASS_DRIVEPOOL : Default drive pool (up to 16 characters) #
# Usually set to the same value as #
# Defined in terms of FILESERV_ID #
# VS_DEFAULT_DRIVEPOOL. #
# CLEANUP_PROCESSING : Default number of files processed per #
# transaction in the fsclean command. #
# POLICY_MAX_TRUNC_ENTRIES : The maximum number of files to truncate #
# each time for a space based file system #
# truncation policy. It is also used for #
# class based policy queries. The default #
# value is 3000 files. #
# POLICY_MAX_RELOC_ENTRIES : The maximum number of files to relocate #
# at a time for a relocation policy. The #
# default value is 3000 files. #
# POLICY_TRUNC_MINSIZE : Minimum file size in bytes to be passed #
# by the fs_store and fs_tierman daemons #
# to fspolicy when truncation policies are #
# launched by TSM automatically, by #
# passing this value as the '-z minsize' #
# option to fspolicy. EMERGENCY truncation #
# will always ignore this sysparm. #
# Valid range: Any integer from 1 to approx #
# 2 gigabytes (2^31 - 1 bytes), inclusive. #
# DFG_FULL_PERCENT : Percent at which the defrag utility #
# determines a media is full. #
# DFG_FRAG_PERCENT : Percent at which the defrag utility #
# determines a media is fragmented. #
# (This is the wasted space in the used #
# portion of the media.) #
# DFG_MAX_MEDCOPY_ATTEMPTS : Number of times fsdefrag will attempt to #
# run fsmedcopy before giving up. A #
# fsmedcopy needs to have successfully #
# copied some files before a failed #
# operation will be retried. #
# DFG_MAX_MEDIA_TO_DEFRAG : This parameter is used by the schedule #
# daemon when starting the fsdefrag command #
# for the defrag schedule item. The value #
# is used for the -n option when invoking #
# the command and will limit the number of #
# media that will be defragmented by the #
# defrag schedule item. #
# Note that a value of 0 is used to indicate#
# no max and all fragmented media will be #
# processed. (The -n option to fsdefrag #
# will be left off in this case.) #
# DFG_IGNORE_VAULTED_MEDIA : This parameter is used by the fsdefrag #
# process when it runs to determine what to #
# do with fragmented media that are #
# currently in a vault archive. Values: #
# - true - do nothing with the media #
# - false - process the media as usual #
# RMVERSIONS_TABLE_MAX_ROWS : This parameter is used by the rmversions #
# process to bound the number of records it #
# processes, to keep memory overruns from #
# occurring. Default is six million. #
# ALLOW_MOUNT_BETWEEN_ARCHIVE:Indicates whether media should be moved #
# between archives to satisfy requests. #
# 0=Mounts will fail if any movement is #
# needed between archives. #
# 1=Mounts will be attempted, regardless of #
# archive mode (attended or unattended). #
# 2=A mount will be performed with a move #
# if the archive mode of both archives is #
# attended. (Default value if not set) #
# MAX_EVENT_FILE_RETRIES : This parameter specifies the maximum #
# number of attempts to read an event file #
# by fs_async. #
# MAX_EVENT_DIR_RETRIES : This parameter specifies the maximum #
# number of attempts to query the FSMs for #
# their event directories while sntsm is #
# starting. The FSMs are queried at five #
# second intervals up to #
# MAX_EVENT_DIR_RETRIES attempts. #
# The default value is 6 (30 seconds). #
# #
# READ_FROM_STUB_OFFSET : This parameter indicates if retrieve #
# processing should start with data after #
# the stub file instead of the beginning of #
# the file. This has no impact on the #
# fsretrieve command or when checksum #
# validation is enabled. For both of these #
# cases the retrieve will always start with #
# the first byte of the file. #
# If this is enabled, it is reccomended #
# to use a stub size which is a multiple #
# of 512K for best retreive performance. #
# DISTRIBUTED_MOVING : This parameter indicates if distributed #
# data movers are enabled and if so what #
# the allocation strategy is. #
# The possible values are: #
# "none" #
# Data movers are run on the local host. #
# This is the default behavior. #
# "threshold" #
# Data movers are assigned to local host #
# until threshold is reached and then #
# the "all" strategy is applied. The #
# threshold can be configured with #
# fsddmconfig. #
# "all" #
# All configured hosts are used for #
# running data movers. A host is #
# selected based on the fewest number #
# of active data movers. For ties the #
# host that has the oldest allocation #
# time will be used. #
# DDM_CLIENT_RETRY_TIMEOUT : The amount of time (in seconds) to retry #
# the connection between the MDC and a DDM #
# client host, before the MDC stops #
# scheduling DDM operations for the client #
# host that it had connection issue with. #
# The default value is 30 seconds and the #
# maximum value is 3600 seconds. #
# RECURSION_BATCH_REPORT_INTERVAL : For CLIs using the -R <directory> #
# option or the -B <batchfilebname> option, #
# provide interim status updates to the #
# user each time a multiple of this #
# threshold number of files, directories, #
# media ids, etc, is reached. #
# The default value is 1000. #
# SYMLINK_MODE: For CLIs using the -R <directory> option, #
# processing will descend down the tree #
# from the dir provided. Default behavior #
# when symbolic links are encountered is #
# determined by this variable. Valid values #
# are 'follow': (follow the link like 'ls' #
# or 'cd' commands) or 'no_follow': (ignore #
# the links like the 'find' command). #
# The current commands using this sysparm: #
# fsrmcopy, fschdiat, fschfiat, fsexpcopy, #
# fsfilecopy, fsfileinfo, fsrmdiskcopy, #
# and fsstore. #
# The default value is 'follow'. #
# POL_RELOC_RESP_ABORT_TIME : The amount of time (in seconds) that a #
# relocation policy (fspolicy -r) waits #
# before sending a cancel request to the #
# TSM subsystem. #
# The default value is 43200 (12 hours). #
# POL_RELOC_RESP_SELECT_TIME : The amount of time (in seconds) that a #
# relocation policy (fspolicy -r) waits #
# for any status response. #
# The default value is 1800 (30 minutes). #
# POL_STORE_RESP_ABORT_TIME : The amount of time (in seconds) that a #
# store policy (fspolicy -s) waits before #
# sending a cancel request to the TSM #
# subsystem. #
# The default value is 43200 (12 hours). #
# POL_STORE_RESP_SELECT_TIME : The amount of time (in seconds) that a #
# store policy (fspolicy -s) waits for any #
# status response. #
# The default value is 1800 (30 minutes). #
# POL_CANCEL_RESP_SELECT_TIME : The amount of time (in seconds) that a #
# store or relocate policy will wait, #
# after sending a cancel request, for any #
# one cancel response, before aborting. #
# The default value is 300 (five minutes). #
# POL_SEND_CLUSTERS_CLASS : The number of complete clusters/requests #
# for a class based store policy to send at #
# a time. These are referred to below as #
# cluster sets. (The default of 0 implies #
# sending clusters/requests as soon as they #
# are "full", file count or bytes.) When set#
# a policy will continue sending complete #
# cluster sets as long as they are available.#
# Once a complete cluster set has been sent #
# no incomplete sets will be sent. The #
# remainder will be left for a following #
# policy run. If when started a complete #
# cluster set is not available, whatever is #
# available will be sent. #
# POL_CLUSTER_UNDERRUN : By default a cluster is considered full by#
# a store policy when it is within 200MB of #
# the cluster size. Setting this parm will #
# change the point at which a cluster is #
# considered full. This applies only to the #
# total bytes in the cluster, not the #
# number of files. #
# NOTE: If no suffix is provided with the #
# value it is assumed to be B (bytes).#
# #
# These parameters are used in the mapping of managed TSM file systems. #
############################################################################
# MAPPER_MAX_THREADS : The fs_mapper process maps each relation #
# point separately in a thread of its own #
# up to this max thread value. The remainder#
# of the relation points are mapped in the #
# main thread. The max value for this #
# variable is 256. The higher the value the #
# more memory that is used by a mapping #
# process. Note that the software does #
# NOT need to be cycled for updates. #
# #
############################################################################
CLASS_SOFTLIMIT=20000;
CLASS_HARDLIMIT=25000;
CLASS_MINTIME=5;
CLASS_TIERTIME=7;
CLASS_TRUNCTIME=3;
CLASS_TRUNCSIZE=0;
CLASS_STUB_READ_AHEAD=false;
CLASS_DEF_MEDIA_TYPE=LTO;
CLASS_DRIVEPOOL=fs_F0drivepool;
CLASS_MAX_COPIES=4;
CLASS_DEFAULT_COPIES=1;
CLASS_FILE_CLEANUP=P;
CLASS_MEDIA_CLEANUP=S;
CLASS_MEDIA_FORMAT=ANTF;
CLASS_MAX_VERSIONS=2;
CLASS_MINSETSIZE=0;
CLASS_MAXSETAGE=0;
CLASS_AUTOSTORE=1;
CLEANUP_PROCESSING=100;
#
# Used by fspolicy
#
POLICY_MAX_TRUNC_ENTRIES=3000;
POLICY_MAX_RELOC_ENTRIES=3000;
POL_RELOC_RESP_ABORT_TIME=43200;
POL_RELOC_RESP_SELECT_TIME=1800;
POL_STORE_RESP_ABORT_TIME=43200;
POL_STORE_RESP_SELECT_TIME=1800;
MAPPER_MAX_THREADS=64;
DFG_FULL_PERCENT=99.9;
DFG_FRAG_PERCENT=85;
DFG_MAX_MEDCOPY_ATTEMPTS=3;
DFG_MAX_MEDIA_TO_DEFRAG=5;
DFG_IGNORE_VAULTED_MEDIA=true;
ALLOW_MOUNT_BETWEEN_ARCHIVE=2;
MAX_EVENT_FILE_RETRIES=3;
MAX_EVENT_DIR_RETRIES=6;
READ_FROM_STUB_OFFSET=false;
DISTRIBUTED_MOVING=none;
#
# Used by mover
#
DDM_CLIENT_RETRY_TIMEOUT=30;
#
# Used by several CLIs with the -R or -B option.
#
RECURSION_BATCH_REPORT_INTERVAL=1000;
SYMLINK_MODE=follow;
############################################################################
# MEDIA MANAGER-SPECIFIC PARAMETERS: #
# #
# These parameters are specific to processing involving the media manager. #
############################################################################
# #
# FILESERV_ID : A 2 character unique identifier used to #
# differentiate Tertiary Manager Systems #
# connected to the same Media Manager host#
# This identifier is the prefix for all #
# MediaClass and DrivePool names #
# It is set up during installation. #
# VS_DEF_QUANTITY : Default number of media for Media #
# Manager entry/exit operations. #
# (Range 1-99) #
# VS_DEFAULT_DRIVEPOOL : Default Media Manager Drive Pool. #
# This drive pool should contain all #
# configured drive components #
# This drive pool will be used #
# for media with no DataClass. #
# Defined in terms of FILESERV_ID. #
# VS_DIR : This should point to MSM environment #
############################################################################
FILESERV_ID=F0;
VS_DEF_QUANTITY=99;
VS_DEFAULT_DRIVEPOOL=fs_F0drivepool;
VS_DIR=/usr/adic/MSM;
############################################################################
# INSTALLATION PARAMETERS: #
# #
# These are the system parameters that are to be established at the time #
# of system installation. The TSM installation script should be used for #
# this purpose. As a general rule, these parameters should NOT be #
# modified unless the system is completely reinitialized and reinstalled. #
############################################################################
# #
# FS_CONSOLE : TSM console device path. #
# FS_DEFAULT_SUBSYSTEM : Default component id for fsmedin, #
# fsmedout, and fsqueue when user does #
# not specify subsystem on command. #
# #
# These parameters are used to set UGO permissions, and group ID #
# for any files created by TSM #
# FS_FILE_MODE : UGO permissions for fs files #
# FS_FILE_GROUP : Group ID for fs files and administrator #
# FS_OPR_GROUP : Group ID for fs operators #
# #
# FS_OWNER_ID : Owner ID for TSM files and database #
# owner's user ID. #
# #
# #
############################################################################
FS_CONSOLE=/dev/console;
FS_DEFAULT_SUBSYSTEM=V0;
# 511 - decimal value of octal permissions 777 #
FS_FILE_MODE=511;
FS_FILE_GROUP=adic;
FS_OPR_GROUP=adic;
FS_OWNER_ID=tdlm;
############################################################################
# SOFTWARE MAINTENANCE PARAMETERS: #
# #
# These parameters can be modified as required for software maintenance. #
# #
############################################################################
# These parameters are used to enable and disable different types of #
# message output. #
# #
# COMMAND_INFO_DETAIL : Enables detailed or internal #
# software messages to be displayed to user #
# y: enable #
# n: disable #
# COMMAND_EXTRACT_HEADER : If enabled, removes the message number, #
# priority, and request id from the status #
# returned to the user. #
# y: enable #
# n: disable #
# #
############################################################################
COMMAND_INFO_DETAIL=y;
COMMAND_EXTRACT_HEADER=n;
Information on the System Parameters Page
| Parameter | Description |
|---|---|
| Name |
Displays the name of the system parameter. For additional information about system parameters, see the |
| Value |
Displays the value of the system parameter. This also serves as a free-form text entry field so that you may update a system parameter value. Caution: When editing values, ensure that the value you enter for a given system parameter is valid. An invalid value can interfere with proper functioning of Storage Manager. Updating a system parameter value restarts Storage Manager. |
| Adjusted | Displays Yes, or No, which signifies whether the default Storage Manager system parameter value has been overridden. |
| Apply | Click to apply the system parameter in the Value field for a given system parameter Name (row). |
| Reset | Click to clear all the values in the Value field for all system parameters in the table. |
| Done | Click to exit the System Parameters page. |
Edit or Update a System Parameter Value
- On the Tools menu, click Storage Manager, and then click System Parameters. The Tools > Storage Manager > System Parameters page appears.
-
Select a system parameter under the Name column (click a row), and then input a valid system parameter into the text field under the Value column. If necessary, click Reset to clear all the values in the Value field for all system parameters in the table.
- Click Apply to submit your system parameter changes. A confirmation dialog appears.
- Click Yes to confirm your changes, or click No to cancel your changes and return to the System Parameters page.
Exit the System Parameters Page
Click Done to exit the System Parameters page.
