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.
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].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
