From:	CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 29-JAN-1989 02:03
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: Making a VAXcluster


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Sat, 28 JAN 89 10:26:07 PDT
Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Fri, 27 Jan 89 23:06:37 PST
Received: by ucbvax.Berkeley.EDU (5.61/1.33)
	id AA22782; Fri, 27 Jan 89 22:44:12 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 28 Jan 89 05:27:35 GMT
From: unmvax!charon!sdowdy@ucbvax.Berkeley.EDU  (Stephen Dowdy)
Organization: University of New Mexico, Albuquerque, NM
Subject: Re: Making a VAXcluster
Message-Id: <4303@charon.unm.edu>
References: <8901271630.AA06551@ucbvax.Berkeley.EDU>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

In article <8901271630.AA06551@ucbvax.Berkeley.EDU> DOMILLER@UALR.BITNET (Dale Miller) writes:
>>    Kevin Cassidy <KCASSIDY @ HUSKY1.SMARYS.CA> writes:
>>I'm hoping someone out there can help me with this problem.
>> [Stuff about needing a CCSD (Cluster Common System Disk) deleted]
>
>1) Make a backup /IMAGE of your system disk to another pack because the
>following procedure can't be done on the system disk of a running system.

I did this on our system while it was running.  However, i did it while
noone else was on it just to be safe.  A /Image backup is definitely good
to have, in the event you screw up and make a non-bootable system disk.

Setup a New value for sysroot.  You must do this in order for the system
to remain functional while you are moving things around. (this will
be setup automatically by STARTUP.COM (or somewhere in the boot sequence)
when it detects you have a [V4COMMON] directory)

$ Define/System SYS$SYSROOT -
	SYS$SYSDEVICE:[SYS0.],SYS$SYSDEVICE:[SYS0.SYSCOMMON.] -
	/Trans=(Concealed,Terminal)
$ Define/System SYS$SPECIFIC -
	SYS$SYSDEVICE:[SYS0.] -
		/Trans=(Concealed,Terminal)
$ Define/System SYS$COMMON -
	SYS$SYSDEVICE:[SYS0.SYSCOMMON] -
		/Trans=(Concealed,Terminal)

Create the common area.
$ Create/Dir SYS$SYSDEVICE:[V4COMMON]

Create the File Enter for Specific to Common
$ Set File/Enter=SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR -
	SYS$SYSDEVICE:[000000]V4COMMON.DIR

Rename the sysroot directories to the common area.
$ Rename SYS$SYSDEVICE:[SYS0]SYSEXE.DIR SYS$SYSDEVICE:[V4COMMON.SYSEXE]
$ Rename SYS$SYSDEVICE:[SYS0]SYSLIB.DIR SYS$SYSDEVICE:[V4COMMON.SYSLIB]
(You get the idea.  Rename everything from [SYS0] to [V4COMMON], except
the file enter for SYSCOMMON.DIR)

Create all the template directories in the old [SYS0] part.
$ Create/Dir SYS$SYSDEVICE:[SYS0.SYSEXE]
...
(until you have a directory by the same name in both the specific [SYS0]
portion and the [V4COMMON] area (don't creat a SYSCOMMON in [V4COMMON]!)

Rename all the site specific stuff from the Common area back to
	[SYS0.SYSEXE]
	VAXVMSSYS.PAR
	all the autogen stuff (PARAMS.DAT, ...)
	SYSUAF.DAT (if you want to maintain seperate login info for each
		node in the cluster, otherwise, leave it in common.
	any packages that can only run on one node for license reasons
	All the NET*.DAT files, except NETNODE_REMOTE.DAT (this is
		the same regardless of specific machine)
	Page/SwapFiles
	SYSDUMP.DMP
Rename everything from SYSLIB, etc that looks like it should go back
to specific area.

>7) Invoke sysgen and USE [SYS?.SYSEXE]VAXVMSSYS.PAR.  Change appropriate
>parameters (VAXCLUSTER, SCS_NODE, QUORUM, etc.) for your cluster. Then
>WRITE [SYS?.SYSEXE]VAXVMSSYS.PAR.  Also be sure to change the same ones in
>MODPARAMS.DAT so you won't lose them the next time you AUTOGEN.

>8)  Alter your boot floppy to specify the system root to boot from (CIBOO.CMD
>if you use HSC disks).  And reboot using the new system disk.

>I think that should at least get you close.  Since I have never tried this
>exact scenario, I won't guarantee it.  Good luck.

I found this method *MUCH* more desirable than re-installing V4.6 and V4.7.
I had to dink with it, by looking at a running cluster and doing DIRE/FILE
to get things right, but it wasn't too bad.  Please try to verify what i
have said above, since i may have forgotten something, and you'd really
hate to have a non-bootable system, wouldn't you?

I have assumed in the above you are using [SYS0] for the node you have now,
as a boot node.  (as you add satellites, they go in [SYS1]..[SYSD], and
all of the system roots are created for you.)

Good Luck!

--stephen
-- 
$!#######################################################################
$! stephen dowdy (UNM CIRT) Albuquerque, New Mexico, 87131 (505) 277-8044
$! Usenet:   {convex,ucbvax,gatech,csu-cs,anl-mcs}!unmvax!charon!sdowdy
$! BITNET:   sdowdy@unmb
$! Internet: sdowdy@charon.UNM.EDU
$!      Team SPAM in '87!            SPAAAAAAAAAAAAAAAAAAAAMMMMMMM!
$!#######################################################################