Backup and Restore
FaceAPI includes three stateful components that store data, such as:
In this article, find out how to perform backup and restore operations for all these components.
Info
In addition to creating backups, it is strongly recommended to regularly check the state of your data and ensure the ability to recover quickly.
Relational Database
FaceAPI supports multiple relational databases, each with its own backup and restore mechanism.
| Database | How to back up and restore data |
|---|---|
| SQLite | This database is a single-file database, and the recommended approach for backup and restore is to copy the database file to another location and paste it back when needed. |
| PostgreSQL | Open documentation |
| MariaDB Server / MySQL | Open documentation |
| Oracle | Open documentation |
| Microsoft SQL | Open documentation |
Storage
FaceAPI supports various storage types for data persistence. When using cloud providers or specific storage solutions, always refer to the respective documentation and best practices for optimal backup and restore procedures.
| Storage | How to back up and restore data |
|---|---|
| File System | Ensure regular backup and restore procedures for the file system. |
| AWS S3 | Open documentation |
| Google Storage | Open documentation |
| Azure Storage | Open documentation |
If MinIO is used as an S3 alternative, it is recommended to implement an Active-Passive Disaster Recovery strategy. Replicate data using MinIO Server-Side Replication, see MinIO documentation for details.
Milvus Vector Database
Milvus, as a vector database, stores backups on S3. Use the Zilliztech utility for copying and restoring Milvus data, see Milvus documentation for instructions.