You are here

AMS Cloud Backup Strategy

Subscribe to Syndicate
The following lists the backup strategy for private cloud databases in Montreal:
  • ONSITE at Data Centre
    • Streaming Replication: every database transaction is replicated on a 24x7 basis to second database server on another machine so that latest transaction is always on second sever. This serves as generally instant-on response in case of total failure of one machine.
    • 2 Daily Snapshots: are made and put on 3rd machine. The purpose is to provide redundancy in case the two primary master/slave machines die at exactly the same time. This allows restoration of a database that is no more than 12 hours old - and 30 daily copies are kept of snapshot backups
    • 24 Month End Backups: The backup process is designed to retain at least 2 years of monthly backups at the data centre
  • OFFSITE at another location
    • 7 Days of Offsite Backups: 7 days of daily snapshots are saved at an offsite FTP server in 'live mode' (i.e. 14 backups). This is in case there is a physical unforeseen act of god at the data centre (eg fire, insurrection, etc).
    • Recyclable NAS Storage: The offsite backups are also saved to a separate NAS box and stored until the device runs out of space and older backups start to recycle. This provides typically months worth of offline backups that take a little longer to access
    • ** periodically, the offsite backup cycle may get reset and the storage retention start again as they are not the primary backup
  • Customer Backups at location of their choice
    • Personal Backups: Each venue, per contract, can have a copy of the database sent to them daily by FTP, they just need to make and ftp site. The venue can specify how many days they want to keep and we’ll delete anything older -- The customer can pick that retention period