Discuss mailing list

[Jamyn Shanley <jshanley AT gmail.com>]

Given the vast majority of the data would be text (sql databases, flat files, whatever) which generally compresses very well in transit, I think it would be pretty low overhead. I doubt there is more than 10g of userdata total. Duplicate data would not need to be re-transmitted, as rsync only sends the changes since the last update. So if a server backed up yesterday and then 200 accounts were added today, rsync would only send the data for those 200 accounts.

Who would pay for the backup server? Well, I could provide one for free.

Or, we could go a different route and encrypt the backups on the server side before transit, and then store the backup on a free or almost free solution (SpiderOak, DropBox, whatever).

On Wed, Feb 6, 2013 at 6:28 PM, Peter Green <peter AT greenpete.free> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Can I make one other suggestion? Mandatory TLD backups
> (rsync+encrypted, whatever) to some "central" OpenNIC machine or
> other backup service.

An interesting idea but would that mean a substantial amount of data
to be backed up and who would pay for the backup server?

Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJREvUqAAoJEPBKqeCz72c5zOgH9Al2zT1pGVP1TpTcvBhB4IeB
MWD2SzUGql5rnSq/zU5dK0pPZ1cNLw829G3luOwFJdxgnsbLZHejx7mVnRIkNtDl
xo16yktPFtnkUkCOfwo9XYKVQTOvKFgo/yeiQ1ssRdW2dcNB/2GPuLoplapaHbCt
fu+uyNMDn9DWPIYzaneAKvbuKkTEXl/j7/I0VQ+WRS453ayLKf0mrAGtEnw061B0
dk3vv60rMW6wTTMT3FfXiyrByH8+hQ1cgZ2vvkrnsC7rkcEgIRG788KnkmYIndSP
AqdPnFHWBexYlf/MUz/84bqsnC8pL5Z6x175xb+ydml71dGD6qt1gbeuRkduSg==
=/YEG
-----END PGP SIGNATURE-----

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org