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

On 9.01.2024 15:11, spadaj...@gmail.com wrote:
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
On Friday, April 28, 2023 at 3:33:36 PM UTC+2 jo.go...@hosted-power.com wrote:

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

    On Wednesday, 21 December 2022 at 04:19:35 UTC+1 Matt Bader wrote:

        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

        On Friday, February 11, 2022 at 6:21:59 PM UTC+1
        zehnb...@gmail.com wrote:

            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

            Andreas Rogge schrieb am Donnerstag, 10. Februar 2022 um
            20:30:54 UTC+1:

                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
                <tel:+49%20221%2063069386>
                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

--
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/56334b0f-cabd-4570-8e4d-c7ba70b8dfc7n%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/56334b0f-cabd-4570-8e4d-c7ba70b8dfc7n%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/601cf55a-944f-4525-a4ba-55d66f01bd5e%40gmail.com.

Reply via email to