View Issue Details

IDProjectCategoryView StatusLast Update
0001507bareos-corefile daemonpublic2023-01-12 17:43
ReporterPacoCables Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformIntel / HP Proliant OSWindows server 64bitsOS Version2019 std edition
Product Version22.0.0 
Summary0001507: Filedaemon fails to do VSS on windows client if it has Spanish as default language
DescriptionWhen Filedaemon receive the message from Windows that tell us the VSS initialization is complete without errors in Spanish, It's considered an error and backup fails.
See next log part:

03-Jan 15:31 sglin003sxxi-fd JobId 11: Connected Storage daemon at 192.168.1.8:9103, encryption: None
03-Jan 15:31 sglin003sxxi-fd JobId 11: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
03-Jan 15:31 sglin003sxxi-fd JobId 11: VolumeMountpoints are not processed as onefs = yes.
03-Jan 15:31 sglin003sxxi-fd JobId 11: Fatal error: CreateSGenerate VSS snapshots failed. ERR=La operaci�n se complet� correctamente.

03-Jan 15:31 sglin003sxxi-fd JobId 11: Error: VSS API failure calling "BackupComplete". ERR=Object is not initialized; called during restore or not called in correct sequence.
03-Jan 15:31 sglin003sxxi-fd JobId 11: Warning: VSS Writer "Shadow Copy Optimization Writer" has invalid state. ERR=The writer vetoed the shadow copy creation process during the backup preparation state.
03-Jan 15:31 sglin001v-sd JobId 11: Releasing device "sglin001v-FileStorage" (/vm/machines/backup/).

The string "La operaci�n se complet� correctamente." means operation completed sucessfully!!
03
Steps To ReproduceIt's supposed you've a Bareos server running elsewhere.
* Install the Spanish version of Windows server (2016 or 2019) in standard edition with desktop experience in a compatible PC. It can be a virtual one.
* Install Windows version of Bareos on it, only client part (filedaemon + systray).
* Configure client, storage, fileset and job as you like
* Be sure you have "Enable VSS = yes" option in fileset
* Run the backup
Additional InformationIf you switch the system language to English, backup runs normally.

It seems that Bareos is making a string compare in place of get a status code or return code (numeric??). Is it that??

(Sorry for my very poor English)
Tagsfiledemon, language, VSS
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

bruno-at-bareos

bruno-at-bareos

2023-01-05 15:56

developer   ~0004853

Hi, we have tried to reproduce the issue, and unfortunately everything is working as expected as you can imagine

cat bareos22_joblog7.log
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Start Backup JobId 140698833649671, Job=backup-bareos-fd.2023-01-05_06.48.43_03
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Connected Storage daemon at localhost:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Probing client protocol... (result will be saved until config reload)
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Connected Client: bareos-fd at localhost:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Handshake: Immediate TLS
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-pluton-dir JobId 7: Using Device "FileStorage" to write.
 2023-01-05 06:48:45 bareos-pluton-fd JobId 7: Created 18 wildcard excludes from FilesNotToBackup Registry key
 2023-01-05 06:48:45 bareos-pluton-fd JobId 7: Connected Storage daemon at localhost:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-pluton-fd JobId 7: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
 2023-01-05 06:48:45 bareos-sd JobId 7: Volume "Full-0001" previously written, moving to end of data.
 2023-01-05 06:48:45 bareos-sd JobId 7: Ready to append to end of Volume "Full-0001" size=491321846
 2023-01-05 06:48:47 bareos-pluton-fd JobId 7: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
 2023-01-05 06:48:48 bareos-pluton-fd JobId 7: VolumeMountpoints are not processed as onefs = yes.
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-sd JobId 7: Releasing device "FileStorage" (C:/bareos-storage).
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-sd JobId 7: Elapsed time=00:00:43, Transfer rate=7.312 M Bytes/second
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-fd JobId 7: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
 2023-01-05 06:49:28 bareos-pluton-dir JobId 7: Insert of attributes batch table with 3340 entries start
 2023-01-05 06:49:28 bareos-pluton-dir JobId 7: Insert of attributes batch table done
 2023-01-05 06:49:28 bareos-pluton-dir JobId 7: Bareos bareos-pluton-dir 22.0.2~pre (02Jan23):
  Build OS: Microsoft Windows Server 2012 (build 9200), 64-bit
  JobId: 7
  Job: backup-bareos-fd.2023-01-05_06.48.43_03
  Backup Level: Full
  Client: "bareos-fd" 22.0.2~pre (02Jan23) Microsoft Windows Server 2012 (build 9200), 64-bit,Cross-compile
  FileSet: "SelfTest" 2022-10-31 03:59:08
  Pool: "Full" (From Job FullPool override)
  Catalog: "MyCatalog" (From Client resource)
  Storage: "File" (From Job resource)
  Scheduled time: 05-Jan-2023 06:48:43
  Start time: 05-Jan-2023 06:48:45
  End time: 05-Jan-2023 06:49:28
  Elapsed time: 43 secs
  Priority: 10
  FD Files Written: 3,341
  SD Files Written: 3,341
  FD Bytes Written: 313,762,080 (313.7 MB)
  SD Bytes Written: 314,441,669 (314.4 MB)
  Rate: 7296.8 KB/s
  Software Compression: None
  VSS: yes
  Encryption: no
  Accurate: no
  Volume name(s): Full-0001
  Volume Session Id: 1
  Volume Session Time: 1672930038
  Last Volume Bytes: 806,107,163 (806.1 MB)
  Non-fatal FD errors: 0
  SD Errors: 0
  FD termination status: OK
  SD termination status: OK
  Bareos binary info: Bareos community build (UNSUPPORTED): Get professional support from https://www.bareos.com
  Job triggered by: User

The error you got look like coming from the system, maybe VSS is not able to create a snapshot and report that, you will have to check in windows system journal to see
the root cause (maybe not enough free space or something similar)

Here the tested system is a windows 2022 server, with spanish as first language, but make no difference if we change it to english.
bruno-at-bareos

bruno-at-bareos

2023-01-12 16:06

developer   ~0004856

Ping any news ?
PacoCables

PacoCables

2023-01-12 17:43

reporter   ~0004860

I've the Windows server running in production. I changed the language to English and all runs well. I can't touch this machine evermore.
Now I'm trying to find a place where setup a Windows server 2019 standard edition with Spanish iso image from Microsoft to reproduce the issue. As sonn as I've it ready i'll put here the result.
Sorry for the delay, but I haven't enough resources :(

Issue History

Date Modified Username Field Change
2023-01-03 18:21 PacoCables New Issue
2023-01-03 18:21 PacoCables Tag Attached: filedemon
2023-01-03 18:21 PacoCables Tag Attached: language
2023-01-03 18:21 PacoCables Tag Attached: VSS
2023-01-05 15:56 bruno-at-bareos Note Added: 0004853
2023-01-12 16:06 bruno-at-bareos Note Added: 0004856
2023-01-12 17:43 PacoCables Note Added: 0004860