[bareos-users] Re: ListenAddress/Bind bareos-fd to IP
You didn't google, did you? ;-) https://docs.bareos.org/Configuration/FileDaemon.html#config-Fd_Client_FdAddresses On Thursday, October 22, 2020 at 1:13:54 PM UTC+2 ballma...@gmail.com wrote: > Hi @all, > > im trying to bind the bareos-fd IP to a specific value. > > Default, bareos-fd open the port on 0.0.0.0:9102. > > How can i change these to a specific ip? > > br > micha > -- 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/d3ef8d37-41bf-45e9-acc1-88f1b9e5bf12n%40googlegroups.com.
[bareos-users] Re: Autchanger Script fails
Bareos uses a script called mtx-changer (probably located in /usr/lib/bareos/scripts) which in turn calls mtx. You can check mtx-changer log (/var/log/bareos/mtx.log) and/or try to manually run mtx manually to see if mtx itself runs ok. On Sunday, February 21, 2021 at 6:38:31 PM UTC+1 tilmang...@googlemail.com wrote: > Dear all, > > I have ADIC DDS Tape library which no longer cleaner removes the tape from > the library. When I issue an umount command, I get an error message. With > an older version of bareos, it used to work. Any advice on how I can debug > and fix this? > > > umount storage=TapeStorage1 > Automatically selected Catalog: QtronCatalog > Using Catalog "QtronCatalog" > Connecting to Storage daemon TapeStorage1 at qtron.fritz.box:9103 ... > 3307 Issuing autochanger "unload slot 8, drive 0" command. > 3995 Bad autochanger "unload slot 8, drive 0": ERR=Child died from signal > 15: Termination > Results=Program killed by BAREOS (timeout) > > 3002 Device ""TapeDrive1" (/dev/nst0)" unmounted > > Thanks > Tilman > -- 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/ca867db5-6f12-4282-bdb6-93820e7c6c69n%40googlegroups.com.
Re: [bareos-users] Long term archiving of cold data
I had a similar project once few years ago. I cannot post the detailed solution due to legal restrictions but I can describe the general idea. The situation was that a piece of software running on a server would create archive files in a given directory. Those files were to be archived in sufficiently many copies and then removed. So I did a full backup job with a fileset created dynamicaly using a script which would do a directory scan in the directory, then run a query against bareos catalog and only backup those files which: 1) Weren't backed up sufficiently many times and 2) Weren't backed up on this media yet. Apart from that I'd run a cron job completely asynchronously which would scan the directory and remove the files which had been already backed up enough times. This way I made sure that each archive file would get backed up on several different media and only after that it would get removed from the source server. In my case it was an all-in-one installation of bareos so I had easy access to both director database and FD directory contents. If you have those components separated you might need to do some access rights juggling of course. Of course you need to set the retention values to some ridiculously high periods in order to not get the files pruned from the database. Hope this helps On Thursday, July 8, 2021 at 5:50:47 PM UTC+2 Olivier Ardouin wrote: > Hi Frank, > > Thank you for this article, but it's not applicable in my case. > > I have only one client (for this Archive task) and my datas are, when > archived, frozen, just some new data to append from time to time. The total > volume of data (more than 34 tb now and still growing) is not compatible > with consolidation tasks (and only one drive in the autoloader). > In fact it could be done whithout bareos by a simple tar command and add > all the new folder to the tape manually. I may end with this solutions and > keep a track of which folders were in wich tape. Restore will be more > manual cause I will not be able to rely on the bareos catalog. I guess the > fonction should be in bareos in the pool type = Archive which is not yet > implemented in Bareos. > > A workaround may be to specified a file set for the "new" data do regular > full backup of this file set with 30 years retention time and a specific > "archive" pool, and move them automatically after the job in an "archived" > folder exclude from the file set. > > Did someone know if the Archive pool type will be implemented soon ? > > Thank's > > Le lundi 5 juillet 2021 à 13:50:24 UTC+2, frankbareos.com a écrit : > >> Bonjour Olivier, >> >> if I understand correctly this article (page 3) should help >> >> https://translate.google.com/translate?sl=auto&tl=fr&u=https://www.admin-magazin.de/Das-Heft/2020/02/Always-Incremental-mit-Bareos/%28offset%29/6 >> >> >> >> best, >> Frank >> >> -- 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/92dd375a-4cc5-4431-b736-7734a6b24d17n%40googlegroups.com.
[bareos-users] Re: Bareos backup switch to a new Server
Let's say that the upgrade proces is more or less independent from the move from one server to another. You can do the upgrade before moving the bareos installation or after - it's your call. The move is not that complicated as long as you know your configuration and know your database (don't forget about the database!). See the https://docs.bareos.org/Appendix/DisasterRecoveryUsingBareos.html#restoring-a-bareos-server Unfortunately, due to many possible variants of configuration (dir, sd, fd on the same machine or maybe sd on another one? single sd, multiple sd's? client-initiated connections? moving to another ip/hostname or scrapping old machine and reusing its network parameters? do you encrypt backups?), it's not easy to give a simple step by step scenario. The easiest situation would of course be if you wanted to do a switch "in-place" - then you'd probably mostly copy the bareos daemons' configuration, spool files, device files (if you're using file-based storage), database configuration and data and you'd be pretty much set. On Monday, April 4, 2022 at 11:18:13 PM UTC+2 u2mi...@gmail.com wrote: > hello guys > > i want to switch the current configuration to a new installed server > current installation is on ubuntu 20.04. desktop version: > bareos-dir Version: 20.0.1 (02 March 2021) Ubuntu 20.04.1 LTS ubuntu > Ubuntu 20.04.1 LTS > > here is the new output of version from bconsole: (on ubuntu 20.04. Server > version) > bareos-dir Version: 21.0.0 (21 December 2021) Ubuntu 20.04.3 LTS ubuntu > Ubuntu 20.04.3 LTS > > can i simple copy paste the configuration files (and adjust) or should i > upgrade the current installation before? > > any hints are welcome > > greetings michael > -- 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/67df00f2-aecd-442f-800f-ad89559a22c7n%40googlegroups.com.
[bareos-users] Re: Perform backups of computers that do not turn on systematically
Two things: 1) Client-initiated connections 2) Run On Incoming Connect Interval = within the job definition And you're good to go. If your laptop or whatever powers up, connects to bareos server and it notices that last backup job was more than predefined time ago, it starts new backup job. On Thursday, May 19, 2022 at 9:11:38 PM UTC+2 khva...@ukr.net wrote: > Bareos does a great job of backing up servers (computers that are always > on). Is there a way to backup computers that are not turned on > systematically, but before performing a backup, check its availability on > the local network, or is there another way? -- 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/66d5fbe6-bc9e-4619-b242-aedd306e8c10n%40googlegroups.com.
[bareos-users] Force diff/inc backups on the same vchanger device as full
I'm sure I'm not the first to think about it but I don't even have a good idea how to look for any earlier questions. I have an SD server which uses vchanger. In my case it's configured along with automounter so I can simply replace a disk and I have fresh batch of file devices (I don't create device per job, I have pre-created static-sized device files). Nothing fancy. But since I'm swapping the entire disk at once in case it fails I lose all jobs stored on this disk. Which means that if I did a full backup on disk A then swapped for disk B and did diffs or incrementals there and the disk A crashed, I lose the ability to restore the machine. The question is how to make sure in my setup that I don't end up with incrementals or diffs requiring full from another storage unit. That would mean that I need to contain full+inc/diff on the same disk. Should I fiddle with creating separate pools and somehowtry to rotate them? (like create separate job set for separate media pool for each week and just repeat them each X weeks where X is number of disks in rotation, assuming that I do a full every week). Or any better ideas? -- 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/9caeccad-f580-44ef-bf0a-8b621ef50069n%40googlegroups.com.
[bareos-users] Windows "portable" version of FD?
As a followup of my earlier ideas about restoring a windows system I tried today launching bareos-fd off of WinPE environment. Generally - it seem to be working relatively OK (haven't tried full restore yet though). But for now the only way to get a windows FD to such WinPE instance is to simply copy over c:\Program Files\Bareos from an existing installation. It's not a very pretty solution since I have to firstly install it somewhere. I cannot find any option in the installer to just unpack the installation package without running all the associated magic (like registering the service, creating configs and so on). Am I missing something? MK -- 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/a7e98b20-a361-4d51-941d-e75fee6634e5n%40googlegroups.com.
Re: [bareos-users] VSS ERR=The process cannot access the file because it is being used by another process
OK. There is more to this than just bareos. 1. I used the script from this thread and it seems to be working relatively well for backing up (I'm yet to test the restore part ;-)) the disk. I don't know, however how to backup whole mountpoint. If I put the location of my symlink/junction/whatever that is, only the junction point itself gets backed up, not the contents. I can't make bareos descend into the mounted VSS shadow copy. I have to explicitly list directories (like c:/vssmount/c/users) to back them up. 2. I spent whole evening yesterday trying to get vss to work, regardless of bareos. I tried creating snapshots with " shadowcopy call create Volume=C:\" and then symlinking them by hand and each time I did them I was also getting access denied due to file open. So there must be something else that the script provided in this thread does and neither bareos nor manual wmic call do. (My system here is Win10) MK On Friday, April 28, 2023 at 3:33:36 PM UTC+2 jo.go...@hosted-power.com wrote: > We have simuilar issues, it seems for some servers a lot is skipped. We > would really like to get to the root cause > > On Wednesday, 21 December 2022 at 04:19:35 UTC+1 Matt Bader wrote: > >> Hi Timo and Andreas, >> >> I'd be interested to know how to handle this issue as well - it's >> happening to a number of my FDs too. Did you figure out how to get VSS to >> work on all files? >> >> Thanks and regards, >> >> Matt >> >> On Friday, February 11, 2022 at 6:21:59 PM UTC+1 zehnb...@gmail.com >> wrote: >> >>> Hey Andreas, >>> >>> Windows Server Backup is working. >>> >>> Those 3 files are just files to demonstrate that somehow the bareos-vss >>> is not working. Like i already mentioned, as a workaround i can create a >>> vss with a powershell-script and ClientRunBeforeJob, then backup and >>> remove the vss with ClientRunAfterJob again. Also using restic, for >>> example, is working like a charm. >>> >>> Best, >>> Timo >>> >>> Andreas Rogge schrieb am Donnerstag, 10. Februar 2022 um 20:30:54 UTC+1: >>> Am 07.02.22 um 08:20 schrieb Vorname Nachname: > Any suggestions? Check if the integrated Windows Server Backup works or not. Are you backing up only these three files, or are the other files where the backup works? Best Regards, Andreas -- Andreas Rogge andrea...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp 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/56334b0f-cabd-4570-8e4d-c7ba70b8dfc7n%40googlegroups.com.
[bareos-users] Delay job on incoming connect?
Hi.
Is there a possibiliry to delay a job from a passive client?
I have a job defined simply like this:
Job {
Name = "laptop"
JobDefs = "DefaultJob"
Schedule= "EarlyWeeklyCycle"
Fileset = "LinuxDocs"
Client = "laptop-fd"
Priority = 5
Run On Incoming Connect Interval = 12h
}
The client here has "connection from client to director=yes"
It's as simple as it gets.
And it works pretty good. The problem is that by default the laptop
connects to wifi on power on and while it's OK for most times, sometimes
(especially when I want to do the full backup) I want to have it connected
with cable ethernet. The problem is that right after the power on the FD
starts, connects to the director and the backup job is spawned. And if I
switch my connection from the default wifi to cable, the job is left
hanging on both sides (FD and dir) and I have to restart both the FD and
director. It's not pretty.
I'm wondering if I can do something to make it all more robust.
MK
--
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/cb6b8767-f9bc-4802-b96a-7d6658140606n%40googlegroups.com.
[bareos-users] Force rotation of physical disks
Hello there.
I have a setup with vchanger serving 4 physical disks. On those disks I
have fixed-size media files.
It works as it should but it doesn't fulfill all my needs.
It does rotate between disks when a particular physical disk gets full (all
medias on that drive are used) but it might do so - for example - mid-job.
Back when I had shorter retention it didn't care that it didn't rotate
between disks for a longer time.
So ideally I'd love to have a situation when I'd have a full job and
subsequent diff/inc jobs created on one disk, then rotate to another
physical disk (the old one I unplug and store off-line) and do
full+diff/inc there and so on. For example in a weekly schedule.
But so far the only Idea I have would be to create a separate pool on each
physical disk and have multiple intertwined jobs - each with a week-long
schedule and multiple-week "pause". Each job would target a different pool.
The downside is of course the administrative overhead to create and
maintain all those jobs and having to reconfigure it as a whole in case I
add or remove disks to/from the rotation pool.
I just browsed the docs in parallel windows and I see that I can override
job-level settings with schedule so maybe it's the way to go. Create
separate pools per physical disk and do something like:
Schedule {
Name = "TriDisk"
Run = Pool=FirstDisk Full w01/w03 sat at 21:00
Run = Pool=SecondDisk Full w02/w03 sat at 21:00
Run = Pool=ThirdDisk Full w03/w03 sat at 21:00
Run = Pool=FirstDisk Incremental Full w01/w03 mon-fri at 21:00
Run = Pool=SecondDisk Incremental Full w02/w03 mon-fri at 21:00
Run = Pool=ThirdDisk Incremental Full w03/w03 mon-fri at 21:00
}
Still a bit troublesome to maintain but better than defining separate jobs.
Any better ideas?
MK
--
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 visit
https://groups.google.com/d/msgid/bareos-users/6f24e8f4-418c-4337-97b4-f18549864de2n%40googlegroups.com.
