On 25 June 2012 15:44, Michael Schuster <[email protected]> wrote: > Hi Aneurin, > > I'd expect one of the design goals of the whole image-update process was to > work with as little interruption as possible (we had this in live upgrade > as well, so the historical precedent is fairly clear, IMO anyway): you > could run your update, watch it finish, analyse logs etc., all while the > machine (think "big server") was up and running *completely unchanged*. > Only when/if you're satisfied that the update did what you expected it to > do, you could (schedule a) reboot. IMO that's a much safer approach than > what you describe.
Ah, that way of working is new to me, but it does make a lot of sense. Thank you both for your quick replies - it seems a lot clearer now, especially with the distinction between a backup BE and a new BE. _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
