Hello Dan,
I am trying to do full and incremental backup using percona plugin but i am
not sure about the process what are the plugins python file to be stored
under /usr/lib64/bareos/plugins and what is the updated material on those
files?
On Monday, 28 November 2016 at 22:50:54 UTC+5:30 Dan
Hmmm. Dang autocorrect.
I did not resolve this problem. I honestly decided not to spend any more time
on it. As I noted in my post, the workaround is to restore each of the backups
(full and each incremental since full) individually. The Percona process
doesn’t change, so the only added eff
Leon -
I did not resolve this problem. I honestly decided not to spend any more time
on it. As I noted in my post, the workaround is to restore each of the backups
(full and eat incremental since full) individually. The Persona process
doesn’t change, so the only added effort is in doing mul
On Monday, November 28, 2016 at 7:20:54 PM UTC+2, Dan wrote:
> Denis -I'm able to backup successfully, both full and incremental. I am also
> getting the "Error: No lsn information found in restore object for file
> /tmp/bareos-restores/..." error on restore. I can actually restore
> successfu
Hello Dan,
sorry for delay.
I add the configuration for a user with privilege to write on db (in fact
root), like this:
[mysql]
user=root
password=lamiapassworddiroot
nient'altro.
On Mon, Nov 28, 2016 at 6:20 PM, Dan wrote:
> Denis -I'm able to backup successfully, both full and incremental.
Denis -I'm able to backup successfully, both full and incremental. I am also
getting the "Error: No lsn information found in restore object for file
/tmp/bareos-restores/..." error on restore. I can actually restore
successfully if I individually retire the full and each incremental and then
Hi Denis,
thanks for clarification!
You are right: the plugin needs better error-handling and
error-messages. I will keep this in mind for the next release.
Regards
Maik
Am 14.11.2016 um 11:01 schrieb Denis Barbazza:
> ok :( I found it, my mistake.
> in .my.cnf i wass missing the part regardi
ok :( I found it, my mistake.
in .my.cnf i wass missing the part regarding mysql command.
Maybe you can add a test in BareosFDPercon to check if mysql command can
login correctly without error.
Hope that this thread can be useful for someone else in the future ;-)
On Mon, Nov 14, 2016 at 10:50 AM
Hello Maik,
another update. I've tried the same setup in debian jessie with
percona-xtrabackup-22 and it works.
both incremental and full backup.
I've tried also restore and it restores all the files.
So now it seems an incompatibility of python or mysql version, in my setup
i've this:
jessie:
mysq
Hello Maik,
if you need some test or more detailed debug let me know.
I will be happy to help you.
thank you for your work
On Thu, Nov 10, 2016 at 8:42 AM, Maik Aussendorf wrote:
> Hi,
>
> both problem reports here refer to Debian / Ubuntu, while the
> development and (customer) production envi
Hi,
both problem reports here refer to Debian / Ubuntu, while the
development and (customer) production environment was RedHat/Centos (7).
So I have to reproduce the behavior in a Debian / Ubuntu environment;
which will take some time.
> Hi all
> I have same trouble, can't restore full backup.
>
вторник, 8 ноября 2016 г., 16:56:17 UTC+6 пользователь maik.aussendorf написал:
> Hello Denis,
>
>
>
>
>
> Am 08.11.2016 um 10:57 schrieb Denis
> Barbazza:
>
>
>
>
> Hello Maik, thank you for your reply.
>
>
>
>
>
> I found the p
>
> it seems that it can't recognize last lsn.
>
> Yes, that seems to be the problem.
>
> echo 'SHOW ENGINE INNODB STATUS' | mysql -r
> It should contain a line like
> Log sequence number 14882332
>
> Can you post that line (or the whole result)?
>
Here the whole result:
# echo 'SHOW ENGINE INN
Hello Denis,
Am 08.11.2016 um 10:57 schrieb Denis Barbazza:
> Hello Maik, thank you for your reply.
>
> I found the problem, it was so simple, damn :-(
> the client cannot reach the storage daemon, I discovered it because
> when I run a file backup it simply told me :(
Good.
>
> But
>
> Now
On mardi, 8 novembre 2016 10.57:48 h CET Denis Barbazza wrote:
> another strange thing is that the full mysql backup has 2 files and 1GB,
> but if I click on "show files" I can see only _percona/xbstream.0XX
> is this normal? I should have also xtrabackup_checkpoints I think... or I'm
> wrong?
Hello Maik, thank you for your reply.
I found the problem, it was so simple, damn :-(
the client cannot reach the storage daemon, I discovered it because when I
run a file backup it simply told me :(
But
Now I was able to make a full backup, size is approsimately 1GB (it could
be real).
The
Hello Denis,
Am 04.11.2016 um 11:43 schrieb Denis Barbazza:
> Hello,
> I'm trying to setup a new backup server with bareos 16.2.4 and a
> client with same version and percona-xtrabackup plugin, but I run into
> trouble :(
>
> I'm running Debian Stretch and I followed the guide here:
> https://git
Hello,
I'm trying to setup a new backup server with bareos 16.2.4 and a client
with same version and percona-xtrabackup plugin, but I run into trouble :(
I'm running Debian Stretch and I followed the guide here:
https://github.com/bareos/bareos-contrib/tree/master/fd-plugins/bareos_percona
My perc
18 matches
Mail list logo