## Why
The info screen lists backups but cannot restore one, so you need the web UI for restores.
## Proposal
From the backup list, restore the selected backup with one of two choices:
1. **To a new VMID.** This is the safe default: the next free ID from `get cluster nextid`, and the original guest is untouched.
2. **Over the existing guest.** This is destructive, so the guest must be stopped and you must type the VMID to confirm.
## cv4pve-cli (2.4.0)
- `do restore`. Check its subcommands and syntax with `--help`.
- `get cluster nextid`
## Risks
Restoring over a guest overwrites it completely. That is why this is low priority and needs the strictest confirmation in the app.
## Done when
- Restore to a new VMID works and is live-tested with CT 104's backup to a new ID. The new guest is deleted afterwards, with the user's approval.
- Overwrite has a typed confirmation.
- Tests are written first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
The info screen lists backups but cannot restore one, so you need the web UI for restores.
Proposal
From the backup list, restore the selected backup with one of two choices:
get cluster nextid, and the original guest is untouched.cv4pve-cli (2.4.0)
do restore. Check its subcommands and syntax with--help.get cluster nextidRisks
Restoring over a guest overwrites it completely. That is why this is low priority and needs the strictest confirmation in the app.
Done when
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com