[bareos-users] Calculating Catalog- Files for Tape Archiving System
Hi,
I wonder how I might calculate the Nbr of Catalog-xxx files for the
following scenario:
Supposing I have a total of
- 20 Tapes à 6 TB where I would archive data during 10 years, archiving
from time to time, when it is necessary.
plus
- 20 Tapes à 6 TB where I would archive date during 2 years, then recycle.
The Catalog -xxx filesize is 500 mb
I don't want my stockage to grow to infinity, I want Bareos to do the
autopruning and recycling itself. But for my archiving I should therefore
know what information is useful for the volume-, job- and fileretention and
maybe also for the nbr of "Maximum Volumes".
Here is my actual Catalog.conf
Pool {
Name = Catalog
Pool Type = Backup
Recycle = yes
Maximum Volume Bytes = 500 G
Maximum Volumes =
Label Format = "Catalog-"
AutoPrune = yes
Volume Retention = 1095 days
Job Retention = 1094 days
File Retention = 1093 days
}
Any hint is appreciated.
Thank you very much!
Regards,
Birgit
--
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/d1ee8abf-101b-4ca9-aa84-728d4d9b35e6n%40googlegroups.com.
Re: [bareos-users] LTO-8 Tape Library bareos compatible?
Hi there, Finally I can confirm that the NEOs T24 LTO-8 works also in my case. Thank you for your feed-backs. Regards, Birgit DUCARROZ Birgit schrieb am Dienstag, 24. Oktober 2023 um 13:34:30 UTC+2: > Hi Laurent, > > Thank you for your response. I would be interested how you used the > barcode feature, but this is maybe not a topic for this bareos forum. > > Kind regards, > Birgit > -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/4a0bb26a-d6e1-4d48-a511-d5dc72c12220n%40googlegroups.com.
Re: [bareos-users] LTO-8 Tape Library bareos compatible?
Dears Philippe and Brock Palen, Thank you so much for your answers (private or public response). This helps me a lot to decide. At this place I want also say that I never ever had bigger problems with bareos: once configuret correctly it is working fine, it is just a great software ! Kind regards, Birgit Philipp Storz schrieb am Samstag, 21. Oktober 2023 um 12:11:13 UTC+2: > Hello Brigit, > > as both the scsi tape and the scsi changer protocols have not changed > since more than 20 years, > I am very sure that it will work with Bareos without problems. > > I do not know of a single case where a SCSI (fibre-channel, sas)-based > tape changer did not work > with Bareos. > > If the changer is supported on Linux (i.e. you can use "tar" to write to > the tape, and use "mtx" to > control the robot) it works. > > You also can ask your vendor to guarantee it, so you can return it if it > does not work :) > > Am 20.10.23 um 15:39 schrieb 'Birgit Ducarroz' via bareos-users: > > Hi there, > > > > Does someone know if *... > > * > > * > > * > > Tandberg Data Tape Library OV-NEO2u83Y NEOs T24 LTO-8 > > > > ... is compatible out of the box with bareos? (Maybe someone is using > this Tape Library)? > > Datasheet: > > https://cdn.competec.ch//documents2/0/3/6/218024630/218024630.pdf > > > > Thank you for any hint. > > Regards, > > Birgit > > > > -- > > 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 > > bareos-users...@googlegroups.com bareos-users...@googlegroups.com>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/bareos-users/17908d71-87e7-417f-b923-1bc1a877f138n%40googlegroups.com > > < > https://groups.google.com/d/msgid/bareos-users/17908d71-87e7-417f-b923-1bc1a877f138n%40googlegroups.com?utm_medium=email&utm_source=footer > >. > > -- > Mit freundlichen Grüßen > > Philipp Storz philip...@bareos.com > Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92 <+49%20221%2063069392> > http://www.bareos.com Fax: +49 221 63 06 93-10 <+49%20221%2063069310> > > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz > > -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/7f4c5884-3c5f-492f-b46f-d7d6cd724fc9n%40googlegroups.com.
[bareos-users] LTO-8 Tape Library bareos compatible?
Hi there, Does someone know if *... * Tandberg Data Tape Library OV-NEO2u83Y NEOs T24 LTO-8 ... is compatible out of the box with bareos? (Maybe someone is using this Tape Library)? Datasheet: https://cdn.competec.ch//documents2/0/3/6/218024630/218024630.pdf Thank you for any hint. Regards, Birgit -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/17908d71-87e7-417f-b923-1bc1a877f138n%40googlegroups.com.
Re: [bareos-users] Re: Error running program when updating bootstrap file
Hi Philipp and Bruno, Thank you for your answers and sorry for the late reply. Bareos sends me all the mails, but no mail with .bsr messages. And yes, I backup my bsr files on a third share, I always did. For me the problem is solved although I do not know why I get no email with the bsr information. BTW, since I use bareos (version 18) : It works perfectly :-) Best regards, Birgit Bruno Friedmann schrieb am Dienstag, 20. Juni 2023 um 17:51:43 UTC+2: > Mainly if you have a working message resource configuration, then you can > almost copy and paste it to the Write Bootstrap line. > The syntax you had use let think to Bareos to write a file, and no more > running a shell command. > > The other way is to store the bsr somewhere else (like other job bsr for > example) you know you will be able to grab in case of disaster recovery. > > On Tuesday, June 20, 2023 at 12:34:09 PM UTC+2 Philipp Storz wrote: > >> Am 20.06.23 um 12:09 schrieb 'Birgit Ducarroz' via bareos-users: >> > Hi Philipp, >> > >> > Thank you for your response. I changed the bsmtp call into >> > Write Bootstrap = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s >> \"Bootstrap for Job %j\" root" >> > But then I get the following error: >> > Error: Could not open WriteBootstrap file: >> > /usr/bin/bsmtp -h root@localhost -f: ERR=Permission denied >> > >> > However, the file bareos.sql has been written into the directory. >> According to >> > https://bugs.bareos.org/view.php?id=587 >> > list jobs shows me a T and successfull terminated. >> > >> > Enter a period (.) to cancel a command. >> > *list joblog >> > Automatically selected Catalog: MyCatalog >> > Using Catalog "MyCatalog" >> > You have messages. >> > *list jobs >> > >> +---+--+---+-+--+--+---+--++---+ >> >> >> > | jobid | name | client| starttime | duration >> | type | level | jobfiles | >> > jobbytes | jobstatus | >> > >> +---+--+---+-+--+--+---+--++---+ >> >> >> > | 1 | BackupCatalog| bareos-fd | 2023-06-20 11:01:37 | 00:00:01 >> | B| F |3,275 | >> > 24,520,303 | T | >> > >> +---+--+---+-+--+--+---+--++--- >> >> >> > >> > If I comment out Write Bootstrap = "/usr/bin/bsmtp -h localhost -f >> \"\(Bareos\) \" -s \"Bootstrap >> > for Job %j\" root" >> > No errors anymore, but I think it is not the aim to ignore the return >> value ... >> > >> > I'm a bit confused about the permission denied error, since the job >> returns a success and the file >> > has been written. Any ideas? >> The bootstrap file should be sent via email, not the sql dump (which is >> much too large probably). >> >> What you can try is to find a working bsmtp call on your machine by >> echoing some text into bsmtp to >> check what the error might be, like >> >> echo "hello" | /usr/bin/bsmtp -h localhost ... >> >> >> > >> > Philipp Storz schrieb am Montag, 19. Juni 2023 um 12:36:13 UTC+2: >> > >> > Hello Birgit, >> > >> > this error is caused by the changes introduced with PR 1296: >> > https://github.com/bareos/bareos/pull/1296 < >> https://github.com/bareos/bareos/pull/1296> >> > >> > The old behaviour was to ignore the return value of the program that >> the bootstrap was sent to, now >> > bareos checks for the return value. >> > >> > So to solve your problem you need to make sure that the bsmtp call is >> successful. >> > >> > Probably you can see the problem if you execute the command show >> manually. >> > >> > Best regards, >> > >> > Philipp >> > >> > >> > Am 19.06.23 um 12:21 schrieb 'DUCARROZ Birgit' via bareos-users: >> > > Hi, >> > > >> > > Please can someone help me with this error? >> > > I installed a brand new bareos 22 >> > > Build OS: Ubuntu 22.04.1 LTS >> > > >> > > In the webGUI the job is marked ass success - green &
[bareos-users] Re: Error running program when updating bootstrap file
Hi Philipp, Thank you for your response. I changed the bsmtp call into Write Bootstrap = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s \"Bootstrap for Job %j\" root" But then I get the following error: Error: Could not open WriteBootstrap file: /usr/bin/bsmtp -h root@localhost -f: ERR=Permission denied However, the file bareos.sql has been written into the directory. According to https://bugs.bareos.org/view.php?id=587 list jobs shows me a T and successfull terminated. Enter a period (.) to cancel a command. *list joblog Automatically selected Catalog: MyCatalog Using Catalog "MyCatalog" You have messages. *list jobs +---+--+---+-+--+--+---+--++---+ | jobid | name | client| starttime | duration | type | level | jobfiles | jobbytes | jobstatus | +---+--+---+-+--+--+---+--++---+ | 1 | BackupCatalog| bareos-fd | 2023-06-20 11:01:37 | 00:00:01 | B | F |3,275 | 24,520,303 | T | +---+--+---+-+--+--+---+--++--- If I comment out Write Bootstrap = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s \"Bootstrap for Job %j\" root" No errors anymore, but I think it is not the aim to ignore the return value ... I'm a bit confused about the permission denied error, since the job returns a success and the file has been written. Any ideas? Philipp Storz schrieb am Montag, 19. Juni 2023 um 12:36:13 UTC+2: > Hello Birgit, > > this error is caused by the changes introduced with PR 1296: > https://github.com/bareos/bareos/pull/1296 > > The old behaviour was to ignore the return value of the program that the > bootstrap was sent to, now > bareos checks for the return value. > > So to solve your problem you need to make sure that the bsmtp call is > successful. > > Probably you can see the problem if you execute the command show manually. > > Best regards, > > Philipp > > > Am 19.06.23 um 12:21 schrieb 'DUCARROZ Birgit' via bareos-users: > > Hi, > > > > Please can someone help me with this error? > > I installed a brand new bareos 22 > > Build OS: Ubuntu 22.04.1 LTS > > > > In the webGUI the job is marked ass success - green > > > > It happens with the Catalog Backup. The bareos-fd backup shows no errors > > > > bareos-dir JobId 2: Error: Error running program when updating bootstrap > file: |/usr/bin/bsmtp -h > > localhost -f "(Bareos) " -s "Bootstrap for Job > BackupCatalog.2023-06-19_12.02.07_09" root: ERR=Child > > exited with code 1 > > > > Thank you a lot! > > Regards, > > Birgit > > > > -- > Mit freundlichen Grüßen > > Philipp Storz philip...@bareos.com > Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92 <+49%20221%2063069392> > http://www.bareos.com Fax: +49 221 63 06 93-10 <+49%20221%2063069310> > > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz > > -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/1ad86ead-ab1c-4e27-a4ff-44c4a41d8d1bn%40googlegroups.com.
[bareos-users] bareos-webui Ubuntu 22.04 php script showed instead of login page
Hi,
I just installed a brand new Ubuntu 22.04 with the latest Bareos Version
and the webui.
Depending my browser, It shows this:
. * */ if(isset($_SERVER['APPLICATION_ENV']) && $_SERVER['APPLICATION_ENV']
== 'development') { error_reporting(E_ALL); ini_set("display_errors", 1);
define('REQUEST_MICROTIME', microtime(true)); } /** * This makes our life
easier when dealing with paths. Everything is relative * to the application
root now. */ chdir(dirname(__DIR__)); // Decline static file requests back
to the PHP built-in webserver if (php_sapi_name() === 'cli-server' &&
is_file(__DIR__ . parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH))) {
return false; } // Setup autoloading require 'init_autoloader.php'; // Run
the application! Zend\Mvc\Application::init(require
'config/application.config.php')->run();
or this:
https://github.com/bareos/bareos for the canonical source repository *
@copyright Copyright (c) 2013-2019 Bareos GmbH & Co. KG
(http://www.bareos.org/) * @license GNU Affero General Public License
(http://www.gnu.org/licenses/) * * This program is free software: you can
redistribute it and/or modify * it under the terms of the GNU Affero
General Public License as published by * the Free Software Foundation,
either version 3 of the License, or * (at your option) any later version. *
* This program is distributed in the hope that it will be useful, * but
WITHOUT ANY WARRANTY; without even the implied warranty of *
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Affero
General Public License for more details. * * You should have received a
copy of the GNU Affero General Public License * along with this program. If
not, see
[bareos-users] Dependency failed for Bareos File Daemon service
Hi list, The bareos-filedaemon.service of one of my ubuntu 18.04 clients stopped to work after a regular security update and restart of the Ubuntu client. I tried to start it again, but it returns the following error: Dependency failed for Bareos File Daemon service So I purged and removed the bareos services on the machine with the command: apt-get --purge remove Now, when trying to re-install it, I run into the following error: bareos-filedaemon.service: Job bareos-filedaemon.service/start failed with result 'dependency'. ... dpkg --configure -a and apt-get install -f did not solve the problem. Any ideas which dependency this might be? Thank you so much. Regards, Birgit -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/9de7e2f0-5a52-4b6c-9df7-602a36d4c26cn%40googlegroups.com.
Re: [bareos-users] Do Not Try to Run Duplicated Jobs
Hi Jon,
First of all, sorry for my late answer.
This is working like a charm, thank you a lot!!
Regards,
Birgit
Jon Schewe schrieb am Dienstag, 9. November 2021 um 17:21:31 UTC+1:
> The handling of canceled jobs in bareos has caused me some issues,
> particularly because a canceled job is not considered success, so if you
> have rerun failed levels enabled you can end up running the same level over
> and over. My solution here deals with that by deleting the canceled jobs,
> which is what you want.
>
>
> /etc/bareos/bareos-dir.d/jobdefs/LTO-Backup.conf
> JobDefs {
> Name = "LTO-Backup"
> Type = Backup
> Level = Incremental
> Schedule = "WeeklyCycle"
> Messages = Standard
> Pool = LTO-5
> Priority = 30
> Rerun Failed Levels = yes
> Accurate = yes
> Spool Data = yes
>
> # retry failed backups
> Reschedule On Error = yes
> Reschedule Interval = 1 minute
> Reschedule Times = 10
>
> #Write Bootstrap = "|/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s
> \"Bootstrap for Job %j\" root@localhost" # (#01)
> Write Bootstrap = /var/lib/bareos/bootstrap/%c.bsr
>
> AllowDuplicateJobs = no
> CancelLowerLevelDuplicates = yes
> CancelQueuedDuplicates = yes
>
> # handle long running jobs and canceling duplicates
> RunScript {
> RunsWhen = After
> RunsOnFailure = Yes
> FailJobOnError = No
> RunsOnClient = No
> Command = "/etc/bareos/delete-canceled-job.sh %e %i"
> }
>
> }
>
>
>
> /etc/bareos/delete-canceled-job.sh
> #!/bin/sh
>
> debug() { ! "${log_debug-false}" || log "DEBUG: $*" >&2; }
> log() { printf '%s\n' "$*"; }
> warn() { log "WARNING: $*" >&2; }
> error() { log "ERROR: $*" >&2; }
> fatal() { error "$*"; exit 1; }
> try() { "$@" || fatal "'$@' failed"; }
>
> mydir=$(cd "$(dirname "$0")" && pwd -L) || fatal "Unable to determine
> script directory"
>
> # call as delete-canceled-job.sh %e %i
> status=$1
> jobid=$2
>
> if [ "Canceled" = "${status}" ]; then
> log "Deleting canceled job ${jobid}"
> #echo "Run 'delete jobid=${jobid}' inside bareos console" | mail -s
> "delete canceled" jon.s...@raytheon.com
> #echo "delete jobid=${jobid} | bconsole"
>
> # schedule with at so that the job can complete and then later be
> deleted
> echo "/etc/bareos/delete-canceled-job_doit.sh ${jobid}" | at now + 2
> minutes
> fi
>
>
>
> /etc/bareos/delete-canceled-job_doit.sh
> #!/bin/sh
>
> debug() { ! "${log_debug-false}" || log "DEBUG: $*" >&2; }
> log() { printf '%s\n' "$*"; }
> warn() { log "WARNING: $*" >&2; }
> error() { log "ERROR: $*" >&2; }
> fatal() { error "$*"; exit 1; }
> try() { "$@" || fatal "'$@' failed"; }
>
> mydir=$(cd "$(dirname "$0")" && pwd -L) || fatal "Unable to determine
> script directory"
>
> # called from at, scheduled by delete-canaceled-job.sh
> jobid=$1
>
> debug "Deleting canceled job ${jobid}"
> #echo "Run 'delete jobid=${jobid}' inside bareos console" | mail -s
> "delete canceled" jon.s...@raytheon.com
>
> output=$(echo "delete jobid=${jobid}" | bconsole 2>&1)
> if [ $? -ne 0 ]; then
> error ${output}
> fatal "Error deleting job ${jobid}"
> fi
>
> # output anything that we don't expect
> echo "${output}" \
> | grep -v "Automatically selected Catalog" \
> | grep -v "Using Catalog" \
> | grep -v "You have messages" \
> | grep -v "deleted from the catalog" \
> | grep -v "delete jobid=${jobid}" \
> | grep -v "Enter a period" \
> | grep -v "You are connected using" \
> | grep -v "Get official binaries and vendor support" \
> | grep -v "bareos.org binaries are UNSUPPORTED by bareos.com" \
> | grep -v "bareos.org build binary" \
> | grep -v "1000 OK" \
> | grep -v "Encryption:" \
> | grep -v "Connecting to Director" \
> | grep -v -e '^[[:space:]]*$'
>
> # debugging
> #echo "delete jobid=${jobid}" \
> #| bconsole 2>&1
> #log "
[bareos-users] Do Not Try to Run Duplicated Jobs
Hi list, Is there a possibility to not run and then cancel duplicated jobs? In my actual config... Allow Duplicate Jobs = no Cancel Lower Level Duplicates = yes Cancel Queued Duplicates = yes ... duplicate jobs cancel which creates me a lot of canceled jobs in the dashboard while running a set of full backups which are running more than one day. But I even don't want to list all these canceled jobs. Thank you for any hint! Kind regards, Birgit -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/46d2bc51-b789-47bc-a328-4b2386e98fd3n%40googlegroups.com.
