These are the guides for the supported systems
There's an article that explains how to restore a backup if needed in this page
OS | Version | Architectures | Lifecycle |
---|---|---|---|
Windows Client | 7 SP1(*), 8.1 | x64, x86 | Windows |
Windows 10 Client | Version 1607+ | x64, x86, Arm64 | Windows |
Windows Server | 2012 R2+ | x64, x86 | Windows Server |
Windows Server Core | 2012 R2+ | x64, x86 | Windows Server |
Nano Server | Version 1809+ | x64 | Windows Server |
* Windows 7 SP1 is supported with Extended Security Updates installed.
OS | Version | Architectures | Lifecycle |
---|---|---|---|
Alpine Linux | 3.11+ | x64, Arm64 | Alpine |
CentOS | 7+ | x64 | CentOS |
Debian | 9+ | x64, Arm32, Arm64 | Debian |
Fedora | 32+ | x64 | Fedora |
Linux Mint | 18+ | x64 | Linux Mint |
openSUSE | 15+ | x64 | OpenSUSE |
Red Hat Enterprise Linux | 7+ | x64 | Red Hat |
SUSE Enterprise Linux (SLES) | 12 SP2+ | x64 | SUSE |
Ubuntu | 21.04, 20.10, 20.04, 18.04, 16.04 | x64, Arm32, Arm64 | Ubuntu |
OS | Version | Architectures |
---|---|---|
macOS | 10.13+ | x64 |
If you need to restore a backup, do not fret. It is incredibly easy.
There are two ways to approach a backup.
First, if you are seeing errors on an update to a new version, you can get an old version of your database from config/temp/version/kavita.db
This is a quick backup that occurs when database migrations are needed on an upgrade. You can just copy and paste this over your database in config/ and retry.
If you however have some bad data and need to restore, then check config/backups
for a zip of all user data. The scheduled backup (server settings) will save your database, appsettings.json, covers, themes, and bookmarks. You just need to copy and paste these over the config folder and restart.