this should allow us to
- define list of datasets that should be automatically snapshotted (for example `storage/encrypted` on fanny)
- define hosts and their datasets that should be backed up
- this would be defined on our offsite machines
- connection will be automatically established through malovpn
- offsite machines will pull backups using `backup` user
Example configuration on fanny could look like this:
``` nix
malobeo.backup = {
enable = true;
snapshots = [ "storage/encrypted" "zroot/encrypted/var" ];
};
```
Configuration on offsite machine (assuming it has a pool called backuppool) could look like this:
``` nix
malobeo.backup = {
enable = true;
hosts.fanny = [
{
sourceDataset = "storage/encrypted";
targetDataset = "backuppool/fanny/encrypted";
}
{
sourceDataset = "zroot/encrypted/var";
targetDataset = "backuppool/fanny/var";
}
];
};
```
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.
ahtlon
this should allow us to
storage/encryptedon fanny)backupuserExample configuration on fanny could look like this:
Configuration on offsite machine (assuming it has a pool called backuppool) could look like this:
WIP backup moduleto WIP: backup moduleThis would solve #38 for now. In future we could still think about restic backups for each individual microvm.
Looks good to me!
@@ -0,0 +20,4 @@enable = mkOption {type = types.bool;default = false;description = "Enable sharing metrics";"Enable sharing metrics"?