We managed to reproduce the issue.  As you already noted, the cause was the "connection from client to director" option.

This was fixed by https://github.com/bareos/bareos/pull/1665

The current next release ( https://download.bareos.org/next/ ) already contains the fix.   Let me know if you tried that version and the issue still persists!

Sincerly

Sebastian Sura

Am 18.01.24 um 19:53 schrieb Joshua Myles:
Interesting. We have a mix of client-initiated and not, and at a glance it looks like the only jobs that ever have warnings ("ERR=The process cannot access the file because it is being used by another process.") are the ones from clients with "Connection From Client To Director = yes". Seems like maybe there's a different code path used when that's enabled, and it hits a bug. Unfortunately we can't switch away from client-initiated for these, we've just been living with the warnings.

Josh

On Thursday, January 18, 2024 at 4:10:27 AM UTC-5 Spadajspadaj wrote:

    Yes. It does seem to be the cause.

    I switched the client connectivity to the "normal" mode (director
    to client) and the job completed OK and I had no problems
    accessing the registry file.

    MK

    On 18.01.2024 09:36, 'jo.go...@hosted-power.com' via bareos-users
    wrote:
    Coindidence or not, we also use Connection From Client to
    Director=yes

    Coindidence or not,  Another host which does not have this
    setting, has 0 errors!

    On Thursday 18 January 2024 at 09:14:17 UTC+1 Spadajspadaj wrote:

        Hi Sebastian.

        Thx for looking into it. This is the job log. Not much
        interesting stuff in there.

        The same thing (the jobid being zero in the trace log) was in
        the previous trace I attached excerpt from few days ago. But
        that one was from a different machine. That was a clean win10
        installation just for testing the FD, this one is my
        production setup. Anyway, one thing that can be relatively
        uncommon (but I don't see why it should affect anything about
        the job itself) is that I use passive clients (Connection
        From Client to Director=yes, Heartbeat Interval=60).

        MK

        *list joblog jobid=17062
        Automatically selected Catalog: PgCatalog
        Using Catalog "PgCatalog"
         2024-01-18 08:06:04 backup1-dir JobId 17062: Start Backup
        JobId 17062, Job=win10test-fd.2024-01-18_08.06.02_12
         2024-01-18 08:06:04 backup1-dir JobId 17062: Connected
        Storage daemon at backup1.local:9103, encryption:
        TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
         2024-01-18 08:06:04 backup1-dir JobId 17062: Encryption:
        TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
         2024-01-18 08:06:04 backup1-dir JobId 17062: Using Client
        Initiated Connection (dziura-fd).
         2024-01-18 08:06:04 backup1-dir JobId 17062: Handshake:
        Immediate TLS
         2024-01-18 08:06:04 backup1-dir JobId 17062: Encryption:
        TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
         2024-01-18 08:06:04 backup1-dir JobId 17062: Using Device
        "vchanger-1-0" to write.
         2024-01-18 08:06:03 dziura-fd JobId 17062: Created 27
        wildcard excludes from FilesNotToBackup Registry key
         2024-01-18 08:06:03 dziura-fd JobId 17062: Connected Storage
        daemon at backup1.local:9103, encryption:
        TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
         2024-01-18 08:06:03 dziura-fd JobId 17062: Encryption:
        TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
         2024-01-18 08:06:05 bareos-sd JobId 17062: Volume
        "vchanger-1_0002_0042" previously written, moving to end of data.
         2024-01-18 08:06:05 bareos-sd JobId 17062: Ready to append
        to end of Volume "vchanger-1_0002_0042" size=26886488931
         2024-01-18 08:06:05 dziura-fd JobId 17062: Generate VSS
        snapshots. Driver="Win64 VSS"
         2024-01-18 08:06:07 dziura-fd JobId 17062:
        (C:\)\\?\Volume{7730df77-9bec-432c-a00a-597b4bf1a6f6}\ ->
        \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
         2024-01-18 08:06:07 dziura-fd JobId 17062: Cannot open
        "C:/windows/system32/config/DEFAULT": ERR=The process cannot
        access the file because it is being used by another process.
        .
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "Task Scheduler Writer", State: 0x1
        (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "VSS Metadata Store Writer", State: 0x1
        (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "Performance Counters Writer", State: 0x1
        (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "Shadow Copy Optimization Writer", State:
        0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:08 dziura-fd JobId 17062: VSS Writer
        (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
         2024-01-18 08:06:09 bareos-sd JobId 17062: Releasing device
        "vchanger-1-0" (/var/spool/vchanger/vchanger-1/0).
         2024-01-18 08:06:09 bareos-sd JobId 17062: Elapsed
        time=00:00:04, Transfer rate=158 Bytes/second
         2024-01-18 08:06:09 backup1-dir JobId 17062: Insert of
        attributes batch table with 1 entries start
         2024-01-18 08:06:09 backup1-dir JobId 17062: Insert of
        attributes batch table done
         2024-01-18 08:06:09 backup1-dir JobId 17062: Bareos
        backup1-dir 24.0.0~pre154.115b3ebca (08Jan24):
          Build OS:               Red Hat Enterprise Linux release
        8.7 (Ootpa)
          JobId:                  17062
          Job: win10test-fd.2024-01-18_08.06.02_12
          Backup Level:           Full
          Client:                 "dziura-fd" 23.0.1~pre57.8e89bfe0a
        (16Jan24) Microsoft Windows 8 Professional (build 9200),
        64-bit,Cross-compile
          FileSet:                "Windows_test" 2024-01-18 08:06:02
          Pool:                   "Offsite-eSATA" (>From Job resource)
          Catalog:                "PgCatalog" (From Client resource)
          Storage:                "vchanger-1-changer" (From Pool
        resource)
          Scheduled time:         18-Jan-2024 08:06:01
          Start time:             18-Jan-2024 08:06:04
          End time:               18-Jan-2024 08:06:09
          Elapsed time:           5 secs
          Priority:               10
          Allow Mixed Priority:   no
          FD Files Written:       2
          SD Files Written:       2
          FD Bytes Written:       0 (0 B)
          SD Bytes Written:       634 (634 B)
          Rate:                   0.0 KB/s
          Software Compression:   None
          VSS:                    yes
          Encryption:             no
          Accurate:               no
          Volume name(s):         vchanger-1_0002_0042
          Volume Session Id:      116
          Volume Session Time:    1704808920
          Last Volume Bytes:      26,886,490,011 (26.88 GB)
          Non-fatal FD errors:    1
          SD Errors:              0
          FD termination status:  OK
          SD termination status:  OK
          Bareos binary info:     Bareos pre-release (UNSUPPORTED):
        Get professional support from https://www.bareos.com
          Job triggered by:       User
          Termination:            Backup OK -- with warnings


        On 18.01.2024 09:04, Sebastian Sura wrote:

        Hi Spadajspadaj,

        something is wrong with your debug output but im not sure
        why.  Debug messages are normally formatted as

        daemon-name (level): file:line-jobid
        For some reason your jobid is 0 (which often means it could
        not be determined) here.
        This should normally not happen and might be why the vss
        name translation does not work for you.

        I tried reproducing the problem you described with your
        fileset, but it just works for me.
        Would it be possible for you to also submit the joblog for
        that particular job ?
        You can retrieve it using "list joblog jobid=17062".

        Sincerely
        Sebastian Sura

        Am 18.01.24 um 08:13 schrieb Spadajspadaj:
        FileSet {
          Name = "Windows_test"
          Enable VSS = yes
          Include {
            File = "C:/windows/system32/config/DEFAULT"
            Options {
               onefs = no
               Signature = MD5
               IgnoreCase = yes
               Portable = no
            }
          }
        }
        -- Sebastian Sura sebasti...@bareos.com Bareos GmbH & Co. KG
        Phone: +49 221 630693-0 https://www.bareos.com Fax: +49 221
        630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln:
        HRA 29646 Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, Jörg 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...@googlegroups.com.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/bareos-users/1154382e-9d9f-4252-bd16-92284ba6e010%40bareos.com
        
<https://groups.google.com/d/msgid/bareos-users/1154382e-9d9f-4252-bd16-92284ba6e010%40bareos.com?utm_medium=email&utm_source=footer>.

-- 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.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/bareos-users/f7f107b9-ba57-4ef4-84d8-a275a562bf67n%40googlegroups.com
    
<https://groups.google.com/d/msgid/bareos-users/f7f107b9-ba57-4ef4-84d8-a275a562bf67n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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/4c058438-864a-4ebe-8a17-54c1401e368cn%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/4c058438-864a-4ebe-8a17-54c1401e368cn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
 Sebastian surasebastian.s...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com            Fax:   +49 221 630693-10

 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg 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/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com.

Reply via email to