I have this working now. The script is below, as per Bill's script with an
extention. It is called from a Runscript as "Command =
/full-path/run-copy-job.sh copy-job-name". There is a copy job defined for
each backup job. The $1 parameter passes the copy job name to the script.
#!/bin/bash
#usage
On 4/9/24 6:53 AM, Chris Wilkinson wrote:
Regarding the suggestion to put a Runafter block in the job to run the copy job at the end, that doesn't seem to be allowed.
Run job=xx commands are not permitted in a Runscript as I just found out. It gives a not allowed command error.
Perhaps there is
Regarding the suggestion to put a Runafter block in the job to run the copy
job at the end, that doesn't seem to be allowed. Run job=xx commands are
not permitted in a Runscript as I just found out. It gives a not allowed
command error.
Perhaps there is another way to accomplish this?
-Chris-
On
Em 02/04/2024 19:58, Bill Arlofski via Bacula-users escreveu:
On 4/2/24 12:01 PM, Roberto Greiner wrote:
Hi,
I've installed Bacula recently in a server with a 7TB RAID5 storage, and
a LTO-6 tape unit.
I have configured 9 remote servers (most Linux, one Windows) to have the
backup made in this
On 4/2/24 12:01 PM, Roberto Greiner wrote:
Hi,
I've installed Bacula recently in a server with a 7TB RAID5 storage, and
a LTO-6 tape unit.
I have configured 9 remote servers (most Linux, one Windows) to have the
backup made in this server in the disk storage, and I'm finish to
understand how to
