From: Piotr Kempa <piotr.kempa@sigarden.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] search by message size (incl. attachments)
Date: Thu, 16 Dec 2010 14:19:30 +0100 [thread overview]
Message-ID: <1292505513-sup-3596@pk-desktop> (raw)
In-Reply-To: <1292503648-sup-6880@niflheimr>
Excerpts from Moritz Wilhelmy's message of 2010-12-16 13:49:31 +0100:
> Excerpts from Piotr Kempa's message of Thu Dec 16 10:22:03 +0100 2010:
> > Re incremental backup - that's something I'll have to do, true, but
> > since I want it to be encrypted on the backup server (with no other
> > users or root getting a peek:) I settled on just bzipping, encrypting
> > and uploading one huge file. Even when there are small changes, when
> > it's one file and it's encrypted, it changes the whole file.
> >
> > I could think about getting some loopfile and cryptsetup a LUKS on it on
> > the server, or maybe encfs (I'm not sure they have encfs the server
> > though...).
>
> You could use encfs locally and just rsync the encrypted encfs on the server?
> Also, see rsnapshot for incrememtal backups.
>
Thanks, all great suggestions (especially rsyncing the encrypted encfs,
why didn't I think of that!).
But from all the answers I gather there's no way to search or sort by
mail size in sup, correct?
Piotr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-16 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 15:59 Piotr Kempa
2010-12-15 21:15 ` Marc Hartstein
2010-12-16 9:22 ` Piotr Kempa
2010-12-16 12:49 ` Moritz Wilhelmy
2010-12-16 13:19 ` Piotr Kempa [this message]
2010-12-16 13:21 ` Iain
2010-12-15 22:03 ` Tero Tilus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292505513-sup-3596@pk-desktop \
--to=piotr.kempa@sigarden.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox