 |
There is no difference where to restore backups: windows agent, ubuntu, freebsd and centos have zero size files. |
|
|
I also have this problem. I have backups for MySQL and MSSQL performed by different Python plugin scripts. The MySQL backups can restore using the Python script OR a generic restore job. The MSSQL backups can restore using the Python script but NOT a generic restore job. When restoring using a generic job on a BSD FD, the restore job reports as successful with the correct number of the files and file sizes. The files are actually empty. When restored using a generic job on Windows the finishes in error after throwing this error message MANY times: 05-Jul 22:25 [CLIENT] JobId 79: Error: filed/restore.c:1231 Write error on [FILE PATH]: The data is invalid. The FD, SD and Directory are all version 16.2.4 |
|
|
I looked into this more. It seems like the Windows client uses its own special filestream format by default. The trouble is that plugins don't necessarily produce a stream in that format... but it seems to be assumed that they do. You can force the backup to be marked appropriated by adding "Portable = yes" to the file set configuration. This will allow the files produced by the plugin to be restored by clients without the plugin installed. Here's an example of a FileSet configuration: FileSet { Name = "SelfTest" Enable VSS = no Include { Options { Signature = MD5 Portable = yes } Plugin = "python:module_path=C\\:/Program Files/Bareos/Plugins:module_name=bareos-fd-eric-mssql:backuppath=C\\:/bareos-dumps:mssqlserver=(LOCAL)/SQLEXPRESS:mssqluser=bareos:mssqlpassword=bareos:db=example" } } I'm not knowledgeable enough about Bareos to know if this would be considered a bug or if it's assumed that you would know to configure your file set appropriately. There's more information on the topic of data stream portability here: http://www.bacula.org/5.1.x-manuals/fr/main/main/Windows_Version_Bacula.html |
|
|
plugin backup need plugin restore |
- Anonymous
