Hello,
you don't have to put the mysql datadir into the fileset File= ..
definition, in fact that would increase you backup.
The documentation says:
|FileSet { Name = "client-data" Include { Options { compression=GZIP
signature = MD5 } File = /etc #... Plugin =
"python:module_path=/usr/lib64/bareos/plugins:module_name=bareos-fd-percona"
} }|
The important part is:
|Plugin =
"python:module_path=/usr/lib64/bareos/plugins:module_name=bareos-fd-percona"|
While the line "File = /etc" is kind of optional, to make sure to also
have your config in the backup - but it is a little bit misleading here,
as it has nothing to do directly with the plugin.
The percona plugin itself needs to know where the mysql datadir resides,
it uses /var/lib/mysql/ as default value. If you need to change it, you
have to carefully adapt the whole dumpoptions settings - see documentation.
Regards
Maik
Am 01.06.2017 um 16:32 schrieb [email protected]:
> On Thursday, May 25, 2017 at 1:10:21 PM UTC+3, [email protected] wrote:
>> Hi,
>>
>> I set up a bareos 16.2.4 server on CentOS 7.
>> I also installed the percona plugin on the client:
>> xtrabackup version 2.4.6 based on MySQL server 5.7.13 Linux (x86_64)
>> (revision id: 8ec05b7)
>> Mysql version: 5.6.12-log MySQL Community Server
>>
>> the size of the /var/lib/mysql is 390GB.
>>
>> I set the incremental level of backup to File storage.
>> The first backup is naturally Full level and what I get is this:
>> For the first 2 hours of running the job nothing happens, except for the
>> storage file, which is growing.
>> When the file is about 400GB+ it says:
>> python-fd: Starting backup of /_percona/xbstream.0000000591
>> And the file continues to grow. Eventually, the job finishes and the job
>> size is 835GB!! That's more than twice the size of the original database.
>>
>> Additionally, when running the subsequent jobs, i.e. incremental level - the
>> size of the backup is about 353GB.
>>
>> I want to mention that 99% of the tables are InnoDB. And the size of MyISAM
>> is no more than several hundreds of megabytes.
>>
>> The changes to the database are no more than 1GB/day.
>>
>> Another thing, I have a table in one database that is about 250GB in size.
>> It's InnoDB. There are definitely some changes during the day. But not
>> gigabytes.
>> When I access the restore page in UI - in Incremental I see this table but I
>> see it as 250GB, i.e. full size. Is this normal?
>>
>> Anyway, it's not really how it's intended to work, is it?
>> What am I doing wrong?
>>
>> I didn't want to flood with configs, so just tell me what info do you need
>> and I'll provide.
>>
>> Thanks,
>> Leon
> So I'm going to answer this myself.
> Please disregard everything I wrote about the reasons for the huge sizes.
> I don't know what was going on in the background,
> but eventually it was the wrong configuration of the fileset.conf
>
> You would expect that you should put the mysql datadir in the the "file" line,
> but just like it's in the conf example in the readme - it's "/etc".
>
> This must be documented in a very clear way, otherwise, for those of us who
> don't just copy/paste - this can be a nightmare.
>
> Thanks
>
--
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.
