ryszard-suchocki
ryszard-suchocki
1:1 replication, like using standard PVE built-in replication mechanism. [host A]------------------[host B] ssd1/vm-100-disk-0 => ssd1/vm-100-disk-0 hdd/vm-100-disk-0 => hdd/vm-100-disk-0 Currently, all FS with autobackup:property=true gives such a result: [host A]------------------[host B]...
Well, you discovered the problem with PVE and VM disk naming when using ZFS storage (disk name is unique in storage scope, but not in whole VM). So stripping the...
> You basically want something like rsync for zfs pools? :) yes, 1:1 replication with all benefits from zfs-autobackup (custom properties, autoprune).
> Hello, it seems fine, but it requires copying/rewriting the whole repo configuration (repeating yourself). A few days ago I created a Q&A topic about copy S3 to S3, where...
What about change the "property" `use: mixin` to the list `use: (new line)- mixin` ? Is it behave same?
Maybe some kind of switch, that will allow choosing whether to overload or merge? I mean such change is somewhat breaking change.
Let me test before close ;)
I tested some the new functionality (resticprofile version 0.18.0-dev commit ""). The new markup "..." works OK.Config v2 changes a lot about how to use resticprofile. Unfortunately, there is no...
Hello, I have a similar issue with generic Linux. File system: btrfs build on top of MD Raid. btrfs allows have multiple subvolumes (ie snapshots). Anyway, the count of occurrences...