Notes on when I configured the AFS backups on 2-12-2001 and when I configured them again for the Sunnyvale office on 10-17-2005 ============================================================================= AFS is backed up with the following root crontab entry on the AFS server, afs1: # ... run the nightly AFS incremental backups. # Be careful to use the AFS version of the dsmc client, as it understands # AFS ACL's. Note this uses the standard dsm.opt file from the # /usr/tivoli/tsm/client/ba/bin directory, so a dumb user can recover their # AFS files by logging onto their userid on afs1, and simply typing dsmcafs. 10 1 * * * /usr/bin/pagsh -c /afs/d/servers/afs1/Do_AFS_Backups.sh >> /afs/d/servers/afs1/AFS.ADSM.logs/output.$(/usr/bin/date +\%Y\%m\%d) 2>&1 See that Do_AFS_Backups.sh script for more details as well as the appropriate files in the /usr/tivoli/tsm/client/ba/bin directory for more details. We take pains to use the AFS-aware version of dsmc so that ACLs are handled correctly. To restore, any user should be able to login to afs1 and invoke the dsmcafs (but when I tried this as a non-root user, I didn't know how to authenticate to the TSM server. What userid & password do I use? I couldn't read the /etc/security/adsm/AFS.SPACE file. How did this work in Almaden? Somehow point to a different password file? I dunno, but this doesn't work for a general user as I thought it did. I guess I never tested it.) ============================================================================= These notes came out of the AFS online documentation, specifically, file:///afs/d/afsdoc/Html/en_US/html/RelNotes/aurns004.htm#HDRTSM when running a web browser from an AIX system with AFS on it. The AFS online documentation is in /afs/d/afsdoc/Html ... I've bracketed my comments with (( ... )) as I followed these directions. ============================================================================= Configuring the Backup System and TSM Perform the following steps to configure TSM and the AFS Backup System for interoperation. Note: You possibly need to perform additional TSM configuration procedures unrelated to AFS. See the TSM documentation. 1. As root ((on the AFS server machine)), 2. Install version 3.7.1 of the TSM client API on the local disk of the Tape Coordinator machine. If you do not already have the API, ... (( Directions on how to ftp tivoli.tsm.client.api.aix43.32bit from ftp.software.ibm.com, in the /storage/tivoli-storage-management-maintenance/client/v3r7/AIX/v371 directory, then install tivoli.tsm.client.api.aix43.32bit, deleted. I had version 4.1.2.0 in /afs/d/software/base/Tivoli.Storage.Manager-4.1.2.0/AIX )) (( This installed 70 files in /usr/tivoli/tsm/client/api/bin and 2 links in /usr/lib. I didn't see any interesting files at first glance. )) (( While I was at it, I also configured the nightly incremental backups for the normal AIX stuff. )) 3. Set the following TSM environment variables as indicated. If you do not set them, you must use the default values specified in the TSM documentation. (( Which is probably /usr/tivoli/tsm/client/api/bin. This is the same directory that the DB/2-Dump-Directly-to-ADSM client uses. Normally, one might have a dsm.sys & dsm.opt file in elephant's /usr/tivoli/tsm/client/api/bin directory, which is Delphion's test DB/2 machine, but we had troubles one day when I changed elephant's /usr/tivoli/tsm/client/ba/bin/dsm.sys, but failed to change the dsm.sys in /usr/tivoli/tsm/client/api/bin, so I made them links to one another. I did the same thing for afs1, namely ln -s ../../ba/bin/dsm.opt /usr/tivoli/tsm/client/api/bin/dsm.opt ln -s ../../ba/bin/dsm.sys /usr/tivoli/tsm/client/api/bin/dsm.sys )) 4. Verify the dsm.sys file. 5. Verify the dsm.opt file. 6. Create a Backup Database entry for each Tape Coordinator that is to communicate with the TSM server. Multiple Tape Coordinators can interact with the same TSM server if the server has sufficient capacity. # backup addhost where tape machine name Specifies the fully qualified hostname of the Tape Coordinator machine. TC port offset Specifies the Tape Coordinator's port offset number. Acceptable values are integers in the range from 0 (zero) through 58510. (( I typed /usr/afs/bin/backup addhost adsmsrv1 -localauth (portoffset defaults to 0) Confirmed with a /usr/afs/bin/backup listhosts command. ... Upon reflection, I think this was wrong. The tape coordinator machine is afs1, not adsmsrv1. I think what we want here, is the machine that will be running the butc process. In the pre-AFS 3.6 days, (I think) we needed to run a special, ADSM replacement for the butc binary, called buta. But according to what I read, buta isn't used/needed because the normal AFS butc binary, understands how to talk to a TSM server. Thus we use the normal AFS butc command, which means running butc on afs1. Thus I redid the addhost cmd, /usr/afs/bin/backup addhost afs1 )) 7. Create a device configuration file for the Tape Coordinator called /usr/afs/backup/CFG_tcid, where tcid is the Tape Coordinator's port offset number as defined in Step 6. The file must include the following instructions: SERVER, which takes as its argument the fully qualified hostname of the TSM server machine. It matches the value in the full_machine_name field of the dsm.sys file, as defined in Step 4. TYPE, which takes as its argument the string tsm (the only acceptable value in AFS 3.6). One of PASSWORD or PASSFILE, to define the password which the Tape Coordinator uses when communicating with the TSM server. PASSWORD takes as its argument the actual password character string. PASSFILE takes as its argument the complete pathname of the file that contains the string on its first line. For more detailed descriptions of the instructions, and of other instructions you can include in the configuration file, see CFG_tcid. (( I created /usr/afs/backup/CFG_0, which contained just SERVER adsmsrv1 TYPE tsm I may have to include either a PASSWORD or PASSFILE statement, later. )) ======================================================================================== I printed off and started following the "Configuring the AFS Backup System" section of the AFS Administration Guide (file:///afs/d/afsdoc/Html/en_US/html/AdminGd/auagd011.htm#HDRWQ333), but hit a roadblock on the "Defining and Displaying Volume Sets and Volume Entries" when adding volume entries into a backup volume set, i.e. on afs1, authenticated as either jasper or admin, I could define a volume set, but when I tried adding to it, it failed. I thought I would organize the backups based on the schedule of full and incremental backups, e.g. /usr/afs/bin/backup addvolset Weekly_Full-Daily_Incremental, which worked fine, but then /usr/afs/bin/backup addvolentry Weekly_Full-Daily_Incremental afs1 a 'u\.pjelleff\.backup' to just test one volume, gave the error, backup: ; Volume entry not added backup: waiting for job termination I couldn't figure it out. There was a patch to AFS 3.6, which I downloaded at /afs/d/software/fixes/AFS_3.6_Patch_1, but I didn't bother to do anything with it. I read the release notes and didn't see anything that led me to believe the patch would fix anything. ======================================================================================== I decided to concentrate on the other kind of AFS backups, doing incremental backups with the dsmafsc TSM client, ala the midway backups at Almaden.