Your message dated Wed, 25 May 2016 07:11:32 +0300
with message-id <20160525041132.GD2634@exolobe3>
and subject line Re: Bug#825235: obnam: make --exclude work during restore
has caused the Debian Bug report #825235,
regarding obnam: make --exclude work during restore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
825235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825235
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: obnam
Version: 1.19.1-1
Severity: wishlist
Dear Maintainer,
I wanted to restore (from scratch) a system where / and /home are mounted on
separate partitions, but backed into the same obnam repository.
First try was to mount /dev/newdrive1 on /target, /dev/newdrive2 on
/target/home, then have obnam restore the last backup to /target.
Can't do that: obnam won't restore to a non-empty dir. (which, by the way, also
includes "lost+found" so you can't restore to a blank partition unless you get
rid of that first.)
Second try was to restore --exclude /home/ --to /target
Can't do that: obnam ignores --exclude during restore.
I ended up listing every root folder except home in the restore command, then
create and mount home, and restore that. This kind of pain could be avoided if
--exclude worked on restore commands. I'm sure there are lots of other use
cases for this.
Bonus points if you also let obnam restore to a non-empty dir (with a --force-
merge option), merging source dirs into existing target dirs, and overwriting
existing files.
Thanks!
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages obnam depends on:
ii libc6 2.22-7
ii python 2.7.11-1
ii python-cliapp 1.20160316-1
ii python-fuse 2:0.2.1-12
ii python-larch 1.20151025-1
ii python-paramiko 1.16.0-1
ii python-tracing 0.9-1
ii python-ttystatus 0.32-1
ii python-yaml 3.11-3+b1
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, May 24, 2016 at 01:46:39PM -0700, Nemo Inis wrote:
> I ended up listing every root folder except home in the restore command, then
> create and mount home, and restore that. This kind of pain could be avoided if
> --exclude worked on restore commands. I'm sure there are lots of other use
> cases for this.
I don't want to do that, I'm afraid. I'd rather you used the FUSE
plugin ("obnam mount") and used your favourite file copying tool (cp,
rsync, ...) to restore. That gives you a lot of flexibility, and
doesn't require Obnam to have code to handle lots of use cases.
> Bonus points if you also let obnam restore to a non-empty dir (with a --force-
> merge option), merging source dirs into existing target dirs, and overwriting
> existing files.
Obnam used to allow restores to any directory. People kept
accidentally wrecking their system by restoring --to=/. This way is
better.
--
Schrödinger's backup hypothesis: the condition of any backup is
undefined until a restore is attempted. -- andrewsh
signature.asc
Description: PGP signature
--- End Message ---
