Forgot to mention: The Merkle-tree-based storage will be an incompatible format
change. On the positive side, I plan creating a migration script. I know this
is going to be pain a bit, but the later I do it, the worse…
Regards,
Vít Šesták 'v6ak'
--
You received this message because you are sub
Hello again. I am close to 0.1 release, the first numbered release. Mostly
documentation-related tasks are missing. Since my last update, I've made rather
quality improvements (e.g., not using utf-8 where not needed, disconnecting
BDVM from network and so on) than new features. I've also organiz
Hello again. I am close to 0.1 release, the first numbered release. Mostly
documentation-related tasks are missing. Since my last update, I've made rather
quality improvements (e.g., not using utf-8 where not needed, disconnecting
BDVM from network and so on) than new features. I've also organiz
Hi Holger,
I am generally OK with this level of sarcasm.
> But if you don't regularily test what you backup and test that you can
> actually restore, your backup is rather worthless. You don't want to find out
> your restore is broken, once your regular install is gone…
Sure. I remember having
Hi Vít,
On Sat, Mar 04, 2017 at 09:53:31AM -0800, Vít Šesták wrote:
> Holger, restore is already implemented in some basic form. (I havre mentioned
> it here on Mar 1.)
I'm sorry, I was wrong indeed and a bit too sarcastic too. I guess this was
due to your initial mail where there was no restor
On backup backends: I'd like to move the discussion to GitHub. I've summed up
what we need and created some comparison table:
https://github.com/v6ak/qubes-incremental-backup-poc/issues/35
Regards,
Vít Šesták 'v6ak'
--
You received this message because you are subscribed to the Google Groups
Holger, restore is already implemented in some basic form. (I havre mentioned
it here on Mar 1.) Both backup and restore are equally important: Without
backup you have nothing to restore from.
Feel free to try it, but remember, this is early stage of development and you
should read limitations.
On Fri, Mar 03, 2017 at 12:42:56PM -0800, Vít Šesták wrote:
> Well, I don't see any problem with restore. This is roughly what dom0 does
> (or initiates):
Vít, please design and *test* your restore. Nobody wants backup, everybody
wants restore.
--
cheers,
Holger
--
You received this
Well, I don't see any problem with restore. This is roughly what dom0 does (or
initiates):
1. create a new VM (with default or explicitly provided parameters and no netvm
– as I have mentioned, I don't backup anything but files and VM name)
2. start a new DVM (we have chosen to trust the DVM…)
3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Feb 28, 2017 at 10:49:43PM -0800, Vít Šesták wrote:
> Hello,
>
> I've implemented some changes, most notably initial support for restores. I
> haven't updated the README yet.
How do you handle restore? File-based backup was considered some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Feb 27, 2017 at 01:59:37PM +, Manuel Amador (Rudd-O) wrote:
> On 02/27/2017 01:53 PM, Manuel Amador (Rudd-O) wrote:
> >
> > I am terrified that Qubes 4.0 will force me to use LVM, because LVM is
> > frankly a disaster for data recovery an
Hello,
I've implemented some changes, most notably initial support for restores. I
haven't updated the README yet.
The CLI is still subject of change, I believe it should be refactored.
I am tracking many ideas in Github issues. There are two notable groups:
* Help-wanted (currently two issues
On 02/27/2017 08:52 AM, Manuel Amador (Rudd-O) wrote:
On 02/27/2017 12:51 PM, Chris Laprise wrote:
In some backup systems, each backup appears complete to the system,
even though it was created with incremental deltas. A benefit of this
is you can delete any backup in the set to reclaim space, w
On 02/27/2017 01:53 PM, Manuel Amador (Rudd-O) wrote:
>
> I am terrified that Qubes 4.0 will force me to use LVM, because LVM is
> frankly a disaster for data recovery and for data integrity as well. I
> would be willing to write an adapter to use ZFS zvols instead. That
> would be the right thin
On 02/26/2017 10:07 PM, Vít Šesták wrote:
> Q: Can I backup VM that is running?
> A: If you have LVM-based private.img, you can. (See README for details.) If
> you have standard file-based private.img, you cannot. I don't plan to
> implement this feature for file-based private.img, because Qubes
On 02/27/2017 12:51 PM, Chris Laprise wrote:
>
> In some backup systems, each backup appears complete to the system,
> even though it was created with incremental deltas. A benefit of this
> is you can delete any backup in the set to reclaim space, without
> affecting any of the remaining backups--
On 02/27/2017 02:58 AM, Vít Šesták wrote:
Ad backups cannot be pruned: You are right, but since even restore is not yet
implemented, I don't see much point of mentioning prune in limitations. And
prune seems to be much easier to implement.
I was referring to the ability to delete any backups
> It almost sounds like you're trying to supply data to the attacker
Good point. I'll rephrase it. Maybe the following is more reasonable:
* Attacker having access to your storage can learn how many VMs you have and
limited metadata for each VM (see below). They however cannot learn VM names,
l
On 02/26/2017 05:07 PM, Vít Šesták wrote:
Hello,
I'd like to announce my PoC for incremental file-based backup for Qubes VMs. It
is not a completely new backup system, it just wires together some existing
software with Qubes principles to provide convenient and secure way to backup
many VMs wi
Hello,
I'd like to announce my PoC for incremental file-based backup for Qubes VMs. It
is not a completely new backup system, it just wires together some existing
software with Qubes principles to provide convenient and secure way to backup
many VMs with minimum overhead and encrypt them by one
20 matches
Mail list logo
