Mysterious Compression Problems

[chri.s]

Hi Bareos Owners,

i have a mysterious problem with todays nightly build 3.3: When i place the gzip compression everything went fine. After changing to lz4 or lz4hc in the FileSet of a Host i get the error that compatible mode is on, while it is set like this:


Error: Fatal error: Illegal compression algorithm LZ4 for compatible mode

<code>
FileDaemon {
Name = bareos-fd
FDport = 9102
Maximum Concurrent Jobs = 20
FDAddress = 10.1.1.36
compatible = no
}</code>

in bareos-fd. Does it need some other configuration to get out of the compability mode?

I am running the 3.3 with configuration build in v 2.4x because 2.4x has some problems with stopping backups in a WAN environment and except this error/misconfiguration problem? everything is running pretty fine. (Thanks at this time to the bareos dev guys.)

Maybe somebody has a hint for me.

Kind Regards,

Chris

[Masopust, Christian]

Hi Chris,

it's in the documentation: http://www.bareos.org/en/HOWTO/articles/new-in-version-1320.html
you need to set "compatible = no" in your fd-config.

br,
christian

-----Ursprüngliche Nachricht-----
Gesendet: Dienstag, 24. September 2013 00:40
Betreff: [bareos-users] Mysterious Compression Problems
Hi Bareos Owners,
When i place the gzip compression everything went fine. After
changing to lz4 or lz4hc in the FileSet of a Host i get the
Error: Fatal error: Illegal compression algorithm LZ4 for
compatible mode
<code>
FileDaemon {
Name = bareos-fd
FDport = 9102
Maximum Concurrent Jobs = 20
FDAddress = 10.1.1.36
compatible = no
}</code>
in bareos-fd. Does it need some other configuration to get
out of the compability mode?
I am running the 3.3 with configuration build in v 2.4x
because 2.4x has some problems with stopping backups in a WAN
environment and except this error/misconfiguration problem?
everything is running pretty fine. (Thanks at this time to
the bareos dev guys.)
Maybe somebody has a hint for me.
Kind Regards,
Chris
--
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
For more options, visit https://groups.google.com/groups/opt_out.

[Masopust, Christian]

Sorry, forget my previous mail... shouldn't answer emails
when having fever :)

-----Ursprüngliche Nachricht-----
Von: Masopust, Christian
Gesendet: Dienstag, 24. September 2013 08:13
Betreff: AW: [bareos-users] Mysterious Compression Problems
Hi Chris,
http://www.bareos.org/en/HOWTO/articles/new-in-version-1320.html
you need to set "compatible = no" in your fd-config.
br,
christian

-----Ursprüngliche Nachricht-----
Gesendet: Dienstag, 24. September 2013 00:40
Betreff: [bareos-users] Mysterious Compression Problems
Hi Bareos Owners,
When i place the gzip compression everything went fine. After
changing to lz4 or lz4hc in the FileSet of a Host i get the
Error: Fatal error: Illegal compression algorithm LZ4 for
compatible mode
<code>
FileDaemon {
Name = bareos-fd
FDport = 9102
Maximum Concurrent Jobs = 20
FDAddress = 10.1.1.36
compatible = no
}</code>
in bareos-fd. Does it need some other configuration to get
out of the compability mode?
I am running the 3.3 with configuration build in v 2.4x
because 2.4x has some problems with stopping backups in a WAN
environment and except this error/misconfiguration problem?
everything is running pretty fine. (Thanks at this time to
the bareos dev guys.)
Maybe somebody has a hint for me.
Kind Regards,
Chris
--
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
For more options, visit https://groups.google.com/groups/opt_out.

[Philipp Storz]

Hello Cris,


I just did a quick test to verify your problem, and here everything works correctly.
Also, the regression tests running all lz* flavors are working.

(see for example
http://regress.bareos.org/testSummary.php?project=1&name=disk%3Alz4-test&date=2013-09-24)

Are you sure that you really restarted the bareos-fd with the new configuration?

I guess that your bareos-fd is not running the new configuration.

Shutdown the bareos-fd, make sure it is not running anymore and start it again.
That should make your configuration work.

Best regards,

Philipp

Post by chri.s
Hi Bareos Owners,
Error: Fatal error: Illegal compression algorithm LZ4 for compatible mode
<code>
FileDaemon {
Name = bareos-fd
FDport = 9102
Maximum Concurrent Jobs = 20
FDAddress = 10.1.1.36
compatible = no
}</code>
in bareos-fd. Does it need some other configuration to get out of the compability mode?
I am running the 3.3 with configuration build in v 2.4x because 2.4x has some problems with stopping backups in a WAN environment and except this error/misconfiguration problem? everything is running pretty fine. (Thanks at this time to the bareos dev guys.)
Maybe somebody has a hint for me.
Kind Regards,
Chris

--
Mit freundlichen Grüßen

Philipp Storz ***@bareos.com
Bareos GmbH & Co. KG Phone: Phone: [phone]
http://www.bareos.com Fax: [phone]

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz, M. v. Wieringen

[chri.s]

Hello Phillip,

thanks for your help.

But: even more. After the System is just for evaluation purposes i restarted it after configuration change. The problem still exists.

24-Sep 10:20 server JobId 41: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="D"
24-Sep 10:20 server JobId 41: Fatal error: No pointer to VssObject or Backup is not Initialized
24-Sep 10:20 server JobId 41: Fatal error: CreateSGenerate VSS snapshots failed. ERR=Function not implemented
24-Sep 10:20 server JobId 41: Fatal error: Illegal compression algorithm LZ4HC for compatible mode
24-Sep 10:18 LocalStorage JobId 41: Fatal error: append.c:159 Error reading data header from FD. ERR=No data available

Compatible is set like shown above in bareos-fd. When set to something with lz this package of errors occurs. Set back to gzip everything is running bareos-fine.

BR,

Chris

[Philipp Storz]

Hello Chris,

it would have been an interesting information that you are talking about a windows client :)

However, I just did a test setup with the latest packages from nightly on a linux machine and a
nightly windows package on a windows7 64bit testmachine, everything works fine.

Looks like you already get an error when creating the vss snapshot.
Maybe you could try to disable vss and see if you still get the same errors.

Also, you could try another machine to verify it is not a local problem on your windows box.


The nightly packages are working in my test setup:


24-Sep 12:46 bacula-dir JobId 4: No prior Full backup Job record found.
24-Sep 12:46 bacula-dir JobId 4: No prior or suitable Full backup found in catalog. Doing FULL backup.
24-Sep 12:46 bacula-dir JobId 4: Start Backup JobId 4, Job=BackupClient1.2013-09-24_12.46.49_14
24-Sep 12:46 bacula-dir JobId 4: Using Device "FileStorage" to write.
24-Sep 12:46 bareos-sd JobId 4: Volume "File-0001" previously written, moving to end of data.
24-Sep 12:46 bareos-sd JobId 4: Ready to append to end of Volume "File-0001" size=10669290
24-Sep 10:47 bac-win-64-fd JobId 4: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 12:47 bareos-sd JobId 4: Elapsed time=00:00:41, Transfer rate=2.268 M Bytes/second
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State:
0x1 (VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "Performance Counters Writer",
State: 0x1 (VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "System Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "ASR Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "Registry Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer",
State: 0x1 (VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "MSSearch Service Writer", State:
0x1 (VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "BITS Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 10:47 bac-win-64-fd JobId 4: VSS Writer (BackupComplete): "WMI Writer", State: 0x1
(VSS_WS_STABLE)
24-Sep 12:47 bacula-dir JobId 4: Bareos bacula-dir 13.3.0 (01Aug13):
Build OS: x86_64-suse-linux-gnu suse openSUSE 12.3 (x86_64)
JobId: 4
Job: BackupClient1.2013-09-24_12.46.49_14
Backup Level: Full (upgraded from Incremental)
Client: "bac-win-64-fd" 13.3.0 (01Aug13) Microsoft Windows 7 Ultimate Edition
Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64
FileSet: "Windows All Drives" 2013-09-24 12:42:39
Pool: "File" (From Job resource)
Catalog: "MyCatalog" (From Pool resource)
Storage: "File" (From Job resource)
Scheduled time: 24-Sep-2013 12:46:49
Start time: 24-Sep-2013 12:46:51
End time: 24-Sep-2013 12:47:33
Elapsed time: 42 secs
Priority: 10
FD Files Written: 685
SD Files Written: 685
FD Bytes Written: 92,870,020 (92.87 MB)
SD Bytes Written: 93,008,361 (93.00 MB)
Rate: 2211.2 KB/s
Software Compression: 45.4 % (lz4)
VSS: yes
Encryption: no
Accurate: no
Volume name(s): File-0001
Volume Session Id: 3
Volume Session Time: 1380019261
Last Volume Bytes: 103,781,675 (103.7 MB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

Post by chri.s
Hello Phillip,
thanks for your help.
But: even more. After the System is just for evaluation purposes i restarted it after configuration change. The problem still exists.
24-Sep 10:20 server JobId 41: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="D"
24-Sep 10:20 server JobId 41: Fatal error: No pointer to VssObject or Backup is not Initialized
24-Sep 10:20 server JobId 41: Fatal error: CreateSGenerate VSS snapshots failed. ERR=Function not implemented
24-Sep 10:20 server JobId 41: Fatal error: Illegal compression algorithm LZ4HC for compatible mode
24-Sep 10:18 LocalStorage JobId 41: Fatal error: append.c:159 Error reading data header from FD. ERR=No data available
Compatible is set like shown above in bareos-fd. When set to something with lz this package of errors occurs. Set back to gzip everything is running bareos-fine.
BR,
Chris

--
Mit freundlichen Grüßen

Philipp Storz ***@bareos.com
Bareos GmbH & Co. KG Phone: Phone: [phone]
http://www.bareos.com Fax: [phone]

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz, M. v. Wieringen

[chri.s]

Hello Philip,

sorry for the lack of information :-)

The backup is running fine with the gzip configuration nothing has changed except the compressionrate - so i think there is no problem with the host.

I reinstalled the actual nightly windows build on the Targetserver. After a rerun the errors where just the compatible mode:

24-Sep 11:53 server JobId 42: Fatal error: Illegal compression algorithm LZ4 for compatible mode
24-Sep 11:51 LocalStorage JobId 42: Fatal error: append.c:159 Error reading data header from FD. ERR=No data available
24-Sep 11:51 LocalStorage JobId 42: Elapsed time=00:00:10, Transfer rate=0 Bytes/second
24-Sep 11:51 bareos-dir JobId 42: Error: Bareos bareos-dir 13.3.0 (01Aug13):


So still no "no compatible" mode, even as the option is set correct. Just a bug?

BR,

chris

[Philipp Storz]

Hello Chris,

as I could not replay your problem please retry on another box.

It looks like your fd is running without having the compatible=no set.

Are you sure that you are editing the right config file?

Post by chri.s
Hello Philip,
sorry for the lack of information :-)
The backup is running fine with the gzip configuration nothing has changed except the compressionrate - so i think there is no problem with the host.
24-Sep 11:53 server JobId 42: Fatal error: Illegal compression algorithm LZ4 for compatible mode
24-Sep 11:51 LocalStorage JobId 42: Fatal error: append.c:159 Error reading data header from FD. ERR=No data available
24-Sep 11:51 LocalStorage JobId 42: Elapsed time=00:00:10, Transfer rate=0 Bytes/second
So still no "no compatible" mode, even as the option is set correct. Just a bug?
BR,
chris

--
Mit freundlichen Grüßen

Philipp Storz ***@bareos.com
Bareos GmbH & Co. KG Phone: Phone: [phone]
http://www.bareos.com Fax: [phone]

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz, M. v. Wieringen

[chri.s]

As easy as it could be: The compatible mode has to be set on both sites :-)

Sorry.