eTapestry currently partners with two hosting providers for hosting services at two separate locations, where we house our server infrastructure and customer data. These are world class hosting centers with the expected level of security, fire suppression, and redundant power capabilities.

Backups are automatically triggered if the database was edited the previous day.  Since we only pull backups if the database differs from the previous backup on record, this prevents multiple backup copies of a database with the same information.  Typically backups start being pulled by the system around 12 AM EDT.

Customer database backups are taken at one data center and saved to disk storage at the other data center.  In the event of a failure at one data center, we can restore all of those customers to the most recent back up that was created at the other hosting facility. eTapestry has never had to do this, but it is a protection that is in place should it be needed. Additionally, key equipment such as database servers and network storage devices at these data centers are under platinum service agreements that include 24/7 response times should a critical issue arise.

Customers can always create their own database backups using queries and report.  Steps can be found here.

Frequently Asked Questions:
  1. How often do you test the process of restoring from a backup?
    • We perform database restorations regularly across all environments and can confirm that the process is stable.
  2. Where are backups stored and for how long are they there?
    • Backups are stored on a Storage Area Network (SAN) which are multiple Hitachi RAID devices on a network. They provide high availability through redundant data duplication. Even with multiple simultaneous hardware failures, data integrity will be maintained. Active client daily backup files live our servers for six months
  3. Do backups transfer to a different location after a certain amount of time?
    • Once a day, old backups are deleted from the SAN following certain rules. This is all handled in an automated fashion. All backups over six months old are deleted from the SAN. Only one full backup per month per database is kept on the SAN and only one incremental backup per week per database is kept on the SAN. The entire SAN is backed up to tape in a rotating basis such that all data is backed up at least once a month.