Re: [Bacula-users] SQL query for copy jobs

Thanks for looking at this.

I am a bit redfaced right now, because it looks like I have to withdraw the question. When I used "bat" to view the Jobs Run, and clicked "Filter Copy Jobs", a lot of the confusing stuff was removed, and I could see that the dates actually had a monotonically increasing progression. Which means that, in fact, I wasn't getting duplicate jobs copied and the ones I thought hadn't been copied actually were.

To check if a job was already copied you have to verify priorjobid column in job table. The original job will have a priorjobid=0 and a copied job will have a priorjobid=<jobid> of the original.

Yes, that is exactly what the "ArchiveAll" job is counting on.

Your SQL is very weird to me. You copy jobs from pool File to the Pool File?

Sorry for the confusion there.

Pool {

Name = File

Pool Type = Backup

Recycle = yes # Bacula can automatically recycle Volumes

AutoPrune = yes # Prune expired volumes

Volume Retention = 90 days # 3 months

Maximum Volume Bytes = 50G # Limit Volume size to something reasonable

Maximum Volumes = 70 # Limit number of Volumes in Pool

Storage = BKUP

Next Pool = Archive # Where to copy/migrate to

}

The Pool definition for the File pool lists "Next Pool = Archive", so the copy jobs really were being written to the Archive pool.

Sorry for the noise everyone.

--Greg

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users