[Info-vax] Cluster node fails to boot from shadow-set member

[Dave Froble]

On 4/17/2019 6:13 PM, Stephen Hoffman wrote:
> On 2019-04-17 21:07:40 +0000, Michael Moroney said:
>
>> I have heard of a *hack* that sort of allows this.  Sort of.  Each
>> system MSCP serves its drive to the other. Each system is set up to
>> boot over the network from the other node's disk. As long as the other
>> node is up (and the quorum issue has been dealt with), it will boot,
>> add its own disk as a copy target and once the shadow copy completes
>> (can take a while!), all is well.
>
> Wouldn't touch that configuration with the proverbial barge pole.
>
> And a shadow copy across gigabit Ethernet isn't speedy with what's large
> for OpenVMS but now considered a dinky terabyte or two of hard disk or
> SSD storage.   Yeah, maybe minicopy...
>
> And neither system can boot from the secondary if the local primary
> storage fails, absent reconfiguration as a cluster satellite.
>
> Whether scrounging used HBAs and a switch and some low-end FC SAN
> storage, or scrounging multi-host SCSI and storage, would be cheaper?
>
> More supportable to use the existing disks and the existing RAID
> controllers, and to then configure the shared files...
>

What people don't seem to want to face is, VMS cluster and Star coupler 
were made for each other.

Yeah, there have been newer storage options, but the bottom line is, if 
your plan is to throw CPUs at the system, shared storage is what's 
called for.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486