Base IBM Storage Protect client configuration files for IBM Storage Scale usage

This topic lists all the Base IBM Storage Protect client configuration files and their examples for IBM Storage Scale.

Important: While the IBM Storage Protect client configuration file dsm.sys can contain node-specific information, it cannot be copied from node to node without touching or correcting the corresponding node-specific information.

The following are example contents of IBM Storage Protect configuration files.

Contents of dsm.sys

Note: Substitute the variables starting with '$' with your own required value. See the following example values of variables.

Servername $servername
    COMMMethod         TCPip
    TCPPort            $serverport
    TCPServeraddress   $serverip
*   TCPAdminport       $serveradminport      
    TCPBuffsize        512
    PASSWORDACCESS     generate
* Place your exclude rules here or configure as cloptset on TSM server
    ERRORLOGName       $errorlog
    ASNODENAME         $client-node-proxyname
    NODENAME           $localnodename

Example values of variables used in dsm.sys

serverport=1500
serverip=myTSMserver.mydomain.org         OR    serverip=1.2.3.4
serveradminport=1526
errorlog=/var/log/mylogs/dsmerror.log
client-node-proxyname=proxy-cluster1
localnodename=gpfs-node1

Contents of dsm.opt

* Special character test flags
QUOTESARELITERAL YES
WILDCARDSARELITERAL YES
* to take traces just remove the * from the next two lines:
*TRACEFLAG SERVICE
*TRACEFILE /tmp/tsmtrace.txt

Contents of dsm.opt when IBM Storage Protect for Space Management is used

* HSM: Write extObjID to DMAPI attribute 'IBMexID' for migrated/pre-migrated files
HSMEXTOBJIDATTR yes
* HSM: Deactivate HSM Automigration and Scout search engine as this will be done by GPFS
HSMDISABLEAUTOMIGDAEMONS YES
* HSM file aggregation of small files
HSMGROUPedmigrate yes
* HSM: Determines if files that are less than 2 minutes old can be migrated during selective migration
hsmenableimmediatemigrate yes