Skip to content
Weaver Docs

Backup And Restore

A backup is a downloadable bundle of everything that makes an instance yours except the downloads themselves. Export one before upgrading, before moving storage, and before rebuilding a host.

What A Backup Contains

Section titled “What A Backup Contains”

Settings, servers with their credentials, categories, API keys, RSS feeds, rules, and seen history, post-processing lists and options, the security settings, and history. Not included: active jobs, staged uploads, the intermediate directory, and every downloaded file.

Credentials are stored encrypted. The bundle carries the encryption master key, and the analysis reports whether the target instance can use it. An instance that supplies WEAVER_ENCRYPTION_KEY needs the same key on the target.

Export

Section titled “Export”

Open Settings → Backup and choose Download Backup. Enter a Backup Password to encrypt the bundle. Keep the password somewhere other than next to the file.

Restore

Section titled “Restore”
  1. On the target instance, open Settings → Backup → Restore Backup and choose the file.
  2. Analyze Backup. The preview shows the source data, intermediate, and complete directories, the schema version, whether it is password protected, any warnings, and whether this instance is ready for restore.
  3. Enter the new data, intermediate, and complete directories.
  4. Fill in Required Category Remaps for any category whose destination lived outside the old complete directory.
  5. Restore Backup. The state is staged with its history jobs. Restart Weaver to apply it.

Restore replaces the target’s settings, API keys, RSS state, and history. Restore into a clean instance rather than merging into a busy one.

Security Settings Travel With A Backup

Section titled “Security Settings Travel With A Backup”

Network access comes along: the listen address, the trusted proxies, the remembered-session networks, and on an install that predates 0.12.0, the browser-access policy and trusted networks. So does the access model itself. Restoring a backup taken before 0.12.0 puts the target on the older access settings, and setting WEAVER_ACCESS_MODE=authenticated moves it back. Review all of it when the new machine sits on a different network. A restored bind address the new host cannot bind does not stop startup: Weaver falls back to 127.0.0.1, logs a warning, and Settings → Security shows the address in force, where you correct it.

Section titled “Related”
  • Storage Layout explains category destination overrides.
  • Upgrading recommends an export before every upgrade.
  • Configuration documents WEAVER_ENCRYPTION_KEY and the backup upload limit.