FYI, I was able to create a file on the remote machines. If anyone is
interested, the following link,
http://bacula.org/rel-manual/Tips_Suggestions.html#SECTION003820000000000000000,
will show you how to run a script to create a file on a remote machine. See
the section, "Executing Scripts on a Remote Machine" in the Tips and
Suggestions section of the documentation.
There is one error on that page. Where it says to run ssh -i Bacula_key -l
root "ls -la", it should be ssh -i Bacula_key -l root 192.168.1.1 "ls -la"
Mike Vasquez wrote:
I have read the documentation and it specifies that I can create a file
when the files are saved normally by doing the following in the file
daemon on the machine being backed up but no file is created.
Messages {
Name = Standard
director = nmc-sdca-mon1-dir = all, !skipped, !restored
file = /opt/bacula/working/status_bu = saved
}
What I want to be is to have the file daemon, if possible, create a file
in the working director when the backup has been completed.
Any ideas?
Mike
--
View this message in context: http://www.nabble.com/Messages-Directive-%28Create-File-job-is-completed%29-tf3916397.html#a11121228
Sent from the Bacula - Users mailing list archive at Nabble.com.
