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!ucbvax!IRLEARN.BITNET!LISTSERV
From: LISTSERV@IRLEARN.BITNET (Revised List Processor, 1.5b)
Newsgroups: mod.computers.vax
Subject: File: "INFO-VAX MAIL" being sent to you
Message-ID: <8611080810.AA25529@ucbvax.Berkeley.EDU>
Date: Tue, 4-Nov-86 20:20:00 EST
Article-I.D.: ucbvax.8611080810.AA25529
Posted: Tue Nov  4 20:20:00 1986
Date-Received: Sat, 8-Nov-86 20:20:49 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 32
Approved: info-vax@sri-kl.arpa

Received: from SRI-KL.ARPA by wiscvm.wisc.edu on 11/04/86 at 19:11:21 CST
Received: from WISCVM.WISC.EDU by SRI-KL.ARPA with TCP; Mon 3 Nov 86
 11:21:50-PST
Received: from (WELCH)UMASS.BITNET by WISCVM.WISC.EDU on 11/03/86 at
  13:21:09 CST
Date:     Sun, 2 Nov 86 13:38 EDT
From:  welch%UMass.BITNET@WISCVM.WISC.EDU
To:  info-vax@sri-kl.arpa
Subject:  VMS Shadowing bug/gotcha

Here's an interesting "gotcha" I just came across having to do with
VMS shadowing:

After installing the shadow key on our clustered CPUs we tried using
shadowing.  It worked only on out 8600 - DEC software support
checked things out and said everything looked fine.  After much
head scratching we realized the difference between our 8600 and
the other CPUs was the type of system disk.  The 8600 is on
a DU disk and the rest on RM05s.

As an experiment we booted another CPU off a spare DU disk and lo and
behold shadowing worked for that CPU, too.

So (at least for now) anyone planning to use shadowing should be warned
that for it to work you must boot from a DU (I suppose any DSA type
disk would work) to get the shadow driver to load instead of the
DUDRIVER.

Bitnet: Jhwelch@Amherst or
        Welch@Umass

                -Jonathan.