Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Messaging Server 6.0 Installation Guide for Solaris Operating Systems

Chapter 4
Upgrading to Sun ONE Messaging Server

This chapter describes how to upgrade from Messaging Server 5.2 to 6.0.

Note

You must first upgrade or migrate to Messaging Server 5.2 prior to upgrading to Sun ONE Messaging Server 6.0. You will not be able to directly upgrade or migrate to Messaging Server 6.0 from versions prior to 5.2. See the iPlanet Messaging Server 5.2 Migration Guide and Installation Guide for more information on migrating to Messaging Server 5.2.

There are three steps to upgrading from Messaging Server 5.2 to Messaging Server 6.0. following topics outline the process:

  1. Creating Upgrade Files to Update your Configuration (UpgradeMsg5toMsg6.pl)
  2. Running the Upgrade Utility (do_the_upgrade.sh)
  3. Migrating User Mailboxes (optional)

Note

Prior to performing the upgrade:

  • Messaging Server 6.0 is installed and configured (with the instructions in Chapter 2, "Installing Messaging Server.") on either the same or a different system from the Messaging Server 5.2 system.
  • Existing Messaging Server 5.2 installations are configured with MTA Direct LDAP Lookup not with imsimta dirsync. For more information, see the Sun ONE Messaging Server 6.0 Administrator’s Guide.

Creating Upgrade Files to Update your Configuration

This section describes how special upgrade files are created in order to update your configuration on your Messaging Server 6.0 system:

Overview

Prior to running an upgrade utility to move from Messaging Server 5.2 to 6.0, you first need to run the UpgradeMsg5toMsg6.pl Perl script (located in msg_svr_base/sbin).

UpgradeMsg5toMsg6.pl compares your 5.2 configuration files with your 6.0 configuration files and creates to sets of files for each configuration file: *.CHANGES files and *.MERGED files.

The *.CHANGES files and *.MERGED files are generated in the workspace directory, /var/tmp/UpgradeMsg5toMsg6.ScratchDir.

The *.CHANGES files show critical configuration file differences between Messaging Server 5.2 and Messaging Server 6.0. These files highlight the configuration entities that are only found in Messaging Server 6.0, the configuration entities from Messaging Server 5.2 that are obsolete in Messaging Server 6.0, and the configuration entities that are only found in the Messaging Server 5.2. Note that not all *.CHANGES files will show differences between the versions of configuration files, and not all configuration files will generate *.CHANGES files.

The *.MERGED files are a consolidation of Messaging Server 5.2 and 6.0 configuration values and settings. In general, configuration parameter values from Messaging Server 5.2 are retained over the Messaging Server 6.0 version if:

Table 4-1 lists the configuration files that generate *.MERGED or *.CHANGES files:

Table 4-1  Messaging Server Configuration Files that Generate *.MERGED or *.CHANGES files 

Configuration Information

Description

Generates *.MERGED File

Generates *.CHANGES File

job_controller.cnf

Job Controller File

X

X

conversions

Conversions File

X

 

channel_option, where channel is an SMTP channel

SMTP channel option files

X

 

native_option

Native channel option file (exception to channel_option)

X

X

channel_headers.opt, where channel is an SMTP channel

Header option files

X

 

dispatcher.cnf

Dispatcher File

X

X

imta_tailor

Tailor File

X

X

option.dat

Global MTA Option File

X

X

aliases

Aliases File

X

 

imta.cnf

MTA Configuration File; only the include references (like file directory locations) are changed. Rewrite rule and channel settings are retained from your 5.2 configuration. To include LMTP in your imta.cnf, copy the LMTP information from your 6.0 imta.cnf file.

X

In some instances, a *.CHANGES file may be generated.

mappings

Mappings File

X

 

mappings.locale

Localized Mappings File

X

 

internet.rules

Internet Rule Configuration File

X

 

backup-groups.conf

Backup Group Definitions

X

X

configutil

Changes of configuration parameters in local.conf and msg.conf configuration files.

 

X

Running the UpgradeMsg5toMsg6.pl Perl Script

To run the UpgradeMsg5toMsg6.pl to create sets of files by which you’ll be able to update your configuration, follow these steps:

  1. If your Messaging Server 5.2 and 6.0 versions are not on the same machine, transfer, extract and copy the Messaging Server 5.2 server-root directory to the Messaging Server 6.0 system. If your server versions are installed on the same machine, you can skip this step.
    1. If your Message Store is too large to transfer from one system to another, you can unmount the disks from the 5.2 system and mount them onto the 6.0 system by using the umount (1M) and mount (1M) commands.

      Note

      You don’t have to copy the Messaging Server 5.2 store data to the Messaging Server 6.0 system, however, you must ensure that the Messaging Server 5.2 store data is accessible during the upgrade process.

    2. Both your 5.2 and 6.0 systems can be running at this point.
  2. Run the UpgradeMsg5toMsg6.pl upgrade script (located in msg_svr_base/sbin) against the msg-instance of 5.2 version and the msg_svr_base of the 6.0 version. For example:

    perl UpgradeMsg5toMsg6.pl /usr/sunone/server5/msg-budgie \
      /opt/SUNWmsgsr

    3. where /usr/sunone/server5/msg-budgie is the msg-instance of the 5.2 Messaging Server and /opt/SUNWmsgsr is the msg_svr_base of the 6.0 Messaging Server.

    Note

    Messaging Server 6.0 does not support multiple instances. If you have multiple instances of Messaging Server version 5.2, you may only choose one instance to upgrade to Messaging Server 6.0. Furthermore, running the upgrade utility more than once in an attempt to migrate multiple instances will only result in you overwriting your configuration.

    *.MERGED and *.CHANGES files (as described in Table 4-1) will be created.

  3. Carefully review the *.MERGED files; if you don’t want to use the suggested recommendations, you must manually adjust the settings.

This utility does not update the Messenger Express customization files. Therefore, you need to manually change these files in order to keep the relevant information from Messaging Server 5.2 and add any new information from the Messaging Server 6.0 installation.

Running the Upgrade Utility

This section describes the do_the_upgrade.sh utility (located in /var/tmp/UpgradeMsg5toMsg6.ScratchDir), a shell script that is made up of four sub-scripts. The following topics are covered in this section:

Overview

The do_the_upgrade.sh utility is made up of four shell scripts that, with your *.MERGED files, update the configuration and file directory locations of your MTA configuration, your configutil parameters, backup parameters, and your mboxlist database in your Messaging Server 6.0 system.

You can either run the do_the_upgrade.sh utility, or you can individually run one or more of the scripts that make up the do_the_upgrade.sh utility (make_mta_config_changes.sh, make_configutil_changes.sh, make_backup_config_changes.sh, and make_mboxlistdb_changes.sh).

To run the do_the_upgrade.sh utility:

# sh /var/tmp/UpgradeMsg5toMsg6.ScratchDir/do_the_upgrade.sh

Note

When executing either the do_the_upgrade.sh utility or any of the sub-scripts, be sure that neither Messaging Server 5.2 nor 6.0 is up and running.

After running the do_the_upgrade.sh script, you can either continue to reference your 5.2 partition paths (though you will not be able to remove your Messaging Server 5.2 server-root directory) or you can manually move the 5.2 store partitions to the appropriate Messaging Server 6.0 directory location. You should perform this step prior to restarting Messaging Server.

MTA Configuration

The MTA upgrade configuration sub-script that makes up of part of the do_the_upgrade.sh utility is called make_mta_config_changes.sh (located in /var/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_mta_config_changes.sh script backs up, renames, and moves the *.MERGED server configuration files to their original names and locations within the Messaging Server 6.0 file directory structure.

Once the script has finished renaming and moving the files, it automatically runs the imsimta cnbuild command to recompile the MTA configuration.

Note

If you want to upgrade an MTA relay machine from Messaging Server 5.2 to Messaging Server 6.0, you only need to run the make_mta_config_changes.sh and the make_backup_config_changes.sh (described in Backup Configuration).

configutil Parameters

The configutil upgrade configuration sub-script that makes up part of the do_the_upgrade.sh utility is called make_configutil_changes.sh script (located in /var/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_configutil_changes.sh script incorporates new or updated parameters in the msg.conf and local.conf files. If default values are not specified in configutil parameters in Messaging Server 6.0, any Messaging Server 5.2 values are carried forward to the Messaging Server 6.0 version.

Backup Configuration

The backup upgrade configuration sub-script that makes up part of the do_the_upgrade.sh utility is called make_backup_config_changes.sh script (located in /var/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_backup_config_changes.sh script upgrades the configuration of your backup services such as those in your backup-groups.conf file.

mboxlist Database

The mboxlist database upgrade configuration sub-script that makes up part of the do_the_upgrade.sh utility is called make_mboxlistdb_changes.sh script (located in /var/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_mboxlistdb_changes.sh script transfers and upgrades your 5.2 mboxlist database and upgrades it to the Messaging Server 6.0 directory structure. The script copies the four *.db files (folder.db, quota.db, peruser.db, and subscr.db) from server-root/msg-instance/store/mboxlist on your Messaging Server 5.2 system to msg_svr_base/data/store/mboxlist on your Messaging Server 6.0 system.

Migrating User Mailboxes

This section describes how to optionally migrate user mailboxes from your Messaging Server 5.2 system to your Messaging Server 6.0 system. If you have Messaging Server 5.2 and 6.0 installed on the same machine, you should not have to migrate your user mailboxes. Furthermore, if you are able to continue accessing the 5.2 machine where your user mailboxes are stored, you are not required to migrate your user mailboxes to your 6.0 machine. You only need to migrate your user mailboxes if you are no longer going to have access to your Messaging Server 5.2 machine.

To move user mailbox data from Messaging Server 5.2 to 6.0 in an online method, follow the steps described in this section. You should not need to bring the Messaging Server down while you move data.

The following topics are outlined:

Requirements

The only requirement for migration is stored running on both the old and new messaging servers.

Migration Instructions

To migrate your user mailboxes from your 5.2 system to your 6.0 system:

  1. Notify users in advance that until data move process is completed, they do not have access to their mailboxes. Be sure that users log out of their mail systems before the data move takes place.
  2. Change the mailUserStatus user LDAP attribute on all user entries on the 5.2 message store from active to hold in order to hold incoming users’ messages in the hold queue and to prevent access to the mailboxes over IMAP, POP, and HTTP.

    3. For more information on mailUserStatus, see the Sun ONE Messaging Server Schema Reference Manual.

  3. Be sure that both your 5.2 and 6.0 Messaging Servers are up and running during this process.
  4. Change the mailHost attribute in all user entries from the old mail server to the new mail server.

    5. To do so, use the following ldapsearch command to find the user entries where the mailHost attribute needs to be modified:

    ldapsearch -h ldap.siroe.com -b "o=internet" \    "(&(objectclass=maildomain)(mailHost=oldmail.siroe.com))"

    Then, use the ldapmodify command to appropriately change the entries to the new mail server.

    For more information on mailhost, see the Sun ONE Messaging Server Schema Reference Manual.

  5. On the old system (oldmail.siroe.com), split your user entries into equal groups (one user name per line) and place into user files
  6. Move the user data from the Messaging 5.2 message store to the Messaging Server 6.0 message store. You only need to perform this step if:
    • you are migrating from windows to unix or from unix to windows.
    • you do not want to migrate the entire message store all at once.
    • you need to rename your users, including uids, domain names, and default domain changes.

      • This step is accomplished by backing up the Messaging Server 5.2 message store with the imsbackup utility and restoring the message store to Messaging Server 6.0 with imsrestore utility.

      If migration using the imsbackup and imsrestore utilities is the chosen method to transfer the store data, then the partition paths should not be mapped to the Messaging Server 5.2 partitions and the mboxlist upgrade step should not be performed. The make_configutil_changes.sh script generated by the upgrade script automatically sets the partition path to map to the Messaging Server 5.2 partitions. This need to be altered manually. In addition, you should not run the make_mboxlistdb_changes.sh script. The do_the_upgrade.sh script runs it automatically by default, so you must remove it manually.

      See the Sun ONE Messaging Server Reference Manual for more information on syntax and usage of the imsbackup and imsrestore utilities.

      Run this command on newmail.siroe.com:

      rsh “ipaddress_of_oldmail.siroe.com /server-root/bin/msg/store/bin/imsbackup \
        -f- -u user_file” | /opt/SUNWmsgsr/sbin/imsrestore -f- -cy -n -v1

      where user_file is the user file described in Step 5 containing user mailbox names.

  7. Using the user files, run multiple concurrent backup and restore sessions (between 10-15) to maximize the restore speed into the new message store.
  8. Set Messaging Server 6.0 to be the new default messaging server for the system.

    9. Change the A record of oldmail.siroe.com to point to newmail.siroe.com (the server responsible for domain(s) previously hosted on oldmail.siroe.com).

  9. Release the messages in the hold queue on your Messaging Server 5.2 system by issuing the following command:

    imsimta process_held -uid=user -domain=domain

    10. where user is the user ID and domain is the domain where the user resides.

  10. Ensure that the user clients are pointing to the new mail server.

    11. After the upgrade finishes, have the users point to the new server through their mail client program (in this example, have it point to newmail.siroe.com from oldmail.siroe.com).

    An alternative is to use an MMP which obviates the need to have users point their clients directly at the new mail server; the MMP will get that information from the mailHost attribute which is stored in the LDAP user entries and will automatically re-direct them to the new server.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.