Hi, Larry. The easiest way would be to use something like Autosys or Control_M to schedule the job dependencies and execute the batch/cmd and script files on the appropriate servers at the appropriate times.
If you don't want to use an independent scheduling package, it is fairly easy to install a ssh server on the Windows server. This is fairly easy with Cygwin/sshd. The UNIX script ssh's with rsa key authentication to the windows server to execute the batch/cmd scripts that stop and start the application. ________________________________ Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 ________________________________ Your Business. Better. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Larry Peifer Sent: Thursday, April 09, 2009 5:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] UNIX BA client trigger a Windows Server action What methods are available to have a UNIX BA client trigger the shutdown of a Windows server and start it back up again after finishing the backup. The windows server is running software the relies on an Oracle database and it does not handle the cold backup of the oracle database. The UNIX BA client is started via a cron job to shutdown the Oracle DB, start a TSM backup and wait for it to finish, and then start the Oracle database. Is there a way to add a step to the UNIX cron job to trigger the shutdown of the Windows server and know when it is down in order to go to the next step. The same type of trigger would be needed to start up the Windows server after the Oracle DB starts successfully following the TSM backup. This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.