Chapter 2 Upgrading to Sun Java Systems Messaging Server

This chapter describes how to upgrade from Messaging Server 5.2 to Messaging Server 6 2005Q1.

Before You Begin

Messaging Server 6 2005Q1 is installed and configured on either the same or a different system from the Messaging Server 5.2 system.



Note	Unlike previous versions of Messaging Server, you cannot upgrade your existing Messaging Server without first installing and configuring Messaging Server 6 2005Q1. Also note that you cannot use this upgrade program with Messaging Server versions older than version 5.2. Therefore, you must first migrate or upgrade to Messaging Server 5.2, install Messaging Server 6 2005Q1 and then run this upgrade program. See the iPlanet Messaging Server 5.2 Migration Guide http://docs.sun.com/source/816-6017-10/index.html for more information on migrating to Messaging Server 5.2.

Existing Messaging Server 5.2 installations are configured with MTA Direct LDAP Lookup not with imsimta dirsync.

In addition, Messaging Server 6 2005Q1 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 2005Q1. Furthermore, running the upgrade utility more than once in an attempt to migrate multiple instances will overwrite your configuration.

Overview of the Upgrade Process

There are three steps to upgrading from Messaging Server 5.2 to Messaging Server 6 2005Q1. The following topics outline the process:

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 2005Q1 system:

About Upgrade Files

Prior to running an upgrade utility to move from Messaging Server 5.2 to 6, 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 Messaging Server 6 configuration files and creates two sets of files for each configuration file: *.CHANGES files and *.MERGED files.

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

The *.CHANGES files show critical configuration file differences between Messaging Server 5.2 and Messaging Server 6 2005Q1. These files highlight the configuration entities that are only found in Messaging Server 6 2005Q1, the configuration entities from Messaging Server 5.2 that are obsolete in Messaging Server 6 2005Q1, 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 Messaging Server 6 configuration values and settings. In general, configuration parameter values from Messaging Server 5.2 are retained over the Messaging Server 6 2005Q1 version if:

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

Table 2-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 Messaging Server 6 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:

Both your 5.2 and Messaging Server 6 2005Q1 systems can be running at this point.

If your Messaging Server 5.2 and 6 versions are not on the same machine, transfer, extract and copy the Messaging Server 5.2 server-root directory to the Messaging Server 6 2005Q1 system. If your server versions are installed on the same machine, you can skip this step.

If your Message Store is too large to transfer from one system to another, you can transfer just the essential portions of the server instance to the new system. There are comments inside of the UpgradeMsg5toMsg6.pl which cover this in detail.

You don t have to copy the Messaging Server 5.2 store data to the Messaging Server 6 2005Q1 system, however, you must ensure that the Messaging Server 5.2 mboxlist directory is accessible during the upgrade process.

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 Messaging Server 6 2005Q1 version. For example:

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

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 Messaging Server 6 2005Q1.

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

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 2005Q1 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 of the Upgrade Utility

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 2005Q1 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).

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

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 2005Q1 is up and running.

Running the do_the_upgrade.sh Utility

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 2005Q1 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 2005Q1 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.

configutil Parameters


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

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 2005Q1, any Messaging Server 5.2 values are carried forward to the Messaging Server 6 2005Q1 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 2005Q1 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 2005Q1 system.

Migrating User Mailboxes

This section describes how to migrate user mailboxes from Messaging Server 5.2 to your Messaging Server 6 2005Q1 system. If you are upgrading Messaging Server 5.2 to Messaging Server 6 and upgrading the entire message store database, you do not need to follow this procedure. The make_mboxlistdb_changes.sh script described in the previous section can be used to upgrade your database more efficiently.

If you choose to migrate mailboxes using this procedure, do not map the partition paths to the Messaging Server 5.2 partitions and also do not run the make_mboxlist_changes.sh script.

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. You need to alter this manually. In addition, you should remove the invocation of the make_mboxlistdb_changes.sh script from your do_the_upgrade.sh script.

To move user mailbox data from Messaging Server 5.2 to Messaging Server 6 2005Q1 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.

Requirements

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

Migration Instructions

To migrate your user mailboxes from your 5.2 system to your Messaging Server 6 2005Q1 system:

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.

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.

For more information on mailUserStatus, see the Sun Java System Communcations Services Schema Reference Manual (http://docs.sun.com/doc/819-0113).

Ensure that both your 5.2 and 6 2005Q1 Messaging Servers are up and running during this process.

Change the mailHost attribute in all user entries from the old mail server to the new mail server.

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. (Use the ldapmodify that comes with Messaging and/or Directory Server. Do NOT use the Solaris ldapmodify.

For more information on mailhost, see the Sun Java System Communcations Services Schema Reference Manual.

On the old system, split your user entries into equal groups using the backup-groups.conf file. (You can also place the user names into files and use the -u option in step 6)

Move the user data from the Messaging Server 5.2 message store to the Messaging Server 6 2005Q1 message store.

This is done by backing up the Messaging Server 5.2 message store with the imsbackup utility and restoring the message store to Messaging Server 6 2005Q1 with imsrestore utility. For example, to migrate mailboxes from oldmail.siroe.com to newmail.siroe.com, run the following command on oldmail.siroe.com:

/<server-root>/bin/msg/store/bin/imsbackup -f- /<instance>/<group> \
| rsh newmail.siroe.com /opt/SUNWmsgsr/lib/msg/imsrestore.sh \

-f- -cy -v1

You can run multiple concurrent backup and restore sessions (one per group) to maximize the transfer rate into the new message store. See the Messaging Server Reference Manual (http://docs.sun.com/doc/819-0106) for more information about the imsbackup and imsrestore utilities as well as Backing Up and Restoring the Message Store.

Set Messaging Server 6 2005Q1 to be the new default messaging server for the system.

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).

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

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

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

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
Sun Java System Messaging Server 6 2005Q1 Administration Guide