I have two AI jobs that have the same client and fileset but different pools (and storages, media types, etc.) Today I saw that when my consolidate job ran it picked up a list of job IDs to consolidate but ran them for the wrong job and thus tried to consolidate to a volume in the wrong pool. Could this be because the AccurateGetJobids function does not consider the job?
https://github.com/bareos/bareos/blob/7b4067ecb525c6fc1b26fe75794371a1ae8398a9/core/src/cats/sql_get.cc#L1355-L1368 I'd previously thought it was the combination of Job/FileSet/Client that defined uniqueness but the query for finding jobs to consolidate doesn't seem to consider the job. Josh -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/7d1fa06a-d961-43c9-a866-949f5bf276a0n%40googlegroups.com.
