From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Venti off-site backups
Date: Wed, 26 Oct 2016 20:19:43 +0200 [thread overview]
Message-ID: <20161026201943.240c883c@neon.9fans.fr> (raw)
In-Reply-To: <CAPd04b6psAMO5AJFh-5WgsvSPz4B0RAHx8z8CRCfANHj1g8zYg@mail.gmail.com>
> I see several threads about how people are cloning their Venti
> servers to remote Venti servers as a means of creating a backup.
Personally, I use three different ways of replicating the
content of my Venti file servers.
1. The first method is to use venti/mirrorarenas to replicate
the content of a Venti arena partition to another hard disk.
venti/mirrorarenas /dev/sdE0/arenas /dev/sdE1/arenas
This method requires two hard disks and two identical arena partitions.
2. The second method is to copy blocks from a Venti arena partition
to a Venti server running on another machine, accessed through the
local network.
You'll find an example of script using this method here:
http://9legacy.org/www.9legacy.org/9legacy/tools/backup/readwrite
This method requires another machine running Venti. The partition
layout could be different and the Venti servers could be running
on different operating systems.
3. The third method is to copy blocks from a Venti arena partition
to arena files, using venti/rdarena. Then you can copy the arena files
to external media like Blu-ray discs or hard disks.
The restoration is done to a running Venti using venti/wrarena.
You'll find backup and restore script examples here:
http://9legacy.org/www.9legacy.org/9legacy/tools/backup/read
http://9legacy.org/www.9legacy.org/9legacy/tools/backup/write
This method require external media to store the arena files.
For example, I use all these three methods to replicate the data
of my main file server. Consequently, the data are replicated on:
- two machines (automatically)
- two hard disks of each machine (automatically)
- some external hard disks (manually)
--
David du Colombier
prev parent reply other threads:[~2016-10-26 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:25 James A. Robinson
2016-10-26 17:43 ` Steven Stallion
2016-10-26 17:59 ` Steve Simon
2016-10-26 18:19 ` David du Colombier [this message]
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=20161026201943.240c883c@neon.9fans.fr \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).