Hello,
Am 08.02.2017 um 20:29 schrieb Kjetil Torgrim Homme: > hello, I'm trying to use the Percona plugin. backup seems to work > (although I am not certain), on this test server the backup jobs says: > > FD Bytes Written: 6,513,699 (6.513 MB) > > mysqldump without compression is ~9 MB, the backup contains just one > file, /_percona/xbstream.0001457954 That's correct. It is the output from xtrabackup command in xbstream format. > > so, trying out restore: > > 08-Feb 19:28 dump-sd JobId 1457958: Forward spacing Volume "incr/Incr-6247" > to file:block 1:970713522. > 08-Feb 19:28 ece026-snapshot-fd JobId 1457958: Error: restore.c:1239 Write > error on /tmp/bacula-restores/_percona/xbstream.0001457954: Child exited with > code -268435457 > 08-Feb 19:28 ece026-snapshot-fd JobId 1457958: Error: Restore command > returned non-zero value: 1, message: Here after 'message: ' the stdError output of the xbstream is expected. > (if you wonder about the Incr name: I did the full backup to the > Incremental-pool for convenience - didn't want to have to wait for > tape.) > > the directory in the error message is left empty. > > I tried to grab the error message from xbstream, but was unable to patch > the python plugin to log it. however strace delivers the goods, sort You can try to use 'stdOut' instead of 'stdError' in line 347 (obviously stdErr is empty in you case). I will print both values in future versions. > of. the xbstream process reads and reads and reads, and then: > > write(2, "xb_stream_read_chunk(): invalid checksum at offset 0xa00025: > expected 0xf96cf5a6, read 0xc7ae89da.\n", 99) = 99 > > it doesn't look like the trace level 200 file from FD has much > interesting to say, but see attached file. > > at this point I would like to see if the problem is in the backup or in > the restore. can I extract the stream to a plain file on the client and > run xbstream on it manually? other hints on how to debug the problem? Yes, you can. E.g. restore to a client with plugins disabled, then you will get the plain xbstream-file. I suggest that you first check, that xtrabackup produces a valid stream that can be successfully used by xbstream again. If that works you can have a look about the stream going into Bareos and what comes back on restore. > > here are my versions: My development box is similar: Centos 7, Python 2.7.5, 5.5.44-MariaDB, percona-xtrabackup-2.3.3 and tested again with updated 2.3.6 Regards Maik > > * ece026-snapshot-fd Version: 15.2.2 (16 November 2015) > x86_64-redhat-linux-gnu redhat CentOS Linux release 7.0.1406 (Core) > > * percona-plugin from Git master today > > * Python 2.7.5 > > * mysql --version > mysql Ver 14.14 Distrib 5.6.30-76.3, for Linux (x86_64) using 6.2 > > * rpm -qf /usr/sbin/mysqld > Percona-XtraDB-Cluster-server-56-5.6.30-25.16.1.el6.x86_64 > > * rpm -qf /bin/xbstream > percona-xtrabackup-2.3.5-1.el6.x86_64 > > Bareos server: > > * dump-dir Version: 16.3.1 (01 July 2016) x86_64-unknown-linux-gnu > ubuntu Ubuntu 14.04.5 LTS (actually from Git, tag Release/16.2.4) > -- With kind regards // Mit freundlichen Grüßen -- Maik Außendorf [email protected] Bareos GmbH & Co. KG Phone: +49221630693-93 http://www.bareos.com Fax: +49221630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
