Web Server Disaster Recovery

You have a right to know what we would do in the case of a disaster!

No matter who you are dealing with you should know what would happen in the worst-case scenario!

Our Plan

• Regular backups.
  We perform a full system backup once every week.
• Automated status updates.
  We receive emails as soon as a server notices any unusual activity, as soon as there is heavy load that slows down our service, and a detailed report of every backup. This doesn't cover every scenario but it helps us prevent most problems before they happen.
• Emergency records.
  An "In Case of Emergency" folder is locked away with details of all accounts and contact information. Key people know about this and would be able to contact you in the very worst case scenario.
• Standards conformity.
  Unless you needed something special, our servers are based on industry-standard software. A few tweaks may be required (usually just a few settings that define where your site is located) but anything that works on our server should work on other Unix-based servers with Apache, PHP and MySQL which covers a majority of hosting companies.
  • Usage of operating systems for websites. (Ours are Unix-based.)
  • Usage of web servers for websites. (We use Apache.)
  • Usage statistics and market share of PHP for websites. (Most of our programming is in PHP.)
  • Database engines ranking. (We use MySQL.)

These tips apply regardless of what company you choose to host your site.

This isn't just a good idea if you choose KolbeNet. Actually, we'll be honest about our plans for disaster recovery.

So here are some things you should always do to protect yourself:

• Keep backups.
  Make sure you have a backup of your website. Here's why:
  • Even businesses with a backup system in place can find that their backups have failed, or they may not have tested them in the first place!
  • Backup systems (including ours) backup the entire server. Extracting a single site from a backup is often difficult or impossible. If there is a problem with just your site, having your own backup may be the only way to recover!
  • If you have your own copy of your site then you know you're safe.
  (If we're hosting your site and you don't know how to do this then just ask and we'll be happy to email you an archived copy.)
• Backup your database. (if your site uses one)
  Okay, admittedly, this one is harder to do, but if your site uses a database you should try to get periodic backups. Ask whoever has designed (or is hosting) your site if there is an easy way to access this or have it automated.
• Keep your account information.
  Make sure you know your login information. Most places that host web sites don't have a record of this and in some cases it can be a hassle to change it. It's a lot easier if you have it readily available.
• Keep your passwords safe.
  This is more like "disaster prevention." However, we've seen people hang their password on the wall next to their desk in a place where anyone can see it. We notice it when somebody starts abusing the account when they never should have been able to login in the first place.