Hello, śr., 19 cze 2024 o 08:27 Stefan G. Weichinger <li...@xunil.at> napisał(a):
> > I have an annoying issue that I don't yet understand > > I read the howtos around volumes and media type etc but so far couldn't > get it working: > > There are 2 storages "File" and "HP-Autoloader" ... so disk- and > tape-based backups. > > There are pools like "daily" "weekly" "monthly" that contain physical > tapes. > > "daily" and "weekly" have labels like "CMR123L6" (side question: I'd > like to configure that as well into the pools. What would be the > LabelFormat here?) > > "monthly" has "ARC123L6" > > and the file-based volumes get LabelFormat = "Vol-" > > The physical tapes use > > MediaType = "LTO-6" > > the disk-based virtual tapes use > > MediaType = "File" > > Now where´s the problem? > > It seems that the Job "BackupCatalog" (sometimes?) creates a new volume > like "Vol-252", but with MediaType "LTO-6", which is then NOT FOUND in > the tape autoloader. Sure, this one doesn't exist. "Vol-" volumes are > for storage "File" only. > Did you label your tapes? You can't use tapes in Bacula without labeling. When you label your tapes, just use "barcodes" options and Bacula will read all barcodes from tapes and label them to match. Then you should put all your new tapes in the Scratch pool during labeling, so Bacula can take one to the selected pool when required. Finally you should configure the "Recycle" pool parameter pointing to the Scratch pool, so all your unused tapes will return to it, closing the cycle. When carefully configured it will automatically rotate all your tapes, which is good for them. I hope it helps > addon: for weekly and monthly the catalog should run to the according > tapes, not to a "daily" tape, right? > The rule of thumb for the tape backups in Bacula is to use as few pools as possible. Especially for catalog backup which is technically redundant (unneeded, see below) and you save it for time saving only during recovery. If you have a single tape drive then you are limited to a single pool usage at any given time, and all your jobs which require another pool will wait. When your backup window is tight then you want to avoid this. I personally create tape pools based on required retention, i.e. Tape1W or Tape1M and join all the pools with similar retention time. > Somewhere I read the catalog should (additionally?) be written to File, > that would complicate it even more. > You should save your BSR file offsite in a secure place this will save a lot of your precious time during recovery. A file based volumes are easier to handle, a tape based volumes could be easier to handle for offsite storage. So, it all depends on your requirements and ability to fulfill them. *) your volumes archive all data required for future catalog recovery; this kind of recovery requires volume scan to populate catalog data, which can take time to complete; so, it is better and faster to save catalog backup to avoid volume scan. -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
