Podcast: Play in new window | Download

Be the hero when disaster strikes, have a disaster recovery plan.

News/Follow-Ups – 02:25

• Twitter gets picky about “twitter” and “tweet”
• Drop.io gets aquired

Geek Tools – 11:13

• Cable Lock Keyring – Keyring made of cable and threaded connectors

Webapps – 15:28

• Visualizations.org – Collection of visualizations and data sources
• Klout – A twitter influence-o-meter

Disaster Recovery – 22:18

• Analog Preparation
  • Documents should be in a secure location
    • Safety Deposit Box
    • Fire Safe
  • Keep digital scans of important documents
• Digital Preparation
  • How fast can you get your site back up if godzilla destroys your data center?
  • What does it cost you if your site is down for 1min? 1hr? 1 day?
  • Recovery Point Objectives
    • How much data can we afford to lose?
  • Recovery Time Objectives
    • How long can we spend getting it back?
  • Backup Data
    • Full DB backups
      • mysqldump
    • 3-2-1 3 backup copies (not including original) 2 different storage media, 1 off-site
  • Test your recovery plan on production
  • Documentation of your infrastructure
    • Server configs
    • Readme
      • IP Addresses
      • Installed software
        • dpkg-get-selections >/var/backup/package_list
      • Installed plugins
  • If you store files use SAN or Amazon S3
  • Monitoring and logging
    • When did it go down?
    • Were you notified?
    • Why did it go down?