ADSM AUTHORIZED USER
An ADSM authorized user on your workstation is responsible for setting options in the client system options file. This file contains these options:
If you have the ADSM HSM client installed on your workstation, the client system options file can also contain space management options.
During installation and setup of ADSM, a sample client system options file called dsm.sys.smp is provided. Copy the dsm.sys.smp file to dsm.sys in your ADSM installation directory, and modify the required options in the new copy. Required options are those that provide information the ADSM client programs need to establish communication with an ADSM server.
The following sections provide an overview of all the options you can set in the client system options file. Use this information to help you decide whether to modify any other options.
Figure 5 lists the authorization options that control access to an ADSM
server.
Figure 5. Authorization Options
| Option | Description | Page |
|---|---|---|
| groups | Specifies the groups on your workstation for which you want to request services from the ADSM server. | Groups |
| mailprog | Specifies the program and user ID to which you want ADSM to send a newly-generated password when the old one expires. Use this option only when the passwordaccess option is set to generate. | Mailprog |
| passwordaccess | Specifies the way in which you want ADSM to handle a password if one is required for your workstation. | Passwordaccess |
| users | Specifies the users on your workstation who can request services from an ADSM server. | Users |
Figure 6 lists the client options that control some aspects of backup
and archive processing.
Figure 6. Backup and Archive Client Options
| Option | Description | Page | ||
|---|---|---|---|---|
| automount | Specifies a symbolic link to an NFS mount point monitored by the automount daemon (SunOS) or the automounter (Solaris) that you want ADSM to consider as a valid domain for incremental backup. | Automount | ||
| changingretries | Specifies the number of retries to attempt when backing up or archiving a file that is in use. | Changingretries | ||
| compressalways | Specifies what ADSM does when a file grows during compression.
| Compressalways | ||
| compression | Specifies whether ADSM should compress files before sending them to the ADSM server. | Compression | ||
| dirmc | Specifies the management class to use for backed up directories. If this is not specified, the management class with the longest retention period is used. | Dirmc | ||
| dotcheck | Specifies whether ADSM checks for "." and ". ." entries in a directory. | Dotdircheck | ||
| inclexcl | Specifies the path and file name of your include-exclude options file. | Inclexcl | ||
| virtualmountpoint | Specifies a directory to serve as a virtual mount point for a file system. This provides a direct path to the files you want ADSM to consider for backup, saving processing time. | Virtualmountpoint |
Communication options specify how your client node communicates with an ADSM server. The options you specify depend upon which communication protocol you choose. Specify which protocol to use with the commmethod option. The default is TCP/IP. For more information, see Commmethod.
Use the communication methods listed below.
Ask your ADSM administrator for assistance in setting your communication options.
TCP/IP must be installed on your workstation to use the shared memory
communication method.
Figure 7. Shared Memory Option
| Option | Description | Page |
|---|---|---|
| shmport | Specifies the TCP/IP port address on which the server listens to establish a shared memory connection (AIX, HP-UX, and Solaris only). | Shmport |
Include either the symbolicdestination option or all of the
following options: cpicmodename, partnerluname,
and tpname to use the SNA LU6.2 protocol (available on an
AIX workstation only).
| Option | Description | Page |
|---|---|---|
| cpicbuffersize | Specifies the buffer size for SNA LU6.2 communication. | CPICBuffersize |
| cpicmodename | Specifies the mode name for SNA LU6.2 communication. | CPICModename |
| partnerluname | Specifies a logical unit name that the transaction program uses to identify the ADSM server in the SNA network. | Partnerluname |
| symbolicdestination | Specifies a symbolic ADSM server name. | Symbolicdestination |
| tpname | Specifies a symbolic name for a transaction program in an SNA network. The transaction program identifies the target logical unit (LU), which is the ADSM server. | TPName |
To use the TCP/IP protocol, include the tcpserveraddress
option in your client system options file. The other TCP/IP options
have default values. Modify those options only if you want to change
their default values.
| Option | Description | Page |
|---|---|---|
| tcpbuffsize | Specifies the size, in kilobytes, of the ADSM internal TCP/IP communication buffer. | TCPBuffsize |
| tcpnodelay | Specifies that ADSM immediately send small transactions to the server. This is available for the AIX client only. | TCPNodelay |
| tcpport | Specifies the TCP/IP port address for an ADSM server. | TCPPort |
| tcpserveraddress | Specifies the TCP/IP address for an ADSM server. | TCPServeraddress |
| tcpwindowsize | Specifies the size, in kilobytes, of the TCP/IP sliding window for your client node. | TCPWindowsize |
Use these options to provide information to ADSM when you perform scheduled work. ADSM uses scheduling options only when the schedule command is running.
ADSM server settings can override most of these options after the
backup-archive client program on your workstation connects with the ADSM
server.
| Option | Description | Page |
|---|---|---|
| maxcmdretries | Specifies the maximum number of times the client scheduler attempts to process a failed, scheduled command. | Maxcmdretries |
| postschedulecmd | Specifies a command to process after running a schedule. | Postschedulecmd, Postnschedulecmd |
| preschedulecmd | Specifies a command to process before running a schedule. | Preschedulecmd, Prenschedulecmd |
| queryschedperiod | Specifies the number of hours the client scheduler waits between unsuccessful attempts to contact the ADSM server for scheduled work. | Queryschedperiod |
| retryperiod | Specifies the number of minutes the client scheduler waits between attempts to process a failed, scheduled command, or between unsuccessful attempts to report results to the server. | Retryperiod |
| schedlogname | Specifies the filename where schedule log information is stored. | Schedlogname |
| schedlogretention | Specifies the number of days to keep log file entries in the schedule log, and whether to save pruned entries. | Schedlogretention |
| schedmode | Specifies which schedule mode to use, polling or prompted. | Schedmode |
| tcpclientaddress | Specifies the TCP/IP address of your client node. Use this only with the schedule command when you specify prompted as the schedule mode. | TCPClientaddress |
| tcpclientport | Specifies the TCP/IP port number of your client node. Use this only with the schedule command when you specify prompted as the schedule mode. | TCPClientport |
Each client node that communicates with an ADSM server must have a node name, and each server with whom your client node communicates, must be identified with a server name.
The default node name for your client node is the name returned by the hostname command. If necessary, you can assign a different node name to your client node. For example, if you have one workstation named AIXsrvr1 and one named AIXSRVR1, an ADSM server would recognize both as the same client node. To change the node name for a client node, specify a different name with the nodename option in your client system options file (dsm.sys).
For special situations, you can also use the virtualnodename option with a command to indicate that you want to request services for a different client node. See "Server and Node Options" for information about using the virtualnodename option for that purpose.
When connecting to a server, the ADSM client must identity itself to the server. This login identification is determined as follows:
Your client node communicates with a particular ADSM server depending upon the options you set in your client system options file. Enter options in stanzas in the client system options file. Each stanza begins with a servername option and must contain all options required to establish communication with an ADSM server.
If your client system options file contains only one stanza, your client node contacts the server specified in that stanza for all services.
If your client system options file contains more than one stanza, you can:
If you do not specify a default server, by default, ADSM contacts the server specified in the first stanza of your client system options file.
If you specify a migration server with the migrateserver option, it overrides what is specified with the defaultserver option for migration only.
If you do not specify a default server or a migration server, by default, ADSM contacts the first server specified in your client system options file.
Place the defaultserver and migrateserver options at the beginning of your client system options file before any server stanzas.
Figure 11 shows a sample client system options file.
Figure 11. Sample Client System Options File
+--------------------------------------------------------------------------------+ |DEFAULTServer server2 | |MIGRATEServer server1 | | | |Servername server1 | | COMMmethod TCPip | | TCPPort 1500 | | TCPServeraddress almvmd.almaden.ibm.com | | Passwordaccess generate | | Mailprog /usr/bin/xsend root | | Groups system adsm | | Users pacheco brown sullivan | | Inclexcl /adm/adsm/backup1.excl | | | |Servername server2 | | COMMmethod SNAlu6.2 | | PARtnerluname raptor | | TPname appcdel | | CPICMOdename appc | | Passwordaccess prompt | | Groups system adsm | | Users jones tallan arbis | | Inclexcl /adm/adsm/backup2.excl | +--------------------------------------------------------------------------------+ |
If you include the servername option, you can also specify which server to contact for backup-archive services in your default client user options file. If you specify which server to contact in the default client user options file, that overrides the default server specified in your client system options file. In addition, users can override the server you specify for backup-archive services by:
Users cannot override the migration server that you specify in the client
system options file.
Figure 12. Server and Node Options
| Option | Description | Page |
|---|---|---|
| defaultserver | Specifies the default name of the ADSM server to contact for
backup-archive services if more than one server is defined in the client
system options file.
Also specifies the ADSM server to contact for space management services if you do not specify a server with the migrateserver option. | Defaultserver |
| migrateserver | The ADSM server to contact for space management services. | Migrateserver |
| nodename | Specifies the name of your workstation used to establish communication with the ADSM server. | Nodename |
| servername | Specifies the name of an ADSM server to contact for services. | Servername |
If you have the ADSM HSM client installed on your workstation, you can set the options listed in this section in your client system options file. These options affect automatic migration, recall, and reconciliation.
Because most space management options apply to your client node and not to a particular ADSM server, they must be placed before any server stanzas in your client system options file. The exception is the errorprog option. You can place an errorprog option in each server stanza.
For information about the ADSM HSM client, see Using the UNIX HSM
Clients.
Figure 13. Space Management Options
| Option | Description | Page |
|---|---|---|
| checkthresholds | Specifies how often the space monitor daemon checks space usage on your file systems. | Checkthresholds |
| errorlogname | Specifies the fully qualified path and file name of the error log. | Errorlogname |
| errorprog | Specifies the path and file name of the program HSM notifies if a severe error occurs during space management processing. | Errorprog |
| kernelmessages | Determines whether HSM-related messages sent by the kernel, are displayed. | Kernelmessages |
| maxrecalldaemons | Specifies the maximum number of recall daemons that can run at one time. | Maxrecalldaemons |
| maxreconcileproc | Specifies the maximum number of file systems HSM can reconcile automatically at one time. | Maxreconcileproc |
| maxthresholdproc | Specifies the maximum number of threshold migration processes that HSM can perform automatically at one time. | Maxthresholdproc |
| migfileexpiration | Specifies the number of days a migrated or premigrated file remains in ADSM storage after it is modified on the local file system or erased from the local file system. | Migfileexpiration |
| minrecalldaemons | Specifies the minimum number of recall daemons to retain. | Minrecalldaemons |
| reconcileinterval | Determines how often HSM automatically reconciles the file systems on your workstation. | Reconcileinterval |
The following options control how ADSM processes transactions between the
client and server.
Figure 14. Transaction Processing Option
| Option | Description | Page |
|---|---|---|
| largecommbuffers | Specifies whether the client will use increased buffers to transfer large amounts of data between the client and the server. | Largecommbuffers |
| nfstimeout | Specifies the amount of time in seconds ADSM will wait for an NFS system call response before timing out. | NFSTimeout |
| txnbytelimit | The number of kilobytes ADSM can buffer in a transaction before sending data to the server. | Txnbytelimit |