[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ntsecurity
Subject:    RE: [NTSEC] NT:  system availability
From:       "Webb, Andy" <Andy.Webb () swinc ! com>
Date:       1997-08-28 19:02:00
[Download RAW message or body]

One of the requirements for high availability is some sort of
redundancy.  Regardless of the platform. In the Microsoft case, their
plan is to provide redundancy through Microsoft Cluster Server
(Wolfpack).  This is in addition to any server redundancy you may have
built (see Compaq Proliant 7000 for highly redundant single server).

Wolfpack will allow you to make changes to the failover server, transfer
the process to the failover server, make changes to the primary server,
transfer the process back.

These are just parts of the solution, but they go a long way toward
solving the problem.

$0.02

=======================================================
Andy Webb              awebb@swinc.com                 www.swinc.com
Simpler-Webb, Inc.                Austin, TX                  
                             "Mauve has more RAM" - Dilbert
=======================================================

> -----Original Message-----
> From:	Mahon, Sean [SMTP:SMAHON2@ITP.EDS.COM]
> Sent:	Thursday, August 28, 1997 9:05 AM
> To:	'ntsecurity@iss.net'
> Subject:	[NTSEC] NT:  system availability
> 
> Hello:
> 
> I am concerned about Microsoft's claims  regarding NT as a "enterprise
> solution".  How can a vendor make that claim when almost all system
> parameter changes require a reboot.  Unix systems (AIX for example,
> can
> be maintained, changed and rebuilt without ever requiring a reboot).
> I
> am curious how people are dealing with this when using NT for mission
> >critical, high availability systems.  Comment?
> >

[prev in list] [next in list] [prev in thread] [next in thread]