<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>WordPress &#8250; Support Topic: Trying to use HyperDB to replicate database</title>
<link>http://wordpress.org/support/</link>
<description>WordPress &#8250; Support Topic: Trying to use HyperDB to replicate database</description>
<language>en</language>
<pubDate>Tue, 24 Nov 2009 09:47:49 +0000</pubDate>

<item>
<title>figaro on "Trying to use HyperDB to replicate database"</title>
<link>http://wordpress.org/support/topic/219276#post-958255</link>
<pubDate>Sat, 17 Jan 2009 01:33:27 +0000</pubDate>
<dc:creator>figaro</dc:creator>
<guid isPermaLink="false">958255@http://wordpress.org/support/</guid>
<description>&#60;p&#62;I &#60;strong&#62;believe&#60;/strong&#62; hyperDB is intended to allow you to split your database tables into different databases and/or servers. It's used by a lot of people who run WPMU sites since Mu creates a new set of tables for every blog created. I have one (small) Mu site with over 400 blogs, so that results in a lot of tables in a single database. Therefore I use another multi-db script (based on hyperDB) to split the tables across 16 databases.&#60;/p&#62;
&#60;p&#62;So, I'm not sure hyperDB won't do what you're wanting to do, but I think it's intended to split up a db full of tables among several db's on the same server or on multiple servers...I'm not sure it's intended to replicate a db.....but, I could be wrong.
&#60;/p&#62;</description>
</item>
<item>
<title>d910qf on "Trying to use HyperDB to replicate database"</title>
<link>http://wordpress.org/support/topic/219276#post-958223</link>
<pubDate>Sat, 17 Jan 2009 00:21:53 +0000</pubDate>
<dc:creator>d910qf</dc:creator>
<guid isPermaLink="false">958223@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Hi - as far as I can tell you need to set up your mysql databases as normal (master/slave etc) and then list each database server in the settings file along with whether it is read only etc.&#60;/p&#62;
&#60;p&#62;For example you might have one database server that handles writes, and 2 that handle read only (I think they would normally be master and 2 slaves). &#60;/p&#62;
&#60;p&#62;Set up the config file with these settings and away you go.... &#60;/p&#62;
&#60;p&#62;Am testing at the moment, will report back.
&#60;/p&#62;</description>
</item>
<item>
<title>nemo-maritime on "Trying to use HyperDB to replicate database"</title>
<link>http://wordpress.org/support/topic/219276#post-904641</link>
<pubDate>Fri, 21 Nov 2008 14:17:08 +0000</pubDate>
<dc:creator>nemo-maritime</dc:creator>
<guid isPermaLink="false">904641@http://wordpress.org/support/</guid>
<description>&#60;p&#62;I am trying really REALLY hard to set up a replication of my database on a new server I added. I am almost dying with this, its killing me slowly! Sometimes it sucks being a website owner, anyways, I am trying to make a copy of my database. I have looked around and I have found sites like&#60;br /&#62;
&#60;a href=&#34;http://dev.mysql.com/doc/refman/5.1/en/replication-howto.html&#34; rel=&#34;nofollow&#34;&#62;http://dev.mysql.com/doc/refman/5.1/en/replication-howto.html&#60;/a&#62;&#60;br /&#62;
and &#60;a href=&#34;http://www.howtoforge.com/mysql_database_replication&#34; rel=&#34;nofollow&#34;&#62;http://www.howtoforge.com/mysql_database_replication&#60;/a&#62; and they are kind of easy, but at the same time confusing as I don't know what to use to imput these codes/requests. So I stumbled across HyperDB ( &#60;a href=&#34;http://codex.wordpress.org/HyperDB&#34; rel=&#34;nofollow&#34;&#62;http://codex.wordpress.org/HyperDB&#60;/a&#62; ), which looks like its made for WordPress, BUT, the installation guide really sucks; it barely explains anything. So I was wondering if anyone here in this huge world wide web of users has a better guide, or can help explain this, I would really appreciate it, as you will be saving me from going insane.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
