When there are long-running queries, mysqbackup hangs there to wait for the completion of the queries. You know that the system has only user data on InnoDB and there is no DDL execution during the backup period. There is no update/alternation to tables with non-InnoDB storage engines.
Which two ways allow the MySQL Enterprise Backup to be executed without being blocked or without locking?
A. Running mysqlbqckup from a remote machine enabled you to back up the database without locking.
B. The locked phase at the end of a mysqlbackup run is short (maybe a few seconds) and does not disturb the normal processing of mysqld much. However, use – -single-user-mode to back up the longrunning queries to allow mysqlbackup to run successfully without locking.
C. There is no extra option. MySQL Enterprise Backup does this automatically by kicking out the longrunning queries.
D. The locked phase at the end of a mysqlbackup run is short (maybe a few seconds), and does not disturb the normal processing of mysqld much. However, use the – – only-innodb option to back up only InnoDB tables, to avoid blocking.
E. The locked phase at the end of a mysqlbackup run is short (maybe a few seconds), and does not disturb the normal processing of mysqld non-InnoDB files.
Note that MyISAM, .frm, and other files copied under the –no-locking setting cannot be guaranteed to be consistent, if they are updated during this final phase of the backup.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
Answer is DE