RESTORE — putting configuration back
Raised by lemonfiber restore. Every one of these refuses before anything is overwritten except RESTORE-6 and RESTORE-10, which are the two that reach you with files already written.
| Code | Severity | Exit | What it means | What to do |
|---|---|---|---|---|
RESTORE-1 | error | 1 | The archive could not be read. Most often it is truncated, or is not a lemonfiber backup. Nothing was touched. | Check the archive, or restore from a different backup. |
RESTORE-2 | error | 1 | The archive was written by a newer lemonfiber than this one, and may hold configuration this version would not restore correctly. Nothing was touched. | Update lemonfiber to at least the version that made the backup, then restore. |
RESTORE-3 | error | 1 | The archive's format cannot be restored by this build. Restoring it could leave the configuration in a state neither version expects. Nothing was touched. | Restore it with the lemonfiber version that made it. |
RESTORE-4 | critical | 1 | The archive holds an entry naming a path that leaves the directory it belongs in, which a genuine lemonfiber backup never does. It is refused and nothing was touched. | Do not restore this archive. It is corrupt, or was tampered with. |
RESTORE-5 | warning | 1 | The archive was taken against a different data root. Restoring it unchanged would keep a setting naming a location that is not on this machine. | Re-run the restore with --repoint to accept moving it to this machine's data root. |
RESTORE-6 | error | 1 | The archive could not be unpacked, and the restore stopped part-way through writing the configuration back. | Check the configuration location is writable and restore again. A seed afterwards reconciles anything left half-written. |
RESTORE-7 | error | 1 | The stack was not confirmed stopped, so nothing was touched. A restore writes over the service databases, and an engine that will not say whether the services are running is refused as firmly as one that says they are. | Stop the stack, check the container engine is answering, then restore again. |
RESTORE-8 | error | 1 | The name you gave is not one of the backups kept here. A restore by name reaches one of the archives this machine took, which are files in a single directory; a name carrying a path, or climbing out of that directory, is refused rather than followed. Nothing was touched. | Ask for one of the backups by the name it was written under. |
RESTORE-9 | error | 1 | This run has nowhere it knows to look for a backup. Archives are kept in lemonfiber's own directory, and this machine would not say where that is. Nothing was touched. | Set a home directory for this user, then restore again. |
RESTORE-10 | error | 1 | The archive was unpacked, and the data root it recorded could not be changed to this machine's — so the settings that landed name a library that is not here. | Set the data root by hand, then run lemonfiber seed. |
RESTORE-11 | warning | 1 | What you agreed to is not what this backup would do now. A fresh look at the archive lists something else, so something changed between reading the listing and answering it. Nothing was overwritten. | Ask what the backup holds again, and read what it says now. |
RESTORE-12 | error | 1 | The archive holds a setup lemonfiber does not manage. It was captured before lemonfiber took over, so putting it back means writing into directories that are not lemonfiber's to write to. Nothing was touched. | Unpack it yourself with tar -xzf, into the paths the message names. |
What each severity and each exit means is on every error by code, beside every other family.