About xtrabackup2.0(copy-back)
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/
-------
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_
647 if_directory_
648 if_directory_
↓
▼After
645 # check that original data directories exist and they are empty
646 ###if_directory
647 ###if_directory
649 ###if_directory
-------
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-bin = log_bin/log_bin
log-error = log_system/
slow_query_log_file = log_system/
-------
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Alexey Kopytov
- Solved:
- Last query:
- Last reply: