Slave Database
 

Heya,

Planning to implement a master-slave setup for vBulletin using the built-in functionality for it; I'm curious, if the slave becomes unavailable, does the site then become inaccessible, or is there a way around that?

For example, we run nightly backups that normally make the site inaccessible for 20-30 minutes due to the size of the DB at 11 million+ posts, was thinking this might be an excellent way around the problem.

A slave database is used of offload some of the work to a secondary database. If you use this, both database must be available.

Do you think it would it be reasonable to have a script to say, write the vb config file to disable the slave accesses, then perform the backup and re-enable?

Having files writable would already decrease security.

By a script I mean a shellscript run on cron, not a php script.