I used the relatively new available client. (23-pre-something,
downloaded around 2 weeks ago). Yes, I should have written that explicitly.
On 16.01.2024 15:23, Bruno Friedmann (bruno-at-bareos) wrote:
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.
Le jeudi 11 janvier 2024 à 23:17:26 UTC+1, Spadajspadaj a écrit :
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
On 11.01.2024 22:03, Spadajspadaj wrote:
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...@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/8169ba0f-0d16-450b-bb91-d72e56db9ee7n%40googlegroups.com
<https://groups.google.com/d/msgid/bareos-users/8169ba0f-0d16-450b-bb91-d72e56db9ee7n%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/5f75fd08-f465-4704-b13b-81a241811b3c%40gmail.com.
