Hi,
How can I catch accurate data sent by Director to FD ?
This can help to understand where is a problem.

Oleg Volkov
T: +972-50-7601914
Skype: voleg4u , Viber, WhatsApp.


On Thu, 2 May 2019 at 15:15, <vole...@gmail.com> wrote:

> I've run FD in debug mode, like:
> # /usr/sbin/bareos-fd -d 99 -f -m > /tmp/debug 2>&1
>
> Inspecting resulting files, found that accurate.c do correct selection.
> It picks up 96 really changed files, summary about 100m.
>
> However, the resulting job shows:
>
> gibuy-dir JobId 22: Bareos gibuy-dir 18.2.5 (30Jan19):
> Build OS: Linux-4.4.92-6.18-default redhat CentOS Linux release 7.6.1810
> (Core)
> JobId: 22
> Job: fd-sle11sp4.2019-05-02_13.46.07_48
> Backup Level: Incremental, since=2019-05-01 22:10:09
> Client: "sle11sp4" 17.2.4 (21Sep17) x86_64-suse-linux-gnu,suse,SUSE Linux
> Enterprise Server 11 (x86_64),SLE_11_SP4,x86_64
> FileSet: "HANA-001" 2019-04-30 22:52:10
> Pool: "Incremental" (From command line)
> Catalog: "MyCatalog" (From Client resource)
> Storage: "File" (From Job resource)
> Scheduled time: 02-May-2019 13:46:07
> Start time: 02-May-2019 13:46:11
> End time: 02-May-2019 13:50:27
> Elapsed time: 4 mins 16 secs
> Priority: 10
> FD Files Written: 260
> SD Files Written: 260
> FD Bytes Written: 4,159,639,508 (4.159 GB)
> SD Bytes Written: 4,159,673,113 (4.159 GB)
> Rate: 16248.6 KB/s
> Software Compression: 87.7 % (gzip)
> VSS: no
> Encryption: no
> Accurate: yes
> Volume name(s): Incremental-0010
> Volume Session Id: 5
> Volume Session Time: 1556710222
> Last Volume Bytes: 4,163,353,822 (4.163 GB)
> Non-fatal FD errors: 0
> SD Errors: 0
> FD termination status: OK
> SD termination status: OK
> Bareos binary info: bareos.org build: Get official binaries and vendor
> support on bareos.com
> Termination: Backup OK
>
> Probably these "extra" files were not sent to FD with accurate data, then
> FD think they are missing and new, then should be backed up. May be they
> are sent by DIR, but because of different buffer sizes, just cutted of the
> accurate data.
>
> As in additional, this happens only in AlwaysInc mode, the classic
> Full-Diff-Inc works correct.
>
> Andreaas, Jorg, what you think ?
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "bareos-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/bareos-users/PMuqXDqUAWQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> bareos-users+unsubscr...@googlegroups.com.
> To post to this group, send email to bareos-users@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to bareos-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/CACWVf36t9Hewx_3a9kKac%3DKzUrxRn-B_F4CJmNfLtLLw%3DTq02g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to