The replication filter you have in place

Replicate_Wild_Do_Table: zo_dev_matrix.*

is actually a little misleading. In the MySQL Documentation, the legal characters for wildcards are %, _ and \_. (If you want to interpret a literal underscore). The asterisk character is not listed. The above filter is actually looking for a table called zo_dev_matrix.*. Therefore, you have two options

OPTION #1

Correct the filter in my.cnf to have this

[mysqld]
replicate_wild_do_table = zo_dev_matrix.%

OPTION #2

Change the filter to the database zo_dev_matrix

replicate_do_db = zo_dev_matrix

only if all your queries do no preface the table with the db and you explicit set the current database to zo_dev_matrix.

CAVEAT

With MySQL 5.6 and back, you must restart mysql after changing the filter in my.cnf. Starting with MySQL 5.7, you can create a dynamic replication filter so a mysql restart is not necessary.

1) Backups:

• You can verify if your backup is successful by tailing the mysqldump for "dump completed successfully" to verify the success of a mysqldump.

• Invalid backup is as-good-as (or as-bad-as) no backup. It's a good idea employ a backup-validation process by restoring it to a provisioned location as possible. Do it.

• If you want to stick to logical backup, try using with myduper/myloader, which will be quicker than mysqldump.

• Again physical backups are faster than logical and this is specifically true for large sizes. If you can giveup on MySQLDump which is slow for restores and especially if you have all-innodb, you should consider using xtrabackup from Percona (for hotbackup). Check installing and configuring xtrabackup with holland framework.

2) Restoring master from slave.

As such there are few questions and articles available but i will quickly notedown steps I can makeout for restoring master from slave.

• Considering your master is M and slave is S. (M --> S)
• M is down.
• S is promoted to Master ( readonly=false, binlogging is enabled)
• M is later fixed and ready to join but need a restore.
• Restore M from latest backup, mark it as readonly=true.
• Upon restore, make it slave of S. (S --> M)
• Once it catches up, you may want to failback to original master.
• Stop production traffic, Mark M as readonly=false, S as readonly=true.
• Mark S as slave of M (should be simple change master to from present binlog of M)
• Thus making them active-passive master-master pair.
• Move traffic to M.
• You might want to break the master-master but it's fine to keep active-passive.
• Making sure nothing writes to Passive master.

Hope this helps.