On 8/30/17 9:27 AM, Julian Poß wrote: >> I suppose that bareos could scan the changer for tapes that don't have >> labels and then assume that it's supposed to use them and label them. >> However this turns into a configuration problem when changing out tapes. >> If you don't have labels on the front of your tapes and you want to pull >> one out for offsite storage how do you know which one is which? > Our tapes all have barcodes on the front, also our autochanger is able to > read them, so i will not run into any problem indentifying tapes. > >> Also how does bareos know which pool the tape should belong to? That >> kind of management is something that usually requires a human in the loop. > I expected bareos to label a tape, based on the job running behind it. > For example, if i am running a full backup job to tape, bareos should be able > to identify an unused tape (or an appendable tape) to store the backup onto. > The next day, the incremental backup will run, so now bareos should be able > to identify an unused tape again and assign it to the incremental pool. > I would be able to tell what tapes were used by bareos, based on the > volumenames created in bareos, since the names would match the barcode. > > After reading your answer, am guessing i need to add a new pool, maybe > something as simply as "tape", where i can assign all tapes to. > Afterwards bareos will be able to write all its job data onto the tapes and > just keeps appending, instead of splitting the tapes into seperate pools. > > Just thinking about it makes me believe, this will be the best solution. > What do you think? Yes, you should have 1 pool that contains all of your tapes. When Bareos is starting a backup job it looks in the pool for a tape that is appendable or empty. You would only need a second pool if you wanted to treat some of the tapes differently, such as my offsite pool. >> I would expect you'd just need to label all tapes once and be done. >> That's how my setup works. I have a 16 tape changer with a cleaning tape >> in slot 16, so I have 15 data tapes. I loaded all of them, then ran >> "label barcodes" once. I then assigned the tapes to 2 pools; one for >> local backups and one for offsite backups. The first couple of times >> that I pulled my offsite tapes to rotate out I called "label barcodes" >> again with the new empty tapes. Then as the tapes that I've sent offsite >> get sent back to me I just put them in the changer, run "update slots" >> and bareos uses whatever tapes are in the changer. > Okay, so basicially i need to run "label barcodes" ten times in my setup and > i am done, got it! Thanks for clarification. > "label barecodes" will label all tapes in the changer at once, so you probably don't need to run it 10 times, unless you have enough tapes to fill your changer 10 times. >> Because I sometimes forget to run "update slots" after swapping tapes I >> have a cron job that runs daily to run "update slots". This ensures that >> bareos always knows what is in the changer. >> Unless you're buying a new batch of tapes each week, you should not need >> to run "label barcodes" much after the initial setup. > Very good idea! I will create a cronjob aswell. This is the command I use: echo "update slots" | bconsole > /dev/null
-- Research Scientist Raytheon BBN Technologies 5775 Wayzata Blvd, Ste 630 Saint Louis Park, MN, 55416 Office: 952-545-5720 -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
