8.5 Upgrading an existing Domino server

 < Day Day Up > 

8.5 Upgrading an existing Domino server

This section describes upgrading a single Domino server using the script file method. Before you begin your upgrade, you should review the release notes and check the platform-specific section for any new features. Also review the fix list. There are also a couple of notes.ini parms which you may want to set before you begin your upgrade:

  1. If you do not want to update your Domino Directory design (during an upgrade, for example), you deploy new designs in a centralized manner, then add the following notes.ini parm: SERVER_UPGRADE_NO_DIRECTORY_REDESIGN=1.

  2. A Domino upgrade adds the "design" task in servertasks= line of the notes.ini. If you do not want to update your Server Tasks, add the following notes.ini parm:


Upgrade steps

  1. Shut down the server.

  2. Back up the /opt/lotus files (library files and program files). If /opt/lotus is a mountpoint in your system, you might want to unmount the volume and mount a new one. See step 5 on page 203.

  3. Copy the following files from out of the notesdata directory into a temporary directory: cert.id, server.id, notes.ini, .profile, httpd.cnf, dcontroller.ini

  4. Remove all files and directories from /opt/lotus.

  5. Refer to the Install Guide to determine how much disk space is required in the program directory for the new release, and make sure that you have sufficient space allocated for this filesystem mounted on /opt/lotus.

  6. FTP the tar file from the CD to /opt/lotus directory. Make sure that you use binary mode.

  7. Telnet into the Linux as a root user and un-tar the file tar -xvzf <filename>. For example: tar -xvzf zLinux65xxx.TAR

  8. Run the install program. We describe here how to upgrade the server using script-mode. If you want to do it interactively, see "Installing the executable server code" on page 133 for a detailed description.

    For either way, you will need the information gathered in step 4 on page 194. In "Install script.dat" on page 357, there is an example of the script file for upgrading your Domino servers.

  9. Make a copy of the script.dat, that is: copy script.dat domino65.dat. Change to the /opt/lotus/zlinux directory.

  10. Update the following lines in domino65.dat. For example:

     installation_type = 2 <Domino Enterprise Server> program_directory = "/opt/lotus" template_install_option = 0 <do not install template files> data_UNIX_user = "ADMINA" data_UNIX_group = "notes" 

  11. You will need one data_directories section for each Domino server:

     data_directories: "/domserva/notesdata" 


    Remove or add data_directories sections as required. For example, if your Linux has two Domino servers on it, you will only have two data_directories sections.

  12. # Uncomment either of the following lines to override the defaults:

     data_UNIX_user = "domserva" data_UNIX_group = "notes" 

  13. Install the new code by entering the following command from the /opt/lotus/zlinux directory: install -script ./domino65.dat

  14. Copy the files from step 2 back to notesdata.

  15. Reinstall any third-party software that loads files into /opt/lotus, such as backup APIs, monitoring software, or virus scanning software. Refer to that product documentation for details.

  16. Logon with the Domino user ID.

  17. Bring up the server by running /opt/lotus/bin/server or /opt/lotus/bin/server -jc (to bring up Domino Controller).


    During an upgrade, you will be using your existing ID files and database, so you should not execute Domino Server setup.

  18. Depending on your notes.ini setting (see step 1 on page 202), you might be prompted as to whether the design of the Domino Directory should be replaced or not.

 < Day Day Up > 

IBM Lotus Domino 6. 5 for Linux on zSeries Implementation
IBM Lotus Domino 6.5 for Linux on Zseries Implementation
ISBN: 0738491748
EAN: 2147483647
Year: 2003
Pages: 162
Authors: IBM Redbooks

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net