Thanks Stephan for all your helpful explanations. Now I understand
better the problems I had.
--------------------------------------------------------------------------------
Christian
------ Message d'origine ------
De : "Stephan Dühr" <[email protected]>
À : [email protected]
Envoyé 2015-02-26 10:25:00
Objet : Re: [bareos-users] Re: MySQL backup
On 02/26/2015 03:59 PM, Christian Tardif wrote:
Haven't been able to make it work completely. I've had some success
at doing the backup... but as I can't do the restore to file (don't
know why), I'm not sure at all the the backup actually succeeded.
list files jobid=<yourjobid>
in bconsole should show the file.
It's always helpful to post an error message and the relevant parts
of your config, otherwise it's hard for other users to help.
The main purpose of this mailinglist is to connect the users community
so that they can help each other.
http://www.bareos.org/en/howto-contribute.html
Regards,
Stephan
Anyway, I worked with the ClientRunBeforeJob and ClientRunAfterJob to
actually create the dump, backing it up, and then delete it. It even
allows me to do other stuff (like exporting my bareos
database outside of Bareos environment in case of severe Bareos
failure. More flexibility here.
Thanks anywayé
---
*Christian
*
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On 2015-02-25 17:20, Ashley wrote:
Hi Chirstian,
I had the same problem on 14.2.2. I switched to using the BPIPE
method as a workaround.
I assume this is a bug but i have not reported it.
Here is my bpipe file set:
FileSet {
Name = "Linux-MySQLServer"
Include {
Options {
Signature = MD5 # calculate md5 checksum per file
One FS = No # change into other filessytems
FS Type = ext2 # filesystems of given types will be backed up
FS Type = ext3 # others will be ignored
FS Type = ext4
FS Type = xfs
FS Type = reiserfs
FS Type = jfs
FS Type = btrfs
sparse = yes
}
File = /
}
Exclude {
File = /var/lib/bareos
File = /var/lib/bareos/storage
File = /mnt
File = /proc
File = /tmp
File = /.journal
}
Include {
Plugin = "bpipe:/MYSQL/AllDatabases.sql:mysqldump --opt
--all-databases:gzip > /var/tmp/bareosRestore.sql.gz"
Options {
signature = MD5
compression = gzip
}
}
}
--
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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Stephan Dühr [email protected]
Bareos GmbH & Co. KG Phone: +49 221-630693-90
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, M. v. Wieringen
--
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.
--
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.
