> Greetings,
>
> At our site, we have begun to upgrade our AFS 3.3 File Servers
> (mixture of Sunos 4.1.3 and Solaris 2.3) to Solaris 2.5 and AFS 3.4a. We have
approximately 15 file servers including 3 database servers.
>
> Question(s) 1:
> We understand that we must upgrade our 3 db servers all at once. What
> is the best way for us to do that to minimize down time? We have considered
just shutting down the 3 db servers and moving the fucntionality to 3 machines
that have been upgraded. Does that sound reasonable? What is involved in doing
that and what things do we need to be aware of?
The main thing you have to keep in mind is that every client knows the
names and IP addresses of your DBservers; thus, you can't easily change
what machines provide those servers.
It should be possible to do a conversion fairly easily:
- Make sure you have copies of the new server binaries on your DB server
machines, with some other names (say, /usr/afs/bin/ptserver.3.4a).
- Shut down all 3 database servers
- Make a copy of the old VLDB, just in case something goes wrong (the
database files can be found in /usr/afs/db).
- Run the VLDB conversion
- Rename the old servers to something different (/usr/afs/bin/ptserver.3.3),
and give the new servers their proper names
- Start everything up again.
If this is done properly, most of the downtime will be during the VLDB
conversion, which is unavoidable in any event.
-- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]>
Systems Programmer, CMU SCS Research Facility
Please send requests and problem reports to [EMAIL PROTECTED]
