9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] advice? fossil+venti (p9), vbackup+venti (p9p) vs. some other means of backup
Date: Thu, 11 Dec 2014 15:04:59 -0500	[thread overview]
Message-ID: <9F47497D-BDA2-46E1-903C-20AD3E5FD486@9srv.net> (raw)
In-Reply-To: <CAOEdRO3Ns6bNydh1yyQTgiJ2Y_xJf+20ErOgCe6aX6Ko1rmH4A@mail.gmail.com>

> Does anybody rely on a backup scheme using, say,
> vbackup+venti on linux? Does it work well, or would
> you recomment other means of doing a backup?

Not precisely what you're asking, but likely close enough experience to be useful:

When last I was responsible for a bunch of unix boxes, I was using venti for backup. I started off using vbackup, but switched to something vac-based pretty quickly. I realized there was a ton of data on there that I didn't feel the need to keep backed up (the OS itself, but more significantly nearly a TB of transcoded video (we kept the source backed up)). Also, I don't think I could get at the vbackup images from Plan 9; the vac ones work fine, with some oddities based on file system differences. These were OS X systems, but I was just using stock p9p stuff; it should run fine on linux. I was sending to a remote venti running on Plan 9.

Using vac instead of vbackup increases your recovery time (you have to reinstall the OS & tools, and in my case we'd have to re-transcode the video), but we had a warm spare and RAID to guard agains simple disk failures; this was mostly for genuine disaster recovery (although being able to mount and cd around my backup history from my Plan 9 workstation was a huge benefit).

I also ran something similar on my laptop. I've stopped using that regularly in favor of Time Machine, but still use it as an occasional one-off for disaster recovery (although it's not off-site).

> I guess there are also people using fossil+venti on
> p9. Are those happy?

Yes, quite. Ever since someone (Richard Miller, I think) tracked down that persistent snapshot hang bug, it's been great. Most of the complaining about fossil's stability comes from outdated info. The fossil+venti combo isn't the fastest option (Erik's kenfs kicks ass there), but the tradeoffs work well for my needs.

> I am looking for a sustainable means of backup,
> mainly on linux, and am avaluating different options
> (rdiff-backup, rsnapshot, dump/restore, rdup...)

I would use this system again if I had unix servers I cared about. For my MacBook, Time Machine gets the edge mostly because it's automatic.

This is not quite the latest version, but you can take a look at /n/sources/contrib/anothy/bin/rc/vacbak. You can also take a look at .../anothy/lib/tet.(cron files xfiles) for examples of config files I used on a system called tet.

You're reminding me I've been meaning to come up with an off-site backup plan for my system, which I haven't had in a few years...




  parent reply	other threads:[~2014-12-11 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:50 Rudolf Sykora
2014-12-11 11:14 ` David du Colombier
2014-12-11 20:04 ` Anthony Sorace [this message]
2014-12-15  7:21   ` Rudolf Sykora
2014-12-16 20:28 ` Enrico Weigelt, metux IT consult

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=9F47497D-BDA2-46E1-903C-20AD3E5FD486@9srv.net \
    --to=a@9srv.net \
    --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).