VSS ERR=The process cannot access the file because it is being used by another process

[Vorname Nachname]

Hello,

iam struggeling setting up the VSS-Support. Keep telling me, that the file is used by another process.

Fileset:

```bash

FileSet {
  Name = "client01-FileSet-2"
  Enable VSS = yes
  Include {
    Options {
      Signature = MD5
      Drive Type = fixed
      IgnoreCase = yes
      WildFile = "[A-Z]:/hiberfil.sys"
      WildFile = "[A-Z]:/pagefile.sys"
      WildFile = "[A-Z]:/swapfile.sys"
      WildDir = "[A-Z]:/RECYCLER"
      WildDir = "[A-Z]:/$RECYCLE.BIN"
      WildDir = "[A-Z]:/System Volume Information"
      Exclude = yes
    }
    File = "C:/Users/User/NTUSER.dat"
    File = "C:/ProgramData/Veeam/EndpointData"
  }
}

```

Log:

```bash

...
07-Feb 08:16 bareos-dir JobId 93: Start Backup JobId 93, Job=client01-Job.2022-02-07_08.16.56_00
07-Feb 08:16 bareos-dir JobId 93: Connected Storage daemon at xxxxxxxxx.de:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
07-Feb 08:16 bareos-dir JobId 93: Using Device "S3_ObjectStorage" to write.
07-Feb 08:16 bareos-dir JobId 93: Probing client protocol... (result will be saved until config reload)
07-Feb 08:16 bareos-dir JobId 93: Using Client Initiated Connection (client01).
07-Feb 08:16 bareos-dir JobId 93:    Handshake: Immediate TLS
07-Feb 08:16 bareos-sd JobId 93: Volume "client01-full-0013" previously written, moving to end of data.
07-Feb 08:17 bareos-sd JobId 93: Ready to append to end of Volume "client01-full-0013" size=593072728
07-Feb 08:16 client01 JobId 93: Created 27 wildcard excludes from FilesNotToBackup Registry key
07-Feb 08:16 client01 JobId 93: Connected Storage daemon at xxxxxxxxx.de:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
07-Feb 08:17 client01 JobId 93: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
07-Feb 08:17 client01 JobId 93: VolumeMountpoints are not processed as onefs = yes.
07-Feb 08:17 client01 JobId 93:      Cannot open "C:/Users/User/NTUSER.dat": ERR=The process cannot access the file because it is being used by another process.
07-Feb 08:17 client01 JobId 93:      Cannot open "C:/ProgramData/Veeam/EndpointData/VeeamBackup.mdf": ERR=The process cannot access the file because it is being used by another process.
07-Feb 08:17 client01 JobId 93:      Cannot open "C:/ProgramData/Veeam/EndpointData/VeeamBackup_log.ldf": ERR=The process cannot access the file because it is being used by another process.
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "SqlServerWriter", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
07-Feb 08:17 bareos-sd JobId 93: Releasing device "S3_ObjectStorage" (S3).
07-Feb 08:17 bareos-sd JobId 93: Elapsed time=00:00:16, Transfer rate=186  Bytes/second
07-Feb 08:17 bareos-dir JobId 93: Insert of attributes batch table with 4 entries start
07-Feb 08:17 bareos-dir JobId 93: Insert of attributes batch table done
...

```

Any suggestions?

Best,
Timo

[Vorname Nachname]

I've also tested the same with another program called restic. With restic iam able to backup the data from the vss-snapshot.
I also tried to run the bareos-fd as different user (local-administrator)

Any ideas?

Best,

Timo

[Vorname Nachname]

Another test i did, was to create the vss-snapshot manually on the windows-host and then copy the data from the manually created vss-snapshot-directory C:\TEST\C:

create-snapshot.ps1

$vss = [WMICLASS]"root\cimv2:win32_shadowcopy"
$vsssnapshot = $vss.Create('C:\', "ClientAccessible")
$vssshadow = Get-WmiObject Win32_ShadowCopy | Where-Object { $_.ID -eq $vsssnapshot.ShadowID }
$vssshadowpath  = $vssshadow.DeviceObject + "\"
$vsssnapshotid = "$vssshadow".Split('=')[1];
$vsssnapshotpath = "C:\TEST\C"
New-Item -ItemType Directory -Force -Path $(Split-Path $vsssnapshotpath -Parent) | Out-Null
cmd /c mklink /J $vsssnapshotpath $vssshadowpath | Out-Null
Write-Output "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") DEBUG:VSS ID: $vsssnapshotid"
Write-Output "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") DEBUG:VSS Mountpoint: $vsssnapshotpath successfully mounted"

job.conf

...

ClientRunBeforeJob = "powershell.exe -noprofile -executionpolicy bypass -file C:/scripts/create-snapshot.ps1"

...

The job runs without any errors or warnings. All files were able to be backupped. One more thing i noticed:

Bareos creates a snapshot will following attributes: vssadmin list shadows

...

Typ: Backup
Attribute: Differential, Auto recovered

...

while the manually created snapshot contains following attributes:

...

Typ: ClientAccessible
Attribute: Persistent, Client-accessible, No auto release, No writers, Differential

...

Any input is welcome

Best,

Timo

[Andreas Rogge]

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

[Vorname Nachname]

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

[Matt Bader]

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

[jo.go...@hosted-power.com]

We have simuilar issues, it seems for some servers a lot is skipped. We would really like to get to the root cause

[spadaj...@gmail.com]

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

[Spadajspadaj]

The more I dig into it, the more it seems it is bareos after all.

Unfortunately, building Windows bareos-fd is no small feat so I cannot directly debug it but.

I ran a procmon against bareos-fd.exe and it seems that while the FD process does create a VSS snapshot... it doesn't read from it. It reads the files straight from the main device. I did a small test fileset consisting of just my user's registry file. And both procmon's dump as well as bareos-fd own debug trace shows that it's trying to read simply a c:\users\test\ntuser.dat instead of properly going for \\?\GLOBALROOT\Device\HardDiskVolumeShadowCopyXX\Users\test\ntuser.dat. That would explain why the job even though it's supposed to use VSS, fails on copying open files.

When I created a very small example VS project just creating a VSS snapshot and copying said file out of the VSS snapshot (using the proper shadow copy volume path), it works OK.

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

[Spadajspadaj]

As I understand, this is the interesting excerpt from the debug trace.

win10test-fd (50): findlib/find.cc:169-0 Verify=<V> Accurate=<Cmcs> BaseJob=<Jspug5> flags=<724185736>
win10test-fd (50): findlib/find.cc:169-0 Verify=<V> Accurate=<Cmcs> BaseJob=<Jspug5> flags=<724185736>
win10test-fd (450): findlib/find.cc:175-0 F C:/Users/test/NTUSER.DAT
win10test-fd (500): compat/compat.cc:278-0 Enter convert_unix_to_win32_path
win10test-fd (500): compat/compat.cc:322-0 path = \\?\C:\Users\test\NTUSER.DAT
win10test-fd (500): compat/compat.cc:328-0 Leave cvt_u_to_win32_path path=\\?\C:\Users\test\NTUSER.DAT
win10test-fd (500): compat/compat.cc:234-0 Win32ConvInitCache: Setup of thread specific cache at address 1532b2b76d0
win10test-fd (500): compat/compat.cc:531-0 Enter make_wchar_win32_path
win10test-fd (500): compat/compat.cc:555-0 Leave make_wchar_win32_path=\\?\C:\Users\test\NTUSER.DAT
win10test-fd (500): compat/compat.cc:1609-0 sizino=8 ino=0 filename=C:/Users/test/NTUSER.DAT
win10test-fd (300): findlib/find_one.cc:911-0 File ----: C:/Users/test/NTUSER.DAT
win10test-fd (130): filed/backup.cc:535-0 FT_REG saving: C:/Users/test/NTUSER.DAT
win10test-fd (130): filed/backup.cc:646-0 filed: sending C:/Users/test/NTUSER.DAT to stored
win10test-fd (150): lib/crypto_openssl.cc:641-0 crypto_digest_new jcr=1532b228410
win10test-fd (300): filed/backup.cc:1575-0 encode_and_send_attrs fname=C:/Users/test/NTUSER.DAT
win10test-fd (500): compat/compat.cc:278-0 Enter convert_unix_to_win32_path
win10test-fd (500): compat/compat.cc:322-0 path = \\?\C:\Users\test\NTUSER.DAT
win10test-fd (500): compat/compat.cc:328-0 Leave cvt_u_to_win32_path path=\\?\C:\Users\test\NTUSER.DAT
win10test-fd (300): filed/backup.cc:1594-0 File C:/Users/test/NTUSER.DAT
attribs=A A IH/ B A A CAi FAAA A A BlnTaz BlnTaz BlnTaz A A L
attribsEx=CAi HaQkZzohoU HaQvQ8Q7yY HaQvQ8Q7yY A FAAA
win10test-fd (300): filed/backup.cc:1620-0 >stored: attrhdr 1 5 0win10test-fd (200): filed/backup.cc:1772-0 No strip for C:/Users/test/NTUSER.DAT
win10test-fd (300): filed/backup.cc:1715-0 >stored: attr len=130: 1 3 C:/Users/test/NTUSER.DAT
win10test-fd (150): filed/backup.cc:737-0 type=3 do_read=1
win10test-fd (100): findlib/bfile.cc:710-0 bopen: fname C:/Users/test/NTUSER.DAT, flags 00100000, mode 0000, rdev 8226
win10test-fd (50): findlib/bfile.cc:565-0 === NO plugin
win10test-fd (100): findlib/bfile.cc:664-0 Read CreateFileW=\\?\C:\Users\test\NTUSER.DAT
win10test-fd (850): lib/message.cc:1216-0 Enter Jmsg type=8
win10test-fd (850): lib/message.cc:613-0 Enter DispatchMessage type=8 msg=win10test-fd JobId 16959:      Cannot open "C:/Users/test/NTUSER.DAT": ERR=The process cannot access the file because it is being used by another process.
.
win10test-fd (850): lib/message.cc:820-0 DIRECTOR for following msg: win10test-fd JobId 16959:      Cannot open "C:/Users/test/NTUSER.DAT": ERR=The process cannot access the file because it is being used by another process.
.
win10test-fd (400): findlib/find_one.cc:493-0 FT_REG FI=1 linked=0 file=C:/Users/test/NTUSER.DAT

From what I understand from the description of the make_wchar_win32_path() method in win32/compat/compat.cc - we should leave the function with the filename properly converted to VSS-based one. But apparently we're stuck with local name.

MK

[Bruno Friedmann (bruno-at-bareos)]

Hello, all normally the issues that are described here, should have been already fixed, and should work without any trouble with bareos >= 23

The code fixing the problem has been submitted and merge a certain time ago with PR1452

https://github.com/bareos/bareos/pull/1452

Please refresh your installation, and of course report success and failures.

[Spadajspadaj]

I used the relatively new available client. (23-pre-something, downloaded around 2 weeks ago). Yes, I should have written that explicitly.

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/8169ba0f-0d16-450b-bb91-d72e56db9ee7n%40googlegroups.com.

[Bruno Friedmann (bruno-at-bareos)]

Hi Spadapjspadaj,

When we examine what happen on test machine here we see it working correctly.

Especially that the VSS is present.

you may think we don't backup the snapshot due to the presence of C:/Users/user/NTUSER.dat in the log, but you need to understand that is the resulting file name after its conversion in compact.cccompat/compat.cc:555-307 Leave make_wchar_win32_path=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Users\user\NTUSER.datcompat/compat.cc:1609-307 sizino=8 ino=0 filename=C:/Users/user/NTUSER.dat desktop-vcf7e32-fd (300): findlib/find_one.cc:911-307 File ----: C:/Users/user/NTUSER.dat desktop-vcf7e32-fd (130): filed/backup.cc:535-307 FT_REG saving: C:/Users/user/NTUSER.dat desktop-vcf7e32-fd (130): filed/backup.cc:646-307 filed: sending C:/Users/user/NTUSER.dat to stored

So to be sure we use the same code, could you please install and run the following bareos-fd

https://download.bareos.org/current/windows/winbareos-23.0.1~pre57.8e89bfe0a-release-64-bit.exe

In your director you set the debug level to 500 for that client (changing the client name in the following example)

setdebug level=500 trace=1 timestamp=1 client=windows-fd

this will indicate where the tracelog will be written (often directly on C:\)

run one backup job then disable the debugging,

To extract in text mode the joblog in bconsole

@out /tmp/backup-win-fd.joblog

list joblog jobid=XXXXX

q

Then you can zip and attach both trace and joblog here.

Add the fileset used too.

BTW please ensure your fileset contain 

  Enable VSS = yes

as stated in documentation and Windows fileset example.

[Bruno Friedmann (bruno-at-bareos)]

To add an illustration to the fact that BareOS works as documented and expected.

We run a backup job while the registry hive is open in regedit and we tried to remove it so you get the expected error, the file is in use.

In the background you can see the success of the job backing up that file without any error.
See the details about the status of VSS BackupComplete.

[Spadajspadaj]

Hi Bruno.

Yes, I understand how it's supposed to work. :-)

OK, I will re-run the tests when I have a spare minute and dump the trace somewhere (the excerpt I posted earlier was with debug level 999 so all messages should have been captured).

And it's not that I _thought_ it wasn't backed up. I know it wasn't backed up. It was throwing errors of being unable to access the file and if I wanted to restore the files I got a zero-length content. I know it should have been converted to the shadowcopy-based filename but wasn't.

I'll check the latest package version first though.

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/9bb76105-597b-4cb9-b5b5-95f54e5b96e6n%40googlegroups.com.

[jo.go...@hosted-power.com]

I just tried https://download.bareos.org/current/windows/winbareos-23.0.1~pre57.8e89bfe0a-release-64-bit.exe on Windows 2022. But I still have 100's of failed in use files :/

[Bruno Friedmann (bruno-at-bareos)]

Please, may I ask you to either provided the trace and job log as requested.
As I can argue that we are using 2019 to 2022 with 0% of your troubles

That kind of guerilla can be endless.

If we have traces, joblog fileset etc we may have a chance to reproduce.
If it is reproducible, then there's a chance to have a fix.
If we can elaborate that fix, you may have a chance to solve your trouble.

[Spadajspadaj]

OK. I had a few spare minutes. I did upgrade to the pre57 release I downloaded today from https://download.bareos.org/current/windows/

The fileset is very simple so that the job is quick and short. It consists of just one file from the windows registry (so that it will be open for sure).

FileSet {
  Name = "Windows_test"

  Enable VSS = yes
  Include {

    File = "C:/windows/system32/config/DEFAULT"
    Options {
       onefs = no
       Signature = MD5
       IgnoreCase = yes
       Portable = no
    }
  }
}

(I tried with both Portable=no as well as Portable=yes as I found some info that it may change backup job behaviour but there was no difference. onefs option is just a remnant from older test jobs, I assume it should have no impact here as we're only targeting a single file).

Attaching the trace from the FD. It's the same as before - the snapshot is being created but the filename is not being converted for read in the end even though the snapshot is there.

MK

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/F46rRPh7Hf8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/30b4adee-5fe4-44dc-8f63-e63eb803fd5dn%40googlegroups.com.

[Sebastian Sura]

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

[Spadajspadaj]

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

--

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.

[jo.go...@hosted-power.com]

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!

[Spadajspadaj]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/f7f107b9-ba57-4ef4-84d8-a275a562bf67n%40googlegroups.com.

[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

[Sebastian Sura]

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:

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/4c058438-864a-4ebe-8a17-54c1401e368cn%40googlegroups.com.

[Spadajspadaj]

Yes, it does seem to be working!

22-Jan 14:16 dziura-fd JobId 17111: Generate VSS snapshots. Driver="Win64 VSS"
22-Jan 14:16 dziura-fd JobId 17111: VolumeMountpoints are not processed as onefs = yes.
22-Jan 14:16 dziura-fd JobId 17111: VolumeMountpoints are not processed as onefs = yes.
22-Jan 14:16 dziura-fd JobId 17111: (S:\)\\?\Volume{260653cf-633a-4504-992e-f82620702a9e}\ -> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy31
22-Jan 14:16 dziura-fd JobId 17111: (C:\)\\?\Volume{7730df77-9bec-432c-a00a-597b4bf1a6f6}\ -> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy30
[...]
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:  OK
  SD termination status:  OK

*status client=dziura-fd
[...]
dziura-fd Version: 24.0.0~pre187.8e12c147a (22 January 2024)  VSS Microsoft Windows 8 Professional (build 9200), 64-bit

Thank you!

MK

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com.

[Joshua Myles]

I've only tested with one client, but 24.0.0~pre187.8e12c147a did work with no VSS errors. I'll be watching for this to be backported to 22 (subscription).

Josh

[Andreas Rogge]

Hi Josh,

the backport has already happened in PR 1667. You can try the
pre-release packages from these subscription repositories:
https://download.bareos.com/bareos/testing/CD/bareos-22

Version 22.1.4~pre39 (and every newer version) should contain the fix.
You can safely install the packages from there. An upgrade to the
upcoming version 22.1.4 will be seamless.

Best Regards,
Andreas

Am 24.01.24 um 12:33 schrieb Joshua Myles:

> I've only tested with one client, but 24.0.0~pre187.8e12c147a did work
> with no VSS errors. I'll be watching for this to be backported to 22
> (subscription).
>
> Josh
>
> On Monday, January 22, 2024 at 11:37:51 AM UTC-5 Spadajspadaj wrote:
>

> __

>>>> https://www.bareos.com <https://www.bareos.com>

>>>>> 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...@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 Surasebasti...@bareos.com

>> Bareos GmbH & Co. KG Phone: +49 221 630693-0

>> https://www.bareos.com <https://www.bareos.com> Fax:+49 221 630693-10 <tel:+49%20221%2063069310>

>>
>> 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/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com <https://groups.google.com/d/msgid/bareos-users/97579337-c80a-4b0d-8a71-997c2633489f%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

> <mailto:bareos-users...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Andreas Rogge andrea...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://www.bareos.com

[jo.go...@hosted-power.com]

Ok that is cool, this similar exists for Bareos 23? Since we're already on 23.0.1, the 22.x would be also a lower version :)

[Andreas Rogge]

Yes, it is in the pre-release for 23 and also for 21.

Am 24.01.24 um 20:59 schrieb 'jo.go...@hosted-power.com' via bareos-users:

> >>>>> <https://www.bareos.com <https://www.bareos.com>> Fax: +49
> 221 630693-10 <tel:+49%20221%2063069310> 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> <https://groups.google.com/d/msgid/bareos-users/1154382e-9d9f-4252-bd16-92284ba6e010%40bareos.com?utm_medium=email&utm_source=footer <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> <https://groups.google.com/d/msgid/bareos-users/f7f107b9-ba57-4ef4-84d8-a275a562bf67n%40googlegroups.com?utm_medium=email&utm_source=footer <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...@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> <https://groups.google.com/d/msgid/bareos-users/4c058438-864a-4ebe-8a17-54c1401e368cn%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/bareos-users/4c058438-864a-4ebe-8a17-54c1401e368cn%40googlegroups.com?utm_medium=email&utm_source=footer>>.

> >> --
> >> Sebastian Surasebasti...@bareos.com
> >> Bareos GmbH & Co. KG Phone: +49 221 630693-0
> >> https://www.bareos.com <https://www.bareos.com>
> <https://www.bareos.com <https://www.bareos.com>> Fax:+49 221

> 630693-10 <tel:+49%20221%2063069310> <tel:+49%20221%2063069310>

> >>
> >> 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/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com <https://groups.google.com/d/msgid/bareos-users/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com> <https://groups.google.com/d/msgid/bareos-users/97579337-c80a-4b0d-8a71-997c2633489f%40bareos.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/bareos-users/97579337-c80a-4b0d-8a71-997c2633489f%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
> > <mailto:bareos-users...@googlegroups.com>.
> > To view this discussion on the web visit
> >

> https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com> <https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/bareos-users/b88fd209-86cc-48b9-9004-4f4161b2494en%40googlegroups.com?utm_medium=email&utm_source=footer>>.

>
> --
> Andreas Rogge andrea...@bareos.com
> Bareos GmbH & Co. KG Phone: +49 221-630693-86

> <tel:+49%20221%2063069386>
> http://www.bareos.com <http://www.bareos.com>

>
> 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
> <mailto:bareos-users...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/bareos-users/77c7fa26-ee69-44f9-8f89-527cbfddbc44n%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/77c7fa26-ee69-44f9-8f89-527cbfddbc44n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[jo.go...@hosted-power.com]

Where do I find the 23 pre release? I only see version 22 on the link shared earlier? :)

[Sebastian Sura]

They can be found here: https://download.bareos.org/current/

Sincerly

Sebastian Sura

Am 25.01.24 um 21:20 schrieb 'jo.go...@hosted-power.com' via bareos-users:

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/288384c2-7743-4afe-8ce0-791e50b6c898n%40googlegroups.com.

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

[Joshua Myles]

Checking in to provide a report on 22.1.4 and the VSS issue for client-initiated connections. We have 11 Windows FDs using client-initiated connections, and nearly all of them would previously give VSS warnings (ERR=The process cannot access the file because it is being used by another process.) and caused us to effectively ignore the Bareos warning jobs.

As of 22.1.4 a couple of days ago, we've not seen any job warnings due to VSS. So here its looks like the fix is good, and I'd expect the same from 23.0.2 though haven't tested it yet.

Josh