by the addition of {\bf ClientRunBeforJob} and {\bf ClientRunAfterJob} Job
records, but the technique still could be useful.) First I thought the "Run
Before Job" statement in the Job-resource is for executing a script on the
-remote machine(the machine to be backed up). It could be useful to execute
+remote machine (the machine to be backed up). (Note, this is possible as mentioned
+above by using {\bf ClientRunBeforJob} and {\bf ClientRunAfterJob}).
+It could be useful to execute
scripts on the remote machine e.g. for stopping databases or other services
while doing the backup. (Of course I have to start the services again when the
backup has finished) I found the following solution: Bacula could execute
\footnotesize
\begin{verbatim}
-ssh -i Bacula_key -l root "ls -la"
+ssh -i Bacula_key -l root <machine-name-or-ip-address> "ls -la"
\end{verbatim}
\normalsize
\end{verbatim}
\normalsize
-Even though Bacula version 1.32 has a ClientRunBeforeJob, the ssh method still
+Even though Bacula version 1.32 and later has a ClientRunBeforeJob, the ssh method still
could be useful for updating all the Bacula clients on several remote machines
in a single script.