Comment 5 for bug 1184888

Well the path I wrote from my.cnf is on the source, and the destination
also for that matter.

On Wednesday, May 29, 2013, Raghavendra D Prabhu wrote:

> @Rocoo,
>
> What is the my.cnf on source host - just to check if
> backup-my.cnf is generated correctly. To see if it is bug in
> that.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1184888
>
> Title:
> innodb_doublewrite not copied back to proper location
>
> Status in Percona XtraBackup:
> New
> Status in Percona XtraDB Cluster - HA scalable solution for MySQL:
> New
>
> Bug description:
> innobackupex: back to original data directory '/data/mysql'
> innobackupex: Copying '/backup/2013-05-28/innodb_doublewrite' to
> '/data/mysql/innodb_doublewrite'
>
>
> /etc/mysql/my.cnf:
>
> innodb_doublewrite_file = /log/mysql-bin/innodb_doublewrite
>
> Ubuntu deb installed.
> ii percona-xtrabackup
> 2.1.3-608.precise
>
> Not sure if it's a problem or not (That the doublewrite file will be
> missing). InnoDB log files are copied to correct destination.
> innobackupex: back to original InnoDB log directory '/log/mysql-bin'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1184888/+subscriptions
>