Improve Restore UX in Disaster Recovery and Backup pages

[DavidePrincipi]

The restore experience across Disaster Recovery and Backup pages is currently fragmented and unclear, especially on single-node clusters and when transitioning from disaster recovery to standard restore operations.

Scope

• Disaster Recovery (single-node clusters)
  • If no additional disk is present, behavior remains unchanged.
  • If an additional disk is present:
    • Only core applications are selectable for restore (Loki, Traefik).
    • Metrics is excluded (it has no backup).
    • A notification explains that other applications can be restored later from the Backup page.
• Backup page
  • Improve visibility and clarity of applications without backup:
    • Missing applications are clearly listed.
    • Users can add them to an existing schedule or create a new one.
  • Refactor layout to better highlight the restore use case, especially when accessed after a disaster recovery flow.

Acceptance Criteria

• Restore behavior is unambiguous for single-node clusters with or without additional disks.
• Users are explicitly informed when non-core applications must be restored from the Backup page.
• The Backup page clearly shows which applications lack backups and provides actionable options.
• After disaster recovery, restored applications are already scheduled for backup as they were in the original cluster.
• Restore actions are easy to discover when arriving from a disaster recovery flow.

See also

• https://mattermost.nethesis.it/nethesis/pl/p8uu8moi47rbxcmg58ersjcywc