About xtrabackup2.0(copy-back)

Asked by kazushige uratani on 2012-04-11

Hello!!

Can I ask a xtrabackup2.0's question of 'copy-back'.

Although 'data dir' must be empty as specification of 'copy-back' of 'XtraBackup2.0',
since 'Fusion-io' is used, 'I/O' distribution has not been carried out in our project.

Therefore, directories, such as 'log_innodb', are created in 'data dir'.
Other directories are also the same.

The error is as follows.
----------------------------------------------------------------------------------------------
IMPORTANT: Please check that the copy-back run completes successfully.
           At the end of a successful copy-back run innobackupex
           prints "completed OK!".

Original InnoDB log directory does not exist! at /usr/bin/innobackupex line 564.
----------------------------------------------------------------------------------------------

Since it is checking with the 'copy-back' of 'innobackupex', the comment is used.
The error is as follows.
----------------------------------------------------------------------------------------------
innobackupex's copy_back function
▼Before
 645 # check that original data directories exist and they are empty
 646 if_directory_exists_and_empty($orig_datadir, "Original data");
 647 if_directory_exists_and_empty($orig_ibdata_dir, "Original InnoDB data");
 648 if_directory_exists_and_empty($orig_iblog_dir, "Original InnoDB log");

   ↓

▼After
 645 # check that original data directories exist and they are empty
 646 ###if_directory_exists_and_empty($orig_datadir, "Original data");
 647 ###if_directory_exists_and_empty($orig_ibdata_dir, "Original InnoDB data");
 649 ###if_directory_exists_and_empty($orig_iblog_dir, "Original InnoDB log");
----------------------------------------------------------------------------------------------

What do you think of this correspondence?
Moreover, be except this correspondence, and if there is a method, give me advice.

Thank you!!

The preset value of 'my.cnf' is indicated as reference.
----------------------------------------------------------------------------------------------
[mysqld]
datadir = /fio/mysql
innodb_log_group_home_dir = /fio/mysql/log_innodb/
log-bin = log_bin/log_bin
log-error = log_system/error.log
slow_query_log_file = log_system/slow-queries.log
----------------------------------------------------------------------------------------------

Question information

Language:
English Edit question
Status:
Solved
For:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB Edit question
Assignee:
No assignee Edit question
Solved by:
Alexey Kopytov
Solved:
2012-04-20
Last query:
2012-04-20
Last reply:
2012-04-11
Best Alexey Kopytov (akopytov) said : #1

Hello,

I'm not quite sure I understand the question. We've seen a number of requests to make the innobackupex requirement to have empty data datadir optional. Something like "innobackupex --copy-back --force". Would that be a solution to the problem for you?

Hello, Alexey.

"innobackupx" was rewritten according to its environment.
The problem of "copy-back" is solved now.
He would sometimes like to hear one.
For a sense.
Isn't there any option which does not become an error in the environment which creates a folder in a "data directory"?
except for an "force" option.

Sorry!!
He would sometimes like to hear one.

I would sometimes like to hear one.

Hello, Alexey.

We decided to create a "log directory" outside a "data directory".
Thank you.

Thanks Alexey Kopytov, that solved my question.