I found the simplest way was to delete the relevant pools using bconsole. This removes all the associated volumes from the catalog as well.
Best -Chris- > On 31 Jan 2021, at 22:07, Christian Lehmann <lcompu...@t-online.de> wrote: > > Dear Chris, > > maybe it’s just enough to mark the volumes no longer available as “Error” or > n appropriate status by update à volume parameters > > I would guess this should be a good way. On the other hand, after dropping > the database entirely, you may re-read all the other volumes and include them > into your newly generated database again. > > But maybe the power users have different ideas… > > Best, > > Christian > > > Von: Chris Wilkinson <winstonia...@gmail.com> > Gesendet: Sonntag, 31. Januar 2021 22:43 > An: Timo Neuvonen <timo-n...@tee-en.net> > Cc: bacula-users <bacula-users@lists.sourceforge.net> > Betreff: Re: [Bacula-users] How to reset catalog after backup drive failed? > > On second thoughts, I will need another solution since dropping the database > entirely would also wipe the records for a second NAS that stores backups for > another set of jobs. I’d rather not lose that backup set if possible. > > Best > -Chris- > > > > > >> On 31 Jan 2021, at 14:52, Chris Wilkinson <winstonia...@gmail.com >> <mailto:winstonia...@gmail.com>> wrote: >> >> Yes, that seems a good plan. There are such scripts in the /etc/bacula >> folder. >> >> Many thanks >> Chris Wilkinson >> >> On Sun, 31 Jan 2021, 2:10 pm Timo Neuvonen, <timo-n...@tee-en.net >> <mailto:timo-n...@tee-en.net>> wrote: >>> > I backup to a NAS drive which has failed this morning. >>> > I can replace the drive and rerun the jobs with the existing resource >>> > defs >>> > but wonder how I should I reset the catalog since all those volumes are >>> > now lost but are still in the database. >>> > >>> > One option is perhaps to delete all the volumes using Baculum. Would that >>> > work, is there a better way ? >>> >>> I think somewhere in the directory tree there's a script >>> "drop_bacula_tables", and probably also "create_bacula_tables". >>> >>> I haven't used them for more than a decade, but I think manual mentions >>> them >>> (in addition to classic tarball install) in some beginners guide, so you >>> could drop all the traces of initial error-and-trial experiments before >>> switching to "production use". >>> >>> >>> Of course, you'd better to consider first if there might ever be any >>> conflict caused by the same job numbers etc. again. For example, if you >>> have >>> an archieve of old bootstrap files, you'd better to get rid of those files >>> too at the same time so they won't confuse you in the future. >>> >>> -- >>> TiN >>> >>> >>> >>> >>> _______________________________________________ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> <mailto:Bacula-users@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >>> <https://lists.sourceforge.net/lists/listinfo/bacula-users>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
