mirror of
https://github.com/netinvent/npbackup.git
synced 2024-11-10 09:03:02 +08:00
Update ROADMAP.md
This commit is contained in:
parent
4f7ecc267b
commit
ef9a26aa08
1 changed files with 23 additions and 6 deletions
29
ROADMAP.md
29
ROADMAP.md
|
@ -1,11 +1,11 @@
|
|||
## What's planned ahead
|
||||
## What's planned / considered
|
||||
|
||||
### Daemon mode
|
||||
|
||||
Instead of relying on scheduled tasks, we could launch backup & housekeeping operations as deamon.
|
||||
Caveats:
|
||||
- We need a windows service (nuitka commercial implements one)
|
||||
- We need to use apscheduler
|
||||
- We need to use apscheduler (wait for v4)
|
||||
- We need a resurrect service config for systemd and windows service
|
||||
|
||||
### Web interface
|
||||
|
@ -20,9 +20,12 @@ Since we run cube backup, we could "bake in" full KVM support
|
|||
Caveats:
|
||||
- We'll need to re-implement libvirt controller class for linux
|
||||
|
||||
### Hyper-V Backup plugin
|
||||
That's another story. Creating snapshots and dumping VM is easy.
|
||||
Shall we go that route since alot of good commercial products exist ?
|
||||
### SQL Backups
|
||||
That's a pre-script job ;)
|
||||
Perhaps, provide pre-scripts for major SQL engines
|
||||
Perhaps, provide an alternative dump | npbackup-cli syntax.
|
||||
In the latter case, shell (bash, zsh, ksh) would need `shopt -o pipefail`, and minimum backup size set.
|
||||
The pipefail will not be given to npbackup-cli, so we'd need to wrap everything into a script, which defeats the prometheus metrics.
|
||||
|
||||
### Key management
|
||||
|
||||
|
@ -31,4 +34,18 @@ Possibility to add new keys to current repo, and delete old keys if more than on
|
|||
### Provision server
|
||||
|
||||
Possibility to auto load repo settings for new instances from central server
|
||||
We actually could improve upgrade_server to do so
|
||||
We actually could improve upgrade_server to do so
|
||||
|
||||
### Hyper-V Backup plugin
|
||||
That's another story. Creating snapshots and dumping VM is easy
|
||||
Shall we go that route since alot of good commercial products exist ? Probably not
|
||||
|
||||
### Full disk cloning
|
||||
Out of scope of NPBackup. There are plenty of good tools out there, designed for that job
|
||||
|
||||
### Rust rewrite
|
||||
That would be my "dream" project in order to learn a new language in an existing usecase.
|
||||
But this would need massive sponsoring as I couldn't get the non-paid time to do so.
|
||||
|
||||
### More backends support
|
||||
Rustic is a current alternative backend candidate I tested. Might happen if enough traction.
|
Loading…
Reference in a new issue