As you datastore is named "backup" not "datatstore"
- add the possibility to restore a single file from the client
FYI: you can download that and the backup log already too.add a show configuration button for virtual machines like on the pve gui.
I think this is block-level/whole machine backup? Are there going to be file level backup clients as well?
Is this the ambition for pbs?
One question: is it possible to use the gui with encryption at this point? I created a backup key for each host but it seems like a gui option is missing for now, probabbly comming in the near future?
/etc/pve/priv/storage/<storeid>.enc). There where some recent qemu-server improvements as well - but only available on pvetest IIRC.
You can use a network storage as a backing path for a Backup Datastore - but we recommend local storage; it's normally just faster and you do not have an extra remote component which could fail.
Just mount it in /etc/fstab then add a path on the moutnpoint as datastore?You can't add NFS remotes through the UI at the moment though?
I have 10gbE to my storage from my virtual environment (where backup server is currently installed) so I'd like to add that as a destination. It's where virtual disks would be anyway!
Yes, some parts like the pve-lxc-syscall interceptor daemon are already written in rust. The webinterface is in ExtJS though, shares already a lot of the codebase.Is it possible that in the future pve or parts of it will be rewritten in rust? I am guessing that rust code from pbs could be resused for pve. Especially web interface related things.
Just mount it in /etc/fstab then add a path on the moutnpoint as datastore?
Do I understand rhat correctly, the disks are where the backups are?
If they are there anyway you just send their content (or parts of that due to the incremental backup) twice over the network...