Ways to Back Up Your Stack Content
Backing up content means creating and maintaining copies of your stack’s entries and assets. Backups help when there is a natural disaster, or you accidentally delete content, or you want to go through some old deleted records.
There are several ways in which you can get your hands on deleted or lost content. Here are some of them:
Content Restore Through Support Team
Contentstack keeps a backup of your content for 14 days. If you want to restore the deleted content to anything beyond 14 days then we raise the request with the SRE team which is typically done in 3 to 4 business days. If you delete any content accidentally, our support team can help restore that content, if we have it in our backups. We have outlined a process of asking for restoring your content in a separate document, and we highly recommend you to go through it.
Currently, Contentstack follows the following data backup frequency:
- Every six-hour backup with 2 days of retention
- Daily backup with 7 days of retention
- Weekly backup with 30 days of retention
Back up Content Using Contentstack DataSync Utility
One of the best ways to ensure that you always have an updated backup of your data is to use our DataSync Utility. It allows you to sync your published data with your local database (filesystem or MongoDB).
So, every time you publish, delete, or update an entry or asset, the corresponding changes are made automatically on your database. Read more about Contentstack DataSync.
Create Backups in Your Local Storage System
You can set up webhooks that trigger on every create, update, delete or publish event, and write scripts that store this webhook data on your local storage system. This way, you'll always have the most updated backup of your content.
Periodic Back up of Stack Content Using 'Export' Script
This is another simple way to create back up periodically. Use the Contentstack Export script to export all the content of your stack in JSON files. You can do this periodically, and replace the earlier back up with the old ones or keep several backups. When required, you can either import content into any stack of your choice or use it in any other way.