Upgrading Server Machines

Repeat the following instructions on each server machine. Perform them first on the database server machine with the lowest IP address, next on the other database server machines, and finally on other server machines. The AFS data stored on a server machine is inaccessible to client machines during the upgrade process, so it is best to perform it at the time and in the manner that disturbs your users least.

• Distributing Binaries to Server Machines

  If you have just followed the steps in Distributing Binaries to Server Machines to install the server binaries on binary distribution machines, wait the required interval (by default, five minutes) for the local upclientbin process to retrieve the binaries.

  If you do not use binary distribution machines, perform the instructions in Distributing Binaries to Server Machines on this machine.

• Become the local superuser root, if you are not already, by issuing the su command.

  % su root Password: root_password

• If the machine also functions as a client machine, prepare to access client files using the method you have selected from those listed in Obtaining the Binary Distribution:

  • If you copied the contents of the root.client directory into AFS (in Step 6 of Storing Binaries in AFS), change directory as indicated.

    # cd /afs/cellname/sysname/usr/afsws/root.client

  • If copying files from the CD-ROM, mount the CD-ROM for this machine's system type on the local /cdrom directory. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation. Then change directory as indicated.

    # cd /cdrom/sysname/root.client

  • If accessing the distribution electronically, you possibly already downloaded it in Storing Binaries in AFS. If so, it is still in the temp_afs36_dir directory. If not, download it and run any commands necessary to uncompress or unpack the distribution. Place it in a temporary location (temp_afs36_dir), and change directory to the indicated subdirectory.

    # cd temp_afs36_dir/root.client

• If the machine also functions as a client machine, copy the OpenAFS version of the afsd binary and other files to the /usr/vice/etc directory.

  # cp -p usr/vice/etc/* /usr/vice/etc # cp -pr usr/vice/etc/C /usr/vice/etc

  If you have not yet incorporated AFS into the machine's authentication system, perform the instructions in the section titled Enabling AFS Login for this system type in the OpenAFS Quick Beginnings chapter about configuring client machines. If this machine was running the same operating system revision with AFS 3.5 or AFS 3.6 Beta, you presumably already incorporated AFS into its authentication system.

• AFS performance is most dependable if the AFS release version of the kernel extensions and server processes is the same. Therefore, it is best to incorporate the OpenAFS kernel extensions into the kernel at this point.

  First issue the following command to shut down the server processes, preventing them from restarting accidently before you incorporate the OpenAFS extensions into the kernel.

  # bos shutdown <machine name> -localauth -wait

  Then perform the instructions in Incorporating AFS into the Kernel and Enabling the AFS Initialization Script, which have you reboot the machine. Assuming that the machine's AFS initialization script is configured to invoke the bosserver command as specified in OpenAFS Quick Beginnings, the BOS Server starts itself and then the other AFS server processes listed in its local /usr/afs/local/BosConfig file. There are two circumstances in which you must incorporate the kernel extensions and reboot now rather than later:

  • You are upgrading the File Server on an HP-UX machine

  • The machine also serves as a client, you upgraded the client files in the previous step, and you want the new Cache Manager to become operative right away

  In any other circumstances, you can choose to upgrade the kernel extensions later. Choose one of the following options:

  • Restart all server processes by issuing the bos restart command with the -bosserver flag.

    # bos restart <machine name> -localauth -bosserver

  • Wait to start using the new binaries until the processes restart automatically at the binary restart time specified in the /usr/afs/local/BosConfig file.

• Once you are satisfied that the machine is functioning correctly at OpenAFS, there is no need to retain previous versions of the server binaries in the /usr/afs/bin directory. (You can always use the bos install command to reinstall them if it becomes necessary to downgrade). If you use the Update Server, the upclientbin process renamed them with a .old extension in Step 1. To reclaim the disk space occupied in the /usr/afs/bin directory by .bak and .old files, you can use the following command:

  # bos prune <machine name> -bak -old -localauth

  Step 5 of Distributing Binaries to Server Machines had you move the previous version of the binaries to the /usr/afs/bin.old directory. You can also remove that directory on any machine where you created it.

  # rm -rf /usr/afs/bin.old