[2587] in SIPB-AFS-requests
New AFS server parts are all here
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Dec 23 15:49:56 1996
Date: Mon, 23 Dec 1996 15:10:50 -0500
From: Greg Hudson <ghudson@MIT.EDU>
To: sipb-afsreq@MIT.EDU
All of the pieces for the new AFS server are currently in our
possession (the enclosures arrived today). I will try to get them
into the machine room in the next day or two (well, not on Wednesday)
and work on installing it. Ideally, we can install it this week and
deploy it some time next week, assuming the disks will fit into the
enclosures and all that.
We should probably have a plan for deployment now. My plan is:
* Install the machine as sipb-server-1 (lots of installation
details glossed over, of course) and bring it up as an
AFS file server.
* vos move all the volumes from ronald-ann to sipb-server-1.
* Bring ronald-ann and sipb-server-1 down; bring up the new
machine as ronald-ann.
* vos syncvldb to point the VLDB at the volumes on ronald-ann.
* Start up a db server on ronald-ann. It should take a dumb
from one of the other servers and everything should work.
I've ignored replication sites in the above list, because I don't know
if vos syncvldb will deal with them. The safest thing to do is
probably to make a list of replication sites currently on ronald-ann
and recreate them after the vos syncvldb.
With this plan, nothing should be unavailable for very long, just the
time it takes to bring up sipb-server-1 as ronald-ann and run the
syncvldb.
