On 9/20/10 8:03 AM, Yuri Timofeev wrote:
> Nobody knows? I also need this feature.
>
This is my solution for now.
I've got a JobDefs for my copy job:
JobDefs {
  Name = "CopyJob"
  Type = Copy
  Priority = 40 # after catalog
  Pool = Full-Pool # ignored when using SQLQuery
  Maximum Concurrent Jobs = 1
  Selection Type = SQLQuery
  Messages = Standard
 
  Level = Full # ignored
  Client = mn-server-fd # ignored
  FileSet="Standard Full Set" # ignored
}

Then each of my regular backup jobs have this RunScript section:
  RunScript {
    RunsOnClient = no
    RunsWhen = After
    FailJobOnError = yes
    Command  = "/etc/bacula/start-job mn-server-copy"
  }

Where the body of that script is:
#!/bin/sh

# run the copy job specified as $1

if [ $# -ne 1 ]; then
  echo "You must specify the name of the job to start"
  exit 1
fi

echo "run $1 yes" | /usr/sbin/bconsole
exit $?

And the corresponding copy job for each backup job is this:
Job {
  Name = "mn-server-copy"
  JobDefs = "CopyJob"
  Selection Pattern = "SELECT MAX(jobid) FROM Job WHERE Name = 'mn-server'"
  Write Bootstrap = "/var/lib/bacula/working/mn-server-copy.bsr"
}

-- 
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users