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

Michael Moroney moroney at world.std.spaamtrap.com
Wed Apr 17 23:21:13 EDT 2019


Stephen Hoffman <seaohveh at hoffmanlabs.invalid> writes:

>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.

Not endorsing it. After all, it is a configuration that that requires a shadow
copy upon every reboot.

>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...

Yes. I don't recall if minicopy is an option for system disks like this.

>And neither system can boot from the secondary if the local primary 
>storage fails, absent reconfiguration as a cluster satellite.

Maybe you didn't understand what I wrote. In this bizarre configuration, each
system is essentially a satellite of the other.

>Whether scrounging used HBAs and a switch and some low-end FC SAN 
>storage, or scrounging multi-host SCSI and storage, would be cheaper?

At least better. I haven't looked to see what islandco may have or if one can
get a couple of interface cards, switch and FC chassis on Ebay cheap, or
something.



More information about the Info-vax mailing list