Hi Thomas, We surely do. I have source for TSM scripts, AIX shell scripts for reporting out TSM data, /etc/inittab, crontab, dsmaccnt.log, snmp customization and other customization I've probably forgotten about on the TSM server that would be a real pain in the posterior to recreate. So we backup the TSM server with the baclient.
Just make sure you put in an EXCLUDE for .dsm files (or whatever other naming convention you use) so you don't backup TSM db, log, and stgpool container files. You surely don't want to back up those with the baclient. Then very little, except customization, changes on the TSM server, anyway. So the cost is very small, and well worth it. It has saved me time and grief before, more than once. -----Original Message----- From: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 1:17 PM To: [EMAIL PROTECTED] Subject: Backing up the TSM server itself Hi TSM-ers, I'm backing up the TSM server files to another machine (DEVCONFG.FILE, DSMSERV.DSK, DSMSERV.OPT, VOLHIST.FILE). Does it make sense to backup the rest of the TSM Server using the TSM client? I'm running TSM 4.1.5.0 on AIX 4.3.3 Kind regards and greetings from Austria Thomas Rupp Vorarlberger Illwerke AG MAIL: [EMAIL PROTECTED] TEL: ++43/5574/4991-251 FAX: ++43/5574/4991-820-8251 ---------------------------------------------------------------------------- -------------- Dieses eMail wurde auf Viren geprueft. Vorarlberger Illwerke AG ---------------------------------------------------------------------------- --------------
