Avoid losing your application data (all of your teams, projects, APIs, etc.) by regularly backing up your data.Apidog primarily uses a single SQL database to store most of its runtime application data. Therefore, backing up this database will safeguard most of your data. You can use this backup to restore your Apidog installation if anything goes wrong (e.g., during an upgrade).
If you're hosting your own MySQL/MariaDB database, simply follow the same instructions you would use for making any normal database backup. For example, if you're using MySQL for your application database, you should follow MySQL's instructions for backing up your database.As long as you have a dump of the Apidog database, you should be good to go.
Amazon has its own best practices on how to backup and restore RDS databases, so we'll defer to them. We recommend that you enable automated RDS Backups.Instructions can be found in the Amazon RDS User Guide.
However, some data, such as automated testing team reports, user-uploaded files, and project icons, are not stored in the database.If you have configured an object storage service, these data will be stored on the object storage service. You can refer to the backup method of this service to back up these data. For example:
Amazon has its own best practices on how to backup and restore S3 data, so we'll defer to them. We recommend that you enable automated S3 Backups. Instructions for S3 can be found in the Using AWS Backup for Amazon S3.
Minio also provides its own best practices for data backup and restore. You can find more information in the Minio Documentation.
If you have not configured an object storage service, Apidog will store these resources in a file-based manner by default. You need to back up these files regular (especially backups before upgrading).
