We’ve had several customers come to us recently with questions about backing up data so we thought we’d 1) share with you some information about what we do and 2) give you some advice on what you can do to ensure your data is safe.
First, we thought we’d share what we do about backups. The safety of your data is as important to us as it is to you and to that end we perform regular backups of all the information you store in QuickBase. We maintain those backups on your behalf to protect you in the event that anything happens to our servers. So if we do something to cause data loss, then we’ve got you covered and will restore your data at no cost to you.
Second, if you want to take matters into your own hands, there are several things you can do to add additional protection from any mistakes you or your team make. More specifically:
1) You can subscribe to our “restore package”. Think of this as an insurance policy against your team making a mistake. Once you’ve upgraded your subscription to include this add-on, then all you need to do is request a previous version of your data by submitting a support case at any time. The additional cost of this is $50 per month and it allows you to request up to 4 restores per year. If you don’t want to sign up for the “restore pack” and you need a restore, we still can do it, but we will need to charge you $1000 for that. The reason we end up having to charge for this is because there are many ways people mess their applications up (e.g. deleting tables, deleting single fields, etc) and restores can be quite time consuming. If you want help purchasing the “restore package”, just submit a support case and we’ll walk you through it.
2) You can make regular copies of your data. This can be done manually by creating a copy of your application, or you can automate it by making a call to the API_CloneDatabase API call. For more information on the API call, checkout our API documentation.
3) You can leverage QuickBase Desktop, a utility that sync’s QuickBase data to Microsoft Access. For more information on that, you can read our knowledgebase article.
Please feel free to reach out to the support team if you have any questions or want some advice on which approach might be best for you. We hope this helped.