That was it!! Got dsmc to startup. Now I have a new problem though. How do I setup the client to run the script before it queries the server for a schedule? It needs to start this script BEFORE being able to connect to the server. It needs to activate the VPN before it is even able to connect to the server. The pre/post schedule commands don't seem to run until you actually get a connection/schedule from the server.
While I could automate it w/ a cron job I'd rather have the dsmc daemon completely control backup so I can control the daemon from the TSM server. sim Prather, Wanda wrote: >The TSM linux client is unix-like. >PRESCHEDULECMD goes in the dsm.sys, not the dsm.opt. > >As a general rule, things that only root should be able to set, go in >dsm.sys. >Things that any user should be able to set for their own backup/restore >session, go in dsm.opt. > >
