Skip to content
DiscVaultDiscVault Docs

Update and migrate: Overview

Goal and result

Section titled “Goal and result”

Use a gated sequence for backup, update, verification, and rollback.

Applies to

Section titled “Applies to”

Stable and beta use the same v26 PostgreSQL-backed topology. Change only DISCVAULT_IMAGE; review release notes and keep a matched PostgreSQL and /data backup before any update or channel switch.

DiscVault v26 stable

Section titled “DiscVault v26 stable”
  • DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
  • one v26 backup/update/restore topology

DiscVault v26 beta

Section titled “DiscVault v26 beta”
  • DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
  • one v26 backup/update/restore topology

Prerequisites

Section titled “Prerequisites”
  • matching backup set
  • release notes and recorded immutable image digest

Procedure

Section titled “Procedure”
  1. Back up: Update and migrate: Backup · matching backup set
  2. Test: Update and migrate: Restore · restore rehearsal
  3. Run: Update and migrate: Container update · DISCVAULT_IMAGE
  4. Preserve: Update and migrate: Image rollback · previous image + matching data

Task routes

Section titled “Task routes”

Expected result

Section titled “Expected result”

A backup is tested before pull/recreate, then health and data are verified.

  • the archive and dump are non-empty, readable in a restore rehearsal, and tied to an immutable image digest
  • the intended image digest is running, health is successful, and owner login, library count, and one media sample all pass

Safety and rollback

Section titled “Safety and rollback”

Next step

Section titled “Next step”

Update and migrate: Backup

Source and status

Section titled “Source and status”