Backup Strategy

From aMember Pro Documentation
Revision as of 20:01, 27 December 2016 by Jenolan (talk | contribs)
Jump to: navigation, search

How many Backups and Frequency

Normally you should have a daily backup, if possible this should be copied to a remote location in case of server catastrophic failure. Do not rely on a single backup, if you have an error it is likely the last backup may not be valid so follow a regime something like this;

  1. Daily backup --- keep for seven days
  2. Weekly Backup --- keep two as at Sunday (or whatever day)
  3. Monthly Backup --- keep two as at the beginning of each month

This may seem excessive but it allows you to roll back safely past any major problem, at the very least keep three days of rolling backups plus one at an important check point. You can also keep a full backup and then keep daily database backups until you change site files then re-download a full backup and again take daily backups of your databases.

Backup Locations

  • Local (Server)
  • Remote (Like AWS S3)
  • Download

Things to remember

  • Developer pre-backup
    Whenever you have someone working on your site make sure that you have a full backup
  • Upgrades
    before performing upgrades whether to aMember, WordPress etc do a full backup as well


Always make sure that any site customisations have been copied somewhere safe, a simple ftp download of these items can save you an enormous amount of time if they are accidentally lost/deleted during other site work.

  • Themes
  • CSS
  • Code Customisations

Other Issues

  • Set email to something like google apps So if the server is down email still works.
  • Set DNS on AWS Route 53 so that you can quickly redirect your web site to another server, also for the email option above