Re: [Bacula-users] Volume media failure, howto configure migration job?

2019-12-31 Thread Martin Simmons
> On Mon, 23 Dec 2019 19:27:59 -0200 (BRST), Heitor Faria said: > > Hello John, > > > `Termination:Migration -- no files to migrate` > > > > so something is still not right... > > Despite you did not post the full job output, I suspect the Migrate job found > no JobIds to

Re: [Bacula-users] Volume media failure, howto configure migration job?

2019-12-23 Thread Heitor Faria
Hello John, > `Termination:Migration -- no files to migrate` > > so something is still not right... Despite you did not post the full job output, I suspect the Migrate job found no JobIds to migrate. The Selection Pattern value should be a RegExp, not a Wildcard, as stated in the

Re: [Bacula-users] Volume media failure, howto configure migration job?

2019-12-23 Thread John H Nyhuis
hmmm, this ends with `Termination:Migration -- no files to migrate` so something is still not right... Thanks, John H. Nyhuis Desk: (206)-685-8334 jnyh...@uw.edu Box 359461, 15th floor, 106 On 12/23/2019 12:07 PM, Heitor Faria wrote: > Hello John, > >> In writing this job

Re: [Bacula-users] Volume media failure, howto configure migration job?

2019-12-23 Thread John H Nyhuis
Ok, so I have adjusted by job block to this: Job { Name = Migrate-07 Type = Migrate Client = bock Messages = Daemon FileSet = GCC_archive-Genomic_Coverage-fileset Level = Full Pool = lto6-pool Max Run Time = 8035200 Spool Attributes = yes Selection Type =

Re: [Bacula-users] Volume media failure, howto configure migration job?

2019-12-23 Thread Heitor Faria
Hello John, > In writing this job definition, there are several problems: > > 1. There is not a single fileset involved, but apparently a single > fileset must be specified... (Or can I specify volume 07L6 as the > fileset in some way)? The FileSet specification is obligatory for most

[Bacula-users] Volume media failure, howto configure migration job?

2019-12-23 Thread John H Nyhuis
Over the weekend, volume barcode 07L6 failed and has been marked as as sev 2 (high) failure by our Quantum Scalar i40 library. To resolve this issue, the library requires that the data on this volume be migrated to a different volume that is not failing, then I need to proceed with