Drupalcon Blog

Dev/test/prod environments
Drupal's cluster
Dual loadbalancers
2 web nodes
2 db servers
Read write patch to core allows multiple db servers
147160 - node on drupal
Other ways to handle it
sql relay
Mysql proxy
Source control
Under each client folder
Under each project folder
Docs folder
Private files folder
Db dumps folder
Sql replication back to dev environment
Same php ini files, apache version/config, and mysql version/conf
Automated deployments
Cfengine
Define classes with declarations on them. Define class about apache with file locations and services.
When the class is changed, anything with that class is updated.
Relationship based
Academic based
Osu.osl.org?
Puppet will be evaluated.
Code vs. Content migrations
Make a rollback plan even on production.
unt with separate backup plan
Planning and tracking enhancements upgrades and fixes
Have backout plan. Allow time to watch it fail and restore
Unfuddled, track - docs for svn
Eliminating unscheduled downtime
Not dependent on one server
multiple db and web servers
Nightly backups with binary logs as well
Copy the db files themselves so its just an rsync instead of sql
Main server gets overloaded and fails over to weaker box amd complicates things
Osuosl.org
To reduce downtime, learn from the downtime you do have
Cacti
Plugin for mysql - temysql
Files directory nfs mount with separate backup plan