Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":2417,"date":"2019-06-17T19:06:43","date_gmt":"2019-06-17T19:06:43","guid":{"rendered":"http:\/\/minervadb.com\/?p=2417"},"modified":"2020-02-04T03:17:08","modified_gmt":"2020-02-04T03:17:08","slug":"using-mariadb-maxscale-for-archiving-mariadb-database-with-mq-and-tee-filters","status":"publish","type":"post","link":"http:\/\/minervadb.com\/index.php\/2019\/06\/17\/using-mariadb-maxscale-for-archiving-mariadb-database-with-mq-and-tee-filters\/","title":{"rendered":"Using MariaDB MaxScale for Archiving MariaDB Database with Mq and Tee filters"},"content":{"rendered":"

Archiving MariaDB Database with Mq and Tee filters<\/b><\/span><\/h1>\n
\n

This whitepaper is about how to use MariaDB MaxScale filters for Archiving MariaDB database. We have considered two MariaDB \/ MySQL servers in this exercise, one is the <\/span>MariaDB Production Database Server<\/b> and other one for <\/span>Archiving MariaDB Production Database Server <\/b>. We have also accommodated <\/span>RabbitMQ<\/b> and <\/span>MariaDB MaxScale<\/b> servers in their respective Instances .<\/span><\/span><\/p>\n

 <\/p>\n\n\n\n\n\n
Instance Details<\/b><\/span><\/td>\nIP<\/b><\/span><\/td>\n<\/tr>\n
MariaDB Production Database Server<\/span><\/td>\n192.168.56.101<\/span><\/td>\n<\/tr>\n
MariaDB Archive Database Server<\/span><\/td>\n192.168.56.102<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Our use case is a MariaDB Production Database Server and MariaDB archive Database Server where only <\/span>INSERT<\/b>, <\/span>UPDATE<\/b> AND <\/span>DELETE<\/b> statements are routed. <\/span>The queries routed to the archive servers are also transformed into a canonical format and sent to a RabbitMQ broker for analysis. This setup allows us to control what we send to the server and could possibly allow us to filter out DELETE statements completely, making the archive server a true archive of all data.<\/span><\/span><\/p>\n

\"\"<\/a><\/p>\n

Reference source – MariaDB.com\u00a0<\/span><\/p>\n

\n
\n

Table of Contents<\/p>\n<\/i><\/a><\/span><\/div>\n