Back up and restore
Tape's library database holds playlists, history, notes, ratings and edits that may not be stored in your music files. Back up both your music and the hub's data; one does not replace the other.
Before changing anything
Keep a copy of the hub data directory. The installed app normally uses ~/.music-hub; Docker uses the host folder mounted at /data. A development build or custom deployment can use another data directory. Use the location for the hub you are actually repairing.
Automatic database snapshots are normally kept in the data directory's backups folder. They protect database state, not your music files. Configuration, connection identity and license state also live in hub data and are not replaced by a database-only backup.
For a manual folder copy, quit Tape or stop the container gracefully first, then copy the whole data directory to a separate location. Do not copy only music.db while the hub is writing: SQLite may still have changes in its WAL file. Preserve the original data when moving to another machine and use license recovery if activation is bound to the old installation.
Restore a database backup
- Open Tape on the hub. In Docker, open its authorized local web interface.
- Open Settings → General → Restore from backup.
- Choose a snapshot from before the problem and check its date.
- Confirm the restore and wait for the library to reopen.
- Check a known playlist, a track note and recent history. Files added or edits made after the snapshot may need to be added again.
Restore replaces the current database state with the snapshot. It does not download or replace your music files. If the files have moved, keep the database and fix the folder location separately.
If restore is unavailable or fails
Install the current supported app version if the problem began after an update. Preserve the data directory and send diagnostics to support. Do not delete the database to make the app start.
For operators, the API reference describes listing backups and restoring a selected snapshot. These are administration operations, not a phone reconnection fix.
Rebuild is the last option
A rebuild creates a new database and scans the files again. It can lose playlists, history, notes, ratings and metadata saved only in the old database. Tags already embedded in supported audio files can be read again, but that does not restore every library edit.
Tape retains an archive of the old database when possible. That archive is a recovery aid, not a promise that the rebuilt library keeps its old state. Rebuild only if restore has failed and you accept these consequences; contact support first if you need help.
Check your backup
Use a spare profile or machine for a restore check. Confirm that your backup can open and that it contains the state you need. Do not test a restore by overwriting your only working library.