Submitted by Richard on Tue, 07/23/2013 - 16:52
A rule I follow is that when you need to use a backup, you probably will need it very badly. Here are my 10 best practices for setting up Drupal site backups so that when (not if) the day comes you need to do a restore, you will be able to recover with minimal downtime and impact.
#1 : Name a person (not a team) who is personally accountable for monitoring the backup process. This doesnt mean that person is doing the backups or fixing the process if it breaks down, but it is that persons job to ensure that alerts from backups are resolved and has tribal knowledge of how the backup process works.
Click read more for Best Practice #2 to #10 ...
Submitted by Richard on Sun, 03/03/2013 - 14:18
I was recently involved in a trouble shooting exercise where an application was giving terrible response times and frequent connection timeouts to visitors. This particular application has peak traffic demands during the business day and very few users overnight. From the checks I made using top and process status reports, it was easy to see that this virtual linux machine was saturated. Multiple virtual CPUs running 99% user+system and a run queue length over 30.
Click read more for why adding more vCPUs was not a good idea.
