From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] OT: how do 9fans backup their Mac(book)?
Date: Fri, 30 Sep 2011 22:01:07 +0200 [thread overview]
Message-ID: <CA+N-5baz8YHTOjXn1m5gMp866H5ZmHY3VSy0hp6vbJ2j-swi3Q@mail.gmail.com> (raw)
In-Reply-To: <7828850E-D4E3-4621-B425-98423B95E1C4@cs.utwente.nl>
What I do is to consider the macs as volatile.
Very much like "firmware".
All the stuff I care about is in our main file server.
I might either use my files using the octopus or just cache them in the local
disk of the mac when I need that.
To recover such "firmware", yes, I use an external disk and time machine,
which is what the mac seems to like.
On Fri, Sep 30, 2011 at 5:19 PM, Axel Belinfante
<Axel.Belinfante@cs.utwente.nl> wrote:
> Just curious what 9fans use, for home and/or work, to backup their macs.
>
> time machine?
> to a local (usb,firewire) disk?
> or remote (time capsule, nas (not officially sanctioned by apple))?
>
> or eat our own dog food and use eg. venti?
> or tra?
>
> or no backup necessary because everything important is already elsewhere?
> (in the cloud, or in a version management system)
>
> or?
>
>
> context: we are reconsidering how to do this at work,
> and prefer not to reinvent the wheel.
>
> (at home I just backup my mac to a readynas box using time machine).
>
>
> Sorry for the off-topic nature of this post, but the fact
> that 9fans will be aware of less-common solutions like venti -
> not to mention the presence of coraid people here -
> made me look for experience/expertise here.
>
> Regards,
> Axel.
>
>
next prev parent reply other threads:[~2011-09-30 20:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:19 Axel Belinfante
2011-09-30 15:53 ` Anthony Sorace
2011-09-30 17:43 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 17:59 ` erik quanstrom
2011-09-30 19:21 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 19:42 ` erik quanstrom
2011-09-30 19:45 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-09-30 19:53 ` erik quanstrom
2011-10-01 8:21 ` Anthony Sorace
2011-10-01 15:14 ` Ethan Grammatikidis
2011-10-01 15:24 ` erik quanstrom
2011-10-01 15:48 ` Ethan Grammatikidis
2011-10-01 16:49 ` Venkatesh Srinivas
2011-10-01 18:21 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-10-01 18:29 ` Anthony Sorace
2011-10-02 15:26 ` Ethan Grammatikidis
2011-11-03 20:54 ` Michaelian Ennis
[not found] ` <CAAQydVjZ42C-GTEFT7E2t=dCQ35fvHzqjSYx9a3o+8v+5D1vfA@mail.gmail.c>
2011-11-03 20:57 ` erik quanstrom
2011-11-01 18:15 ` smiley
2011-11-01 18:57 ` Anthony Sorace
2011-09-30 19:50 ` Latchesar Ionkov
2011-10-01 15:21 ` Ethan Grammatikidis
2011-09-30 20:01 ` Francisco J Ballesteros [this message]
2011-09-30 21:15 ` Bakul Shah
2011-10-01 17:22 ` John Stalker
2011-10-02 0:35 ` steve jenkin
2011-10-02 1:28 ` erik quanstrom
2011-10-02 2:28 ` steve jenkin
2011-10-02 2:37 ` erik quanstrom
2011-10-02 3:07 ` steve jenkin
2011-10-02 12:38 ` Iruatã Souza
2011-10-03 3:57 ` steve jenkin
2011-10-03 4:02 ` erik quanstrom
2011-10-02 13:30 ` Salman Aljammaz
2011-10-03 3:47 ` steve jenkin
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=CA+N-5baz8YHTOjXn1m5gMp866H5ZmHY3VSy0hp6vbJ2j-swi3Q@mail.gmail.com \
--to=nemo@lsub.org \
--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).