Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!ESOC.BITNET!ESC1318
From: ESC1318@ESOC.BITNET
Newsgroups: mod.computers.vax
Subject: VAXcluster software
Message-ID: <8607011514.AA28984@ucbvax.Berkeley.EDU>
Date: Tue, 1-Jul-86 11:15:28 EDT
Article-I.D.: ucbvax.8607011514.AA28984
Posted: Tue Jul  1 11:15:28 1986
Date-Received: Wed, 2-Jul-86 00:03:16 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26
Approved: info-vax@sri-kl.arpa



  Sorry if this is repeating on you, but I sent the original back in the
  Great Quiet of 06/86.

  The original was probably a repeat of previous questions but I'd appreciate
  a few replies.

  I'm interested in VAXcluster software (oh dear !!)

  a)  has anyone out there got any experience/comments to make on
      the timings involved in failover ?
  b)  has anyone tried operating a hardware cluster without the VAXcluster
      software ?

  As well as any help on the 2 questions above I'd be grateful for any
  tales/experiences with VAXclusters. We've got (will have) 3 processor nodes
  (2 real time applic, and 1 backup/dev machine) with HSC dual ported disks.
  I'm trying to investigate the problems / benefits of using or not using the
  VAXcluster software with our hardware cluster.

     Thanks for taking your time to read this , I'd be grateful for any
   experience / knowledge you could pass on.

                    Regards.
                        Mike Brett