I figured out part of the problem, it turned out there was no access from
fd to cd , and not as it was written in the logs from fd to dir. The task
started to run and is being executed, and after some time this task is
started again in a cycle, while the first one has not yet finished doing
its work and so it starts indefinitely. How to fix it? Version: 21.1.3
вторник, 24 мая 2022 г. в 23:59:52 UTC+3, khvalera:
> *In bareos-fd.service status appeared:*
>
> *bareos-fd[4127]: lib/bsock_tcp.cc:128 Unable to connect to backup-dir on
> 192.168.8.1:9101. ERR=Connection refused*
>
> *strange, access to port 192.168.8.1:9101 checked, everything should be
> fine.*
>
> вторник, 24 мая 2022 г. в 23:02:07 UTC+3, khvalera:
>
>> *Made the following config files:*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> */etc/bareos/bareos-fd.d/directorDirector { Name = backup-dir Password =
>> "******"Connection From Client To Director = yesAddress = 192.168.8.1}
>> /etc/bareos/bareos-dir.d/client-jobClient {Name = client-testAddress =
>> 10.10.22.90Password = "******"File Retention = 90 daysJob Retention = 30
>> daysAutoPrune = yesConnection From Client To Director = trueConnection From
>> Director To Client = noHeartbeat Interval = 60}Job {Name =
>> "backup-client-test"Client = "client-test"RunOnIncomingConnectInterval =
>> 12hJobDefs = "backup-client-linux-jobdefs"} *
>> *Job in progress:*
>>
>>
>>
>>
>>
>>
>>
>> *8 2022-05-24 22:19:16 backup-dir JobId 94: Encryption:
>> TLS_CHACHA20_POLY1305_SHA256 TLSv1.37 2022-05-24 22:19:16 backup-dir JobId
>> 94: Handshake: Immediate TLS6 2022-05-24 22:19:16 backup-dir JobId 94:
>> Using Client Initiated Connection (client-test).5 2022-05-24 22:19:16
>> backup-dir JobId 94: Probing client protocol... (result will be saved until
>> config reload)4 2022-05-24 22:19:16 backup-dir JobId 94: Using Device
>> "storage-gr-lvm" to write.3 2022-05-24 22:19:16 backup-dir JobId 94: Start
>> Backup JobId 94, Job=backup-client-test.2022-05-24_22.19.13_172 2022-05-24
>> 22:19:13 backup-dir JobId 94: No prior or suitable Full backup found in
>> catalog. Doing FULL backup.1 2022-05-24 22:19:13 backup-dir JobId 94: No
>> prior Full backup Job record found.*
>>
>> *this task hangs in this state, and after a while dobles of this task
>> appear in cycles. What could I be missing?*
>>
>> пятница, 20 мая 2022 г. в 10:25:55 UTC+3, spadaj...@gmail.com:
>>
>>> Two things:
>>>
>>> 1) Client-initiated connections
>>>
>>> 2) Run On Incoming Connect Interval = <some 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/bdf0f6ea-5bd8-4928-a14a-94a39badb980n%40googlegroups.com.
