Hi, I have had good experience in creating a TSM Administrative Schedule that saves volhist and devcnfg to disk. Then I've made a client schedule that sends a mail with those files (and different status messages for TSM) to backupoperators (including an external account, in case of a complete disaster - mailserver and TSM server are in the same location).
Rgds. Geirr G. Halvorsen -----Original Message----- From: Coats, Jack [mailto:[EMAIL PROTECTED]] Sent: 1. august 2002 21:50 To: [EMAIL PROTECTED] Subject: Re: How to save volhist and devconfig Brian, Yes, we do that. On our windows TSM server we automatically run a batch file that 1) saves the volhist and devconfig into a local directory. 2) copies all this, and the license files to two servers at other locations across our network 3) generates a floppy disk with the same info on it to go out with the database backup tape each morning, at the same time we send off offsite backups. I wanted to run it from the TSM scheduler and that was a little trickier, but doable with some help from this list :) -----Original Message----- From: brian welsh [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 2:18 PM To: [EMAIL PROTECTED] Subject: How to save volhist and devconfig Hello, I was wondering how other administrators are saving the volhist, devconfig, dsmserv.dsk and dsmserv.opt. Every day we save the volhist and devconfig and manually ftp these files to a network-drive in case of a crash of the server. Now I'm not familiar with scripts so far, but I want to automate these job. So, I was wondering how other administrators are doing this job. Thanks for your reply. Brian. _________________________________________________________________ Chat on line met vrienden en probeer MSN Messenger uit: http://messenger.msn.nl
