kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: anyone aware of a high availability setup that relies on fully redundant install?
Date: Mon, 18 Apr 2016 06:29:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1604180626380.4199@localhost.localdomain> (raw)
In-Reply-To: <208224.1460954905@turing-police.cc.vt.edu>

On Mon, 18 Apr 2016, Valdis.Kletnieks at vt.edu wrote:

> On Sun, 17 Apr 2016 10:47:55 -0400, "Robert P. J. Day" said:
> >   i figure this is as good a place as any to ask ... is anyone here
> > aware of anyone using a linux config and install that, for the
> > purposes of reliability or high availability or whatever you want to
> > call it, relies on a second, completely independent installation of
> > linux on the same hard drive?
>
> IBM's AIX has for a long time had the concept of an 'alternate boot
> volume', which can be another logical volume on the same physical
> hard drive.  But it's not intended for high-availability, it's for
> "if this software upgrade goes pear-shaped I have an easy backout
> procedure".  And it avoids most of the "you have to keep two
> version" issues by providing a tool to copy your *current* system
> onto the alternate boot.  I'm sure some Linux distros have stolen
> the concept.

  that makes sense -- a *minimal* bootable system for recovery and
troubleshooting. but not a fully independent previous install.

> Most implementations of "high availability" would see the phrase "on
> the same hard drive" and start pointing and laughing at the single
> point of failure.

  trust me, i'm aware of that. :-) perhaps i shouldn't have used the
phrase "high availability", this proposal was more for just the
ability to back out of a botched or flawed upgrade.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2016-04-18 10:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17 14:47 anyone aware of a high availability setup that relies on fully redundant install? Robert P. J. Day
2016-04-17 15:23 ` Res: " Daniel
2016-04-17 16:02 ` Greg KH
2016-04-17 17:16   ` Robert P. J. Day
2016-04-17 21:17     ` Greg KH
2016-04-18  4:48 ` Valdis.Kletnieks at vt.edu
2016-04-18 10:29   ` Robert P. J. Day [this message]
2016-04-18 14:43     ` Valdis.Kletnieks at vt.edu
2016-04-18 19:49   ` Miles Fidelman
2016-05-12 16:06 ` Andrew Bradford

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=alpine.LFD.2.20.1604180626380.4199@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).