On Tue, Dec 10, 2013 at 04:45:55PM +, Steven Hammond wrote:
> We back our servers to disk. We then follow up with a job to copy
> them to tape. The backup to disk uses compression. My question is
> this: When the COPY job runs, does it decompress the job on disk
> before sending it to th
We back our servers to disk. We then follow up with a job to copy them to
tape. The backup to disk uses compression. My question is this: When the COPY
job runs, does it decompress the job on disk before sending it to the tape or
does it just copy it straight to tape (which means the hardware
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 Job
Nobody knows? I also need this feature.
2010/8/2 Jon Schewe :
> I want to setup bacula so that when a job finishes (one that writes to
> disk) it then spawns a job that copies itself to tape. I know about
> PoolUncopiedJobs and I don't want to do that, as it can cause the same
> job to be queued
I want to setup bacula so that when a job finishes (one that writes to
disk) it then spawns a job that copies itself to tape. I know about
PoolUncopiedJobs and I don't want to do that, as it can cause the same
job to be queued multiple times and will pull all of my old backup jobs,
which I really