2. Template dsm.sys options file
* TSM Archiving on a Unix System * This is the example dsm.sys file for use with Archive to the * HFS at Oxford from a Unix client. As supplied, it must be * edited as described below. * In the line * Nodename CHANGE.THIS * you must alter the CHANGE.THIS to the registered name of * your archive client node. This will (probably) be of the * form something.archive or something_archive.dept * As things are set up below, you will have to type in your * password the first time you invoke the TSM software. * It will then be stored on your client in encrypted form * so that the scheduler can subsequently pass it to the * server without needing input from you. TSM will change * your password at roughly yearly intervals, and needs to * tell you what the new password is when it does so. The line * Mailprog MAIL-PROG root * tells TSM to use the (mail) program specified by MAIL-PROG * to mail this new password to root. You should replace * MAIL-PROG by a suitable mail agent executable, and perhaps * replace root by some more suitable username. For example * Mailprog /usr/bin/mailx admin * By default all users and members of all groups are permitted * to use TSM (permissions on the executables being ok). To * restrict this, uncomment the *Users and *Groups lines and * substitute as argument a space-separated list of usernames * and groupnames. If both lines are amended in this manner * the users specified and all members of the groups specified * will have access to TSM. * The other lines set up default values for various options. * You should not change any of these unless you know what you * are doing (i.e. have read the TSM client manual), or under * advice from OUCS. * If your system is already using TSM backup, you will already * have a dsm.sys file on your system. In this case copy the * uncommented section below (after editing it as above) * and append it to the end of your existing dsm.sys * file; the file will then have two "stanzas", one for backup and * one for archive. You will note that the names both of the TSM * server and your node name for use with archiving are different * from the names used for backup. You must take care to retain * these differences * If your system is only using TSM Archive, then save this file * after editing it. * This file must be placed in different places in the filestore * depending on your platform (and in some cases operating system * version). The following table lists where it should go, provided * you have installed TSM software at its default location. * IBM AIX /usr/bin/dsm.sys * SGI IRIX a symbolic link from * /usr/tivoli/tsm/client/ba/bin/dsm.sys * * Linux /usr/bin/dsm.sys * Sun Solaris 2.6/7/8/9 a symbolic link from * Sun Solaris 10 /opt/tivoli/tsm/client/ba/bin/dsm.sys Servername OX_HFS CommMethod TCPIP TCPServeraddress dsma.ox.ac.uk TCPPort 2000 Nodename CHANGE.THIS PasswordAccess generate Mailprog MAIL-PROG root Compression no *Users space-separated-list *Groups space-separated-list *VirtualMountPoint directory-name TCPBuffSize 32 TCPWindowSize 63 TCPNodelay yes TxnByteLimit 25600 * end-of-file
Up: Contents Previous: 1. Configuring the TSM Unix client for Archive