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
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
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
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
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
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
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
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
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
