Stefan, are your bacula catalog backups being made to a disk volume, as is default, or to a tape volume? If being made to a disk volume you could restore a catalog backup. If your catalog backups were being made to that same machine whose backups were purged, and you lost the database entries for the catalog backups, you can still run bscan against the catalog backups to do a restore.
By default, a database restore will purge all other entries in the database. So if you're going to make a restore of the bacula catalog you'll need to do it soon vs later OR maybe try to do some hybrid method where you restore entries partially later, but I have no knowledge of how to do that and I don't know how dangerous or foolish such a thing may be. I assume right now you aren't doing many or any backups because your tape drive is down (except for the backups made to disk that you're trying to purge/prune because you accidentally backed up data that's too big for your disk storage). However, once you start running more backups you increasingly accumulate more catalog data you don't want to lose. If catalog entries for volumes other than the disk volumes on your storage were lost (backups made to tape via that client), your system might attempt to automatically reuse tape volumes once your tape system is back online, thereby overwriting backups you'd want to keep. Maybe watch out for that. The data on your tape volumes is obviously still available, and worst case you could do a bscan operation against those volumes once tape drive is operational again. Would just have to be sure any impacted tapes aren't automatically overwritten. A bscan operation would definitely take a while, depending on how many tapes are impacted (if any). A catalog restore is almost certainly what you want to do, presuming there isn't a bunch of new catalog entries made after the accidental purge event. To manually remove the disk volumes, and associated job and file entries, do a delete operation. Easily done in Bacularis or baculum, (I haven't done it in bconsole though I'm sure it's doable there too). I would have a catalog backup restored BEFORE I performed the delete operation, and I would be very careful to select the correct volumes to delete. Running to a meeting, will check back later. Robert Gerber 402-237-8692 r...@craeon.net On Wed, May 15, 2024, 2:17 AM Stefan G. Weichinger <li...@xunil.at> wrote: > Am 08.05.24 um 13:13 schrieb Stefan G. Weichinger: > > > > I assume the drive has a problem. > > we used a new cleaning tape and a new LTO tape, btape still fails > > I tend to say this drive is defective > > Today the IT and the CEOs decide how to proceed. > > For now I created a temporary file-based storage on disk. > > As if it isn't dangerous enough right now I made a mistake: > > at first I had the huge veeam-files dumped to disk, I didn't want that. > So I tried to delete jobs or volumes in bacularis, but that didn't > remove the files on disk. > > googled and found some hint to "purge" ... now I purged all jobs from my > single client even the good ones :-( > > Now I have volumes on disk with no jobs in the DB. I re-run the valid > jobs right now, this creates new "virtual tapes" now, but I have to > (manually?) remove all those orphaned volumes to free space. > > > > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > 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
