Upgrading MailMarshal 5.5 to MailMarshal SMTP 2006

WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Upgrading MailMarshal
SMTP 5.5 Installations to
MailMarshal SMTP 2006
April, 2006
Contents
Introduction
2
Case 1: Standalone MailMarshal SMTP Server
2
Case 2: Array of MailMarshal SMTP Servers
10
Additional Resources
25
This document describes the process required to upgrade from MailMarshal SMTP version 5.5 to MailMarshal 2006 SMTP
(version 6.1.4.x) in two typical environments:
•
Standalone MailMarshal 5.5 email processing server
•
Array of MailMarshal 5.5 email processing servers
In this document, MailMarshal 5.5 SMTP is referred to as “MailMarshal 5.5,” and MailMarshal 2006 SMTP (version 6.1.4.x) is
referred to as “MailMarshal 2006.”
This document cannot be a definitive guide to all possible environments. For best results, plan your product upgrade and data
migration using this document in combination with the MailMarshal SMTP User Guide, Release Notes, and relevant Knowledge
Base articles.
1
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Introduction
This document guides you through the process of upgrading from MailMarshal 5.5 to
MailMarshal 2006. To complete the product upgrade and data migration processes,
you may have to complete a number of steps on various computers in your existing
MailMarshal SMTP installation.
This document presents the following typical MailMarshal SMTP configurations and
the steps required to upgrade each to MailMarshal 2006:
•
Case 1: A standalone MailMarshal 5.5 email processing server. For more
information, see “Case 1: Standalone MailMarshal SMTP Server” on page
2.
•
Case 2: An array of MailMarshal 5.5 email processing servers, typically
deployed in a DMZ. For more information see “Case 2: Array of
MailMarshal SMTP Servers” on page 10.
Notes:
• To upgrade from MailMarshal versions prior to 5.5, you must upgrade to MailMarshal
5.5 before you run the MailMarshal 2006 installer.
• If you are using Microsoft Desktop Engine (MSDE) as your database, references in this
document to Microsoft SQL Server (SQL) also apply to MSDE.
• Please refer to the Release Notes for general information about hardware and software
requirements.
Case 1: Standalone MailMarshal SMTP Server
This section describes the steps required to upgrade a MailMarshal 5.5 installation on
a single server (“standalone installation”)
Note: If your current MailMarshal 5.5 installation uses an array of MailMarshal
email processing servers, see “Case 2: Array of MailMarshal SMTP Servers,”
starting on page 10.
Standalone: Before and After the Upgrade to MailMarshal 2006
The following figure illustrates a typical MailMarshal 5.5 configuration using a
standalone email processing server.
Frequently, the MailMarshal SMTP server also hosts the Microsoft SQL Server. It may
also act as the organization’s internal email server (using third party email server
software or MailMarshal POP3). There may or may not be a DMZ in this configuration.
2
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
The following figure shows the minor configuration changes that occur when you
upgrade a standalone MailMarshal 5.5 server. The primary change is that the
MailMarshal SMTP server now also hosts the MailMarshal SMTP Array Manager. The
upgrade also creates a new MailMarshal 2006 database.
In the upgraded configuration, you can add additional email processing servers to
MailMarshal SMTP to create an array of email processing servers, called nodes. With
MailMarshal 2006, you can also deploy the Web-based Spam Quarantine
Management tool using Microsoft Internet Information Services (IIS).
Standalone: Product Upgrade and Data Migration Process Checklist
The following checklist identifies the steps required to upgrade a standalone
MailMarshal 5.5 server to a MailMarshal 2006 Array Manager and migrate data from
your MailMarshal 5.5 database. The checklist also provides cross-references to
detailed instructions for each step. Complete the steps in the following order.
Standalone Upgrade Procedure Checklist
1. Back up important MailMarshal SMTP configuration and database
files. For more information, see “Standalone Step 1: Back Up
Important MailMarshal SMTP Data” on page 3.
2. Upgrade the standalone MailMarshal 5.5 Master to MailMarshal
2006. For more information, see “Standalone Step 2: Upgrading to a
MailMarshal 2006 Array Manager” on page 5.
3. Run the MailMarshal Migration Wizard to migrate your database
records and quarantined email, archive, and log files. For more
information, see “Standalone Step 3: Migrating Your Data to
MailMarshal 2006” on page 8.
Standalone Step 1: Back Up Important MailMarshal SMTP Data
The first step in the upgrade process is to back up important MailMarshal 5.5 database
and configuration data files. The following table lists the files to back up and refers
you to additional information.
3
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
File Name or
Extension
*.mmr
Typical Location
Description
MailMarshal
SMTP server
MailMarshal 5.5 configuration information.
For more information, see “Backing Up the
MailMarshal SMTP Configuration” on page
4.
Additional MailMarshal SMTP
configuration data, SpamCensor extended
rules, and your MailMarshal SMTP user
group definitions. For more information, see
“Back Up Custom Information” on page 4.
Microsoft SQL Server (SQL) database. For
more information, see Marshal Knowledge
Base article Q10221: How do I back up my
filetype.cfg
*.xml
usergroups.txt
install path
install path\config
install path\config
MailMarshal
5.5 database
Microsoft SQL
Server computer
MailMarshal or WebMarshal database?
Quarantined and archived email which is migrated from MailMarshal 5.5 to
MailMarshal version 6.x SMTP will no longer be accessible in a MailMarshal 5.5
Console. If you wish to retain access to this email with a MailMarshal 5.5 Console you
can back up the contents of your \Rulesets folder.
Note: The contents of the \Rulesets folders can be very large depending on your
volume of email and your retention period.
Backing Up the MailMarshal SMTP Configuration
Back up your MailMarshal 5.5 configuration before you upgrade to MailMarshal 2006.
It is important to preserve your MailMarshal 5.5 configuration; however, the
configuration cannot be imported to MailMarshal 2006.
To back up the MailMarshal 5.5 configuration files:
1.
Start the MailMarshal Configurator on the MailMarshal 5.5 server.
2.
On the Tools menu, click Server Properties.
3.
On the Server Properties window, select the General tab.
4.
Click Export.
5.
Specify a storage location and file name, and then click Save.
6.
Click OK.
Back Up Custom Information
MailMarshal SMTP stores custom settings in a number of files. Use standard
Windows techniques to back up the following files.
File Name or
Extension
filetype.cfg
Typical Location
Description
install path
*.xml
install path\config
Additional MailMarshal SMTP
configuration data you have customized
SpamCensor extended rules
usergroups.txt
install path\config
Your MailMarshal SMTP user group
definitions
4
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
For example, if MailMarshal SMTP is installed in the default location for version 5.5,
\Program Files\NetIQ\MailMarshal, back up the files specified in the
table from the following folders:
\Program Files\NetIQ\MailMarshal
\Program Files\NetIQ\MailMarshal\config
Back Up the MailMarshal SMTP Database
Use standard SQL Server backup techniques to store a safe copy of your MailMarshal
5.5 database. Later in the upgrade, the Migration Wizard migrates the information so
you can access your data using MailMarshal 2006. For more information about backing
up a MailMarshal 5.5 database, see Marshal Knowledge Base article Q10221: How do
I back up my MailMarshal or WebMarshal database?
Standalone Step 2: Upgrading to a MailMarshal 2006 Server
The following steps upgrade your MailMarshal 5.5 server to a MailMarshal 2006
server and Array Manager. During this step, you will run the MailMarshal 2006 setup
program on your existing MailMarshal 5.5 server using the default settings.
The upgrade process leaves your MailMarshal 5.5 database in place, creates a new
MailMarshal version 6.0 database, and installs the MailMarshal 2006 Array Manager
component.
When the setup program is complete, run the MailMarshal 2006 Configurator to reload
and upgrade your MailMarshal rules. Finish Step 2 by making a backup copy of your
new MailMarshal SMTP configuration file.
To upgrade your MailMarshal 5.5 server to MailMarshal 2006:
1.
If you are upgrading MailMarshal within a DMZ, you may need to temporarily
open port 1433 (Microsoft SQL Server ODBC port) to allow communication with a
SQL Server in your trusted network. For more information, refer to the
documentation for your firewall or other perimeter defense tools.
2.
If you are using MSDE and hosting it on a Microsoft Small Business Server (SBS),
install MSDE 2000 on the server before you continue. For more information, see
Marshal Knowledge Base article Q10057: Does MailMarshal support Microsoft
Windows Small Business Server (SBS) 2003?
3.
On the MailMarshal 5.5 server, run the MailMarshal 2006 setup program from
the CD or Web download.
4.
On the autorun window, click Install MailMarshal 2006.
5.
Read the Welcome window, and then click Next.
6.
Read the License agreement. If you agree with the terms, click I accept the
terms of the license agreement, and then click Next.
7.
On the Setup Type window, click Custom Install and then click Next.
8.
On the Installation Options window, select Array Manager and SMTP Server
and then click Next.
5
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
9.
If you are using an existing MailMarshal installation that includes a database, on
the SQL Server Options window, click I want to use an existing installation
of SQL Server 2000 or MSDE 2000. Click Next.
If your existing MailMarshal SMTP configuration does not include a database,
you can click I want to install and use the Microsoft SQL Desktop Engine
(MSDE).
Notes:
• This window will not appear if MSDE or Microsoft SQL Server is installed on the
MailMarshal server.
• Depending on email volume and other factors, you may need to use Microsoft SQL Server
rather than MSDE. For help making this decision, see the MailMarshal SMTP Sizing
Guide.
• If you install MSDE, you may need to restart the computer, and then start the
MailMarshal installation from the beginning, in order to connect to MSDE.
6
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
10. On the Folder Locations window, specify the current location of your MailMarshal
5.5 folders. By default, MailMarshal 5.5 created the folders in \Program
Files\NetIQ\MailMarshal.
If you want to install MailMarshal in a different location, click Change. When
you have completed specifying a new location, and return to this window, click
Next.
11. On the Database window, specify the connection details for the new
MailMarshal 2006 database, and then click Next.
Note: Do not specify your current MailMarshal 5.5 database. Specify the
Microsoft SQL Server computer name or IP address, a name for the new
MailMarshal 2006 database, and the Microsoft SQL Server or Windows
credentials to access the database.
12. On the Ready to Install the Program window, click Install.
13. If you have Windows Management Instrumentation (WMI) services installed on
the computer, click Yes to restart the WMI service so the setup program can
continue.
7
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
14. On the License window, make a note of the new license number the setup
program generates for you. You may need the new License Key to reinstall
MailMarshal on this computer at a later time. Click OK.
15. When the setup program displays the Finish window, the MailMarshal 5.5 server
is upgraded to MailMarshal 2006 with the new MailMarshal 2006 database.
However, old data has not yet been migrated to the new database. When you
click Finish, by default the migration wizard is launched to migrate the data.
16. If you do not want to perform migration now, uncheck the Launch Migration
Wizard checkbox.
17. Click Finish.
Standalone Step 3: Migrating Your Data to MailMarshal 2006
MailMarshal 6.x introduced changes to the MailMarshal SMTP SQL database schema,
the MailMarshal SMTP folder structure, and some MailMarshal SMTP file naming
conventions. In this step of the upgrade process, you will use the MailMarshal SMTP
Migration Wizard to migrate the MailMarshal 5.5 email history database records and
the quarantined and archived email and associated log files to the new MailMarshal
2006 database and folder structure.
Note: Until you migrate your quarantined and archived email and associated log
files, you cannot view or manage the quarantined email using the MailMarshal
SMTP Console.
The following sections provide details instructions for completing these steps.
Folder and Filename Changes
MailMarshal 2006 revises the folder structure and file naming conventions to support
the new features and functions of the product.
Folder Structure Remapping
The following table shows how the MailMarshal 5.5 folders correspond to folders in
MailMarshal 2006. The table uses the default installation location, \Program
Files\NetIQ\MailMarshal.
MailMarshal 5.5 Folders
\MailMarshal\MMExp
MailMarshal 2006 Folders
\MailMarshal \Unpacking
\MailMarshal \Logging
(no SQL logging)
\MailMarshal \Logging
\DBLog
\ManagerDBLog
(new folders now include database activity
logs)
\MailMarshal \Queues
\Decryption
\Encryption
\Incoming
\Processed OK
\Sending
\MailMarshal \Quarantine
\Deadletter
\GUID (one for each Rulesets subfolder)
\Symbolic
\Rulesets subfolders
\ValidFingerprints
\MailMarshal
\Decryption
\Encryption
\Incoming
\Processed OK
\Sending
\MailMarshal
\Deadletter
N/A
\Rulesets
\Rulesets subfolders
\ValidFingerprints
8
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
The MailMarshal SMTP setup program duplicates your MailMarshal 5.5 and earlier
\Rulesets folder structure in the new \Quarantine\Symbolic folder, copies the \Rulesets
folder structure, and copies all folder data to the new structure. However, the setup
program does not alter the MailMarshal 5.5 filenames to MailMarshal 6.x format.
File Naming Changes
MailMarshal 6.x introduced the ability to use multi-node arrays. This enhancement
required changes to the quarantine and archive email and associated log file naming
conventions. The Migration Wizard renames the files as it migrates your MailMarshal
5.5 data to the new folder structure.
The following table shows the file naming convention changes in MailMarshal 2006.
The new naming convention uses four digits before the extensions *.mml and *.log to
indicate which MailMarshal 2006 server quarantines the message.
MailMarshal 5.5 Filenames
B000000010.00000010.mml
B000000010.00000010.log
MailMarshal 2006 Filenames
B41e5befe000.000000000002.0001.mml
B41e5befe000.000000000002.0001.log
Running the MailMarshal SMTP Migration Wizard
Run the MailMarshal SMTP Migration Wizard only after you have upgraded your
standalone MailMarshal 5.5 email processing server to MailMarshal 2006. Use the
MailMarshal Migration Wizard to complete the following tasks:
•
Migrate MailMarshal 5.5 email history database records to the new
MailMarshal version 6.0 database
•
Migrate your MailMarshal 5.5 quarantined and archived email and
associated log files in the \Rulesets folder to the MailMarshal SMTP Array
Manager \Quarantine folder
Note: To ensure upgraded messages are logged with the correct timestamp,
ensure the Microsoft SQL Server hosting the new MailMarshal 2006 database
and the upgraded MailMarshal 2006 Array Manager are in the same time zone.
The wizard converts the internal representation of times from local time to UTC.
The migration process can take a long time (hours or days), depending on the volume
of database records and file data. MailMarshal continues to process new email
messages while the wizard is running.
To run the MailMarshal SMTP Migration Wizard:
1.
By default, the Migration Wizard is launched at the end of the upgrade
installation process. To start the Migration Wizard at another time, click Start >
Programs > MailMarshal > MailMarshal Tools > MailMarshal Migration
Tool.
2.
Read the Welcome window, and then click Next.
3.
Click Migrate both the email history database records and the
quarantined and archived email and associated log files and then click
OK.
Note: If you need to stage the upgrade and migration process due to time or
other constraints, you can click Migrate only the email history database
records and run the wizard again later to migrate the quarantined and
archived email and associated log files.
4.
If the MailMarshal 5.5 database connection information is not stored in the
MailMarshal 2006 Configuration file, the wizard displays the Select Database
window. Specify the MailMarshal 5.5 database location and credentials, and
then click OK.
9
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
5.
Select Automatic mapping and then click Next. This option is only valid if you
have not yet completed the initial migration of MailMarshal 5.5 information.
6.
Click Start to begin the data migration process.
7.
The Status window displays the wizard progress. The wizard starts by migrating
the email history database records and then continues by migrating the
quarantined and archived email and associated log files.
8.
The import process can take a long time (hours or days) depending on the volume
of data. If you need to interrupt the process, click Stop. You can rerun the wizard
later without losing data to complete the migration.
Note: If the wizard encounters a message it cannot convert, you can choose to
abort, retry, ignore the message, or ignore all problem messages. By choosing to
ignore all problem messages, you can allow the wizard to run unattended. The
wizard logs activity in the file <Installation
path>\Logging\migration.log
Review the migration log text file to identify any messages the Migration Wizard
cannot convert.
9.
When the Status window indicates the data migration is complete, click Next.
10. The Finished window displays a summary of the migration. Click Finish to close
the wizard.
If you have interrupted the Migration Wizard before the data migration is complete,
you can run the Wizard again at a later time to complete the process without losing
data. Be sure to check the status in the migration.log file to identify and
handle any unmigrated data.
For more information about configuring and using your upgraded MailMarshal 2006
product, see the User Guide for MailMarshal 2006.
Case 2: Array of MailMarshal SMTP Servers
This section describes the steps required to upgrade an array of MailMarshal email
processing servers, usually in the DMZ (“5.5 array installation”)
Note: If your current MailMarshal 5.5 installation uses a standalone
MailMarshal email processing server, see “Case 1: Standalone MailMarshal
SMTP Server,” starting on page 2.
Array: Existing MailMarshal 5.5 Configuration
The following figure illustrates a typical MailMarshal 5.5 configuration using multiple
email processing servers in the DMZ, labeled MM1, MM2, and MM3.
10
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
In this MailMarshal 5.5 configuration, you normally run the MailMarshal Configurator
by logging on to the Master email processing server (MM1) in the DMZ. However,
other email administrators are able to run the MailMarshal SMTP Management
Console from a computer in the trusted network.
In the scenario shown in the previous figure, the following ports are typically open
between the DMZ and trusted network.
Port
25
389
1433
19001
Owner
SMTP
LDAP
Microsoft SQL
MailMarshal
Description
Email traffic
LDAP connectivity to your directory server
ODBC for MailMarshal logging to database
MailMarshal SMTP Management Console
To complete an upgrade to MailMarshal 2006, you must upgrade one email server to
the MailMarshal 2006 Array Manager, and then upgrade the additional MailMarshal
5.5 email processing servers to MailMarshal 2006 nodes. You must also migrate data
on each upgraded server.
Array: Configuration After Upgrading to MailMarshal 2006
When the upgrade to MailMarshal 2006 is complete, your environment should be
similar to the following figure. The new configuration still has email processing
servers, called nodes, inside the DMZ (MM1, MM2, and MM3). However, a new
component, the MailMarshal SMTP Array Manager (labeled MM4), is moved to the
trusted network. The detailed steps refer you to the proper computers using the MM1,
MM2, MM3, and MM4 notation.
11
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Because the Array Manager communicates with the email processing nodes in the
DMZ as well as the other services MailMarshal SMTP requires, only two ports must be
open between the DMZ and trusted network, resulting in a more secure configuration.
Using MailMarshal 2006 with the Array Manager, you must open only the following
ports to your trusted network.
Port
25
19001
Owner
SMTP
MailMarshal
Description
Email traffic
MailMarshal SMTP Array Manager to
MailMarshal SMTP email processing nodes
Using MailMarshal 2006 also simplifies maintaining your MailMarshal SMTP
configuration since the Array Manager replicates email policy to each of the nodes in
the MailMarshal SMTP array. You can run the MailMarshal SMTP Configurator inside
the trusted network. All the other components MailMarshal SMTP communicates with
reside within the trusted network.
If you want to provide MailMarshal SMTP end users with the MailMarshal SMTP
Spam Quarantine Management tool, you can deploy Microsoft Internet Information
Server (IIS). The Spam Quarantine Management tool allows end users to review their
quarantined email and to specify a personal email address blacklist and whitelist.
You can install the MailMarshal SMTP Array Manager, Microsoft SQL Server, and
Microsoft IIS on just one computer, but for clarity, the figure shows these applications
installed on separate computers. For more information about deploying Microsoft IIS
and using the Spam Quarantine Management tool, see the User Guide for MailMarshal
2006.
Array: Upgrade and Migration Process Checklist
The following checklist includes the steps required to upgrade a MailMarshal 5.5 array
installation to MailMarshal 2006, and provides cross-references to the detailed
instructions. Complete the steps in the following order.
12
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Array Upgrade Procedure Checklist
1. Back up important MailMarshal configuration and database files. For
more information, see “Array Step 1: Back Up Important MailMarshal
SMTP Data” on page 13.
2. Upgrade your MailMarshal 5.5 Master server to MailMarshal 2006.
For more information, see “Array Step 2: Upgrading the MailMarshal
5.5 Master Server to MailMarshal 2006” on page 14.
3. Move the upgraded MailMarshal 2006 Array Manager components
from the DMZ to a computer in your trusted network. For more
information, see “Array Step 3: Moving the MailMarshal 2006 Array
Manager” on page 17.
4. Run the MailMarshal Migration Wizard to migrate your email history
database records and quarantined and archived email and associated
log files. For more information, see “Array Step 4: Install and Run the
Migration Wizard” on page 22.
5. Repeat the upgrade installation process on each MailMarshal 5.5
server. Connect the upgraded nodes to the MailMarshal 2006 Array
Manager, and run the Migration Wizard on each upgraded node. For
more information, see “Array Step 5: Upgrade Additional
MailMarshal 5.5 Servers” on page 24.
Array Step 1: Back Up Important MailMarshal SMTP Data
The first step in the upgrade process is to back up important MailMarshal 5.5 database
and configuration files. Back these files up to a network share or removable media to
simplify moving the Array Manager later in the upgrade process.
The following table lists the files to back up and refers you to additional information.
File Name or
Extension
*.mmr
Typical Location
Description
MailMarshal
SMTP server
MailMarshal 5.5 configuration information.
For more information, see “Backing Up the
MailMarshal SMTP Configuration” on page
13.
Additional MailMarshal SMTP
configuration data, SpamCensor extended
rules, and your MailMarshal SMTP user
group definitions. For more information, see
“Back Up Custom Information” on page 14.
Microsoft SQL Server (SQL) database. For
more information, see Marshal Knowledge
Base article Q10221: How do I back up my
filetype.cfg
*.xml
usergroups.txt
install path
install path\config
install path\config
MailMarshal
5.5 database
Microsoft SQL
Server computer
MailMarshal or WebMarshal database?
Quarantined and archived email which is migrated from MailMarshal 5.5 to
MailMarshal version 6.x SMTP will no longer be accessible in a MailMarshal 5.5
Console. If you wish to retain access to this email with a MailMarshal 5.5 Console you
can back up the contents of your \Rulesets folder.
Note: The contents of the \Rulesets folders can be very large depending on your
volume of email and your retention period.
Backing Up the MailMarshal Configuration
Back up your MailMarshal 5.5 configuration before you begin installing the
MailMarshal 2006 upgrade.
13
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
To back up the MailMarshal SMTP configuration files:
1.
Start the MailMarshal 5.5 Configurator on the Master server.
2.
On the Tools menu, click Server Properties.
3.
On the Server Properties window, select the General tab.
4.
Click Export.
5.
Specify a storage location and file name and then click Save.
Tip: Store the configuration data on a network share or removable media to
simplify moving the Array Manager from this computer to another computer later
in the upgrade process.
6.
Click OK.
Back Up Custom Information
When you configure MailMarshal SMTP to enforce your email policies, MailMarshal
SMTP stores your custom settings in a number of files. Use standard Windows
techniques to back up the following files.
File Name or
Extension
filetype.cfg
Typical Location
Description
install path
*.xml
usergroups.txt
install path\config
install path\config
Additional MailMarshal SMTP
configuration data you have customized
SpamCensor extended rules
Your MailMarshal SMTP user group
definitions
For example, if MailMarshal SMTP was installed in the default location for version 5.5,
\Program Files\NetIQ\MailMarshal, back up the files specified in the
table from the following folders:
\Program Files\NetIQ\MailMarshal
\Program Files\NetIQ\MailMarshal\config
Back Up the MailMarshal SMTP Database
Use standard SQL Server backup techniques to store a safe copy of your MailMarshal
5.5 database. Later in the upgrade, the Migration Wizard migrates the information so
you can access your data using MailMarshal 2006. For more information about backing
up a MailMarshal 5.5 database, see Marshal Knowledge Base article Q10221: How do
I back up my MailMarshal or WebMarshal database?
Array Step 2: Upgrading the MailMarshal 5.5 Master Server to
MailMarshal 2006
The following steps upgrade your MailMarshal 5.5 Master server to the MailMarshal
2006 Array Manager. During this step, run the MailMarshal 2006 setup program on
your existing MailMarshal 5.5 Master server using the default settings to create a new
database on your SQL Server.
The upgrade process leaves your MailMarshal 5.5 database in place, creates a new
MailMarshal 2006 database, and installs the MailMarshal 2006 Array Manager on the
Master server. Next, run the MailMarshal SMTP Configurator to reload existing
MailMarshal 5.5 rules. Finish by making a backup copy of the new configuration file.
To upgrade the MailMarshal 5.5 Master server to MailMarshal 2006:
1.
If you are upgrading MailMarshal SMTP within a DMZ, you may need to
temporarily open port 1433 (SQL Server port) to allow communication with a SQL
14
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Server in your trusted network. For more information, refer to the documentation
for your firewall or other perimeter defense tools.
2.
If you are using MSDE and hosting it on a Microsoft Small Business Server (SBS),
install MSDE on the server before you continue. For more information, see
Marshal Knowledge Base article Q10057: Does MailMarshal support Microsoft
Windows Small Business Server (SBS) 2003?
3.
On the MailMarshal 5.5 server, run the MailMarshal 2006 setup program from
the CD or Web download.
4.
On the autorun window, click Install MailMarshal 2006.
5.
On the Welcome window, click Next.
6.
Read the License agreement. If you agree with the terms, click I accept the
terms of the license agreement. Click Next.
7.
On the Upgrade Type window, click I want to install a full version of
MailMarshal on this server and then click Next.
8.
If you are using an existing MailMarshal SMTP installation that includes a
database, on the SQL Server Options window, click I want to use an existing
installation of SQL Server 2000 or MSDE 2000. Click Next.
15
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
If your existing MailMarshal SMTP configuration does not include a database,
you can click I want to install and use the Microsoft SQL Desktop Engine
(MSDE).
Note: Most array installations will require use of Microsoft SQL Server rather
than MSDE. For help making this decision, see the MailMarshal SMTP Sizing
Guide.
9.
On the Folder Locations window, specify the current location of your MailMarshal
5.5 folders. By default, new 5.5 installations were installed in \Program
Files\NetIQ\MailMarshal.
If you want to install MailMarshal in a different location, click Change to specify
the new location, and then click Next.
10. On the Database window specify the connection details for the new MailMarshal
2006 database, and then click Next.
Note: Do not specify your current MailMarshal 5.5 database. Specify the
Microsoft SQL Server computer name or IP address, a name for the new
MailMarshal 2006 database, and the credentials to access the database.
16
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
11. On the Ready to Install the Program window, click Install.
12. If you have Windows Management Instrumentation (WMI) services installed on
the computer, click Yes to restart the WMI service to allow setup to continue.
13. On the License window, make a note of the new license number the setup
program generates for you. You may need the new License Key to reinstall
MailMarshal on this computer at a later time. Click OK.
14. On the Finish window, choose to whether to run the Migration Wizard by
checking or unchecking the Launch Migration Wizard checkbox.
Note: Unchecking this checkbox is recommended. Data migration can take a long
time, and most organizations will prefer to complete the server upgrades before
migrating data. However, if you wish to migrate the data from this server
immediately, you can do so. Data migration is covered in “Array Step 4: Run the
Migration Wizard” on page 22.
15. Click Finish.
The upgraded MailMarshal 5.5 Master server is now upgraded to the Array Manager
for MailMarshal 2006. In the remainder of this document, this upgraded computer is
referred to as MM1.
At this point, this server is upgraded to MailMarshal 2006. However, MailMarshal 5.5
data has not yet been migrated to the new configuration and you cannot yet manage
email from the MailMarshal SMTP Console. You will migrate your MailMarshal 5.5
data in a later step.
Array Step 3: Moving the MailMarshal 2006 Array Manager
This section describes the steps required to move the upgraded MailMarshal 2006
Array Manager from MM1 in the DMZ to a new computer, such as MM4, in the
trusted network.
Moving the Array Manager into the trusted network makes the MailMarshal SMTP
configuration easier to manage and more secure, requiring fewer open ports between
the DMZ and the trusted network.
The following procedure requires you to perform steps on at least two computers:
•
The upgraded MailMarshal 2006 Array Manager in the DMZ (MM1)
17
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
•
The computer in the trusted network to which you are moving the
MailMarshal 2006 Array Manager (MM4)
You also must also be able to run Microsoft SQL Server Enterprise Manager (or
command line tools) to remove a temporary database you create during the installation
process.
The following table provides an overview of the steps required to move a newly
upgraded MailMarshal 2006 Array Manager in the DMZ (on MM1) to a new computer
in the trusted network (MM4). The table also identifies the computers on which you
perform the steps.
On this computer…
New computer in trusted
network where you want to
move the Array Manager (MM4)
SQL Server hosting MailMarshal
database (SQL Server host)
MailMarshal SMTP Array
Manager in the DMZ (MM1)
Perform these steps…
• Install MailMarshal 2006 with Array Manager
only option
• Create a temporary database during the
installation process (TempMMDB)
• Point the new Array Manager to the previously
upgraded database (MailMarshal6)
Delete the temporary database created during
the installation (TempMMDB)
• Remove the Array Manager component
• Rejoin the server to the array by pointing to the
IP address of the new Array Manager in the
trusted network (MM4)
Note: The computer to which you move the Array Manager software (MM4) must
not have any MailMarshal SMTP components installed. Ensure any MailMarshal
SMTP services and tools are removed prior to installing the Array Manager
component.
To install the MailMarshal SMTP Array Manager component on the new
computer in the trusted network:
1.
On the computer in the trusted network where you want to move the Array
Manager (MM4), run the MailMarshal SMTP setup program. On the autorun
window, click Install MailMarshal 2006.
2.
On the Welcome window, click Next.
3.
Read the License agreement. If you agree with the terms, click I accept the
terms of the license agreement. Click Next.
4.
On the Setup Type window, click Custom Install and then click Next.
5.
On the Installation Options window, select Array Manager and deselect
(uncheck) SMTP Server and then click Next.
6.
On the SQL Server Options window, click I want to use an existing
installation of SQL Server 2000 or MSDE 2000. Click Next.
18
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
7.
Choose the installation location, and then click Next.
8.
On the Database window, specify details for a new temporary database that you
will later delete, such as TempMMDB. Specify the correct Microsoft SQL Server
name or IP address, the temporary database name, and access credentials.
Note: Do not specify the new MailMarshal 2006 database that was created
when you upgraded MM1. Specify a temporary “dummy” database that you will
later delete.
9.
On the Ready to Install window, click Install.
10. After the installation is complete, the setup program prompts you to start the
MailMarshal SMTP Configuration Wizard. This Wizard prompts you for basic
information that will later be overwritten with the backup configuration you
previously saved. The data you enter here is not important. Complete the required
fields on the windows of this Wizard, and then click Finish. The MailMarshal
Configurator main window displays.
11. On the Configurator Tools menu, click MailMarshal Properties.
19
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
12. On the MailMarshal Manager Properties window, click Restore.
13. Navigate to the backup file you created from the upgraded MailMarshal 2006
Array Manager in the DMZ (MM1). Choose the backup file you created and click
Open.
14. When MailMarshal SMTP has restored the configuration, the Configurator
prompts you to commit the changes. Click OK.
15. On the Tools menu, click Commit Configuration Changes.
16. When prompted to restart services and commit the changes, click Yes.
17. Click OK.
18. On the Windows Start menu, click Start > Programs > MailMarshal >
MailMarshal Tools > MailMarshal Server Tool.
20
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
19. On the Database tab, click Change.
20. Specify the SQL Server name or IP address and the name of the MailMarshal
2006 database that you created when upgrading the MM1 server, and the
credentials for accessing the database.
21. The MailMarshal Server Tool prompts you that a valid MailMarshal 2006
database already exists. Click Use to continue using the upgraded MailMarshal
2006 database. The database contains the upgraded MailMarshal 5.5
configuration but does not yet contain any email history or reporting data. You
will migrate your data in later steps.
22. When prompted to restart the MailMarshal SMTP MMArrayManager service,
click Yes.
Perform the following steps on the MailMarshal SMTP Array Manager in the
DMZ (MM1).
23. Run the MailMarshal setup program.
24. Click Modify, and then click Next.
21
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
25. Read the License agreement. If you agree with the terms, click I accept the
terms of the license agreement, and then click Next.
26. On the Setup Type window, click Custom Install, and then click Next.
27. On the Installation Options window, deselect (uncheck) Array Manager,
ensure that SMTP Server is selected, and then click Next.
28. On the MailMarshal Array window, specify the name or IP address of the newly
installed Array Manager computer (MM4) and the port number. If the MM1
server is in a DMZ and not part of the Windows domain in which the Array
Manager MM4 is a member, provide a valid Username, Password, and Domain.
You can provide credentials for any user account to which you have delegated
appropriate rights under the Manager Security tab of the MailMarshal Properties
window in the MailMarshal Configurator on the Array Manager computer. When
you have specified this information, click Next.
29. If you are prompted to restart the Windows Management Instrumentation (WMI)
services, click Yes.
30. When prompted to rejoin the array, click Rejoin.
Perform the following step on the new Array Manager computer in the trusted
network (MM4).
31. On the Start menu, click Start >Programs > MailMarshal > MailMarshal
Configurator. Ensure the computer name for the MM1 server appears in the list
and that all services on the upgraded MailMarshal 2006 server are running.
Perform the following step on the Microsoft SQL Server computer.
32. Delete the temporary database you created in Step 8 to conserve space on the
SQL Server disk.
Array Step 4: Run the Migration Wizard
MailMarshal 6.x introduced changes to the MailMarshal SMTP SQL database schema,
the MailMarshal SMTP folder structure, and some MailMarshal SMTP file naming
conventions. In this step of the upgrade process, you will use the MailMarshal SMTP
Migration Wizard to migrate the MailMarshal 5.5 email history database records and
the quarantined and archived email and associated log files to the new MailMarshal
2006 database and folder structure.
22
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
Note: Until you migrate your quarantined and archived email and associated log
files, you cannot view or manage the quarantined email using the MailMarshal
SMTP Console.
The following sections provide details instructions for completing these steps.
The file structure and naming conventions changed in MailMarshal 6.x. For more
information and details about the changes, see “Folder and Filename Changes” on
page 11.
Running the MailMarshal SMTP Migration Wizard
Run the MailMarshal SMTP Migration Wizard after you have upgraded your
MailMarshal 5.5 Master server (MM1) to MailMarshal 2006. Use the MailMarshal
SMTP Migration Wizard to complete the following tasks:
•
Migrate MailMarshal 5.5 email history database records to the new
MailMarshal 2006 database
•
Migrate your MailMarshal 5.5 quarantined and archived email and
associated log files in the \Rulesets folder to the MailMarshal Array
Manager \Quarantine folder
Note: To ensure upgraded messages are logged with the correct timestamp,
ensure the Microsoft SQL Server hosting the new MailMarshal 2006 database
and the upgraded MailMarshal 2006 Array Manager are in the same time zone.
The wizard converts the internal representation of times from local time to UTC.
The migration process can take a long time (hours or days), depending on the volume
of database records and file data. MailMarshal SMTP continues to process new email
messages while the wizard is running.
To run the MailMarshal SMTP Migration Wizard:
1.
On the upgraded MailMarshal 5.5 server (MM1), start the Migration Wizard.
Click Start > Programs > MailMarshal > MailMarshal Tools > MailMarshal
Migration Tool.
2.
Read the Welcome window, and then click Next.
3.
Click Migrate both the email history database records and the
quarantined and archived email and associated log files and then click
OK.
Note: If you need to stage the upgrade and migration process due to time or
other constraints, you can click Migrate only the email history database
records and run the wizard again later to migrate the quarantined and
archived email and associated log files.
4.
If the MailMarshal 5.5 database connection information is not stored in the
MailMarshal 2006 Configuration file, the wizard displays the Select Database
window. Specify the MailMarshal 5.5 database location and credentials, and
then click OK.
5.
Select Automatic mapping and click Next. This option is available only if the
initial migration of this database to MailMarshal 2006 format has not been
completed.
6.
Click Start to begin the data migration process. The Status window displays the
wizard progress. The wizard starts by migrating the email history database
records and then continues by migrating the quarantined and archived email and
associated log files.
23
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
7.
The import process can take a long time (hours or days) depending on the volume
of data. If you need to interrupt the process, click Stop. You can rerun the wizard
later without losing data to complete the migration.
Note: If the wizard encounters a message it cannot convert, you can choose to
abort, retry, ignore the message, or ignore all problem messages. By choosing to
ignore all problem messages, you can allow the wizard to run unattended. The
wizard logs activity in the file <Installation
path>\Logging\migration.log Review the migration log text file
to identify any messages the Migration Wizard cannot convert.
8.
When the Status window indicates the data migration is complete, click Next.
9.
The Finished window displays a summary of the migration. Click Finish to close
the wizard.
If you have interrupted the Migration Wizard before the data migration is complete,
you can run the Wizard again at a later time to complete the process. Be sure to check
the status in the migration.log file to identify and handle any unmigrated data.
Array Step 5: Upgrade Additional MailMarshal 5.5 Servers
After you have installed and moved the upgraded MailMarshal SMTP Array Manager
to the computer in the trusted network (MM4), upgrade any additional MailMarshal
5.5 servers, such as MM2 and MM3, and connect them to the MailMarshal 2006 array
by completing the following additional steps:
•
Run the setup program on each MailMarshal 5.5 server, such as MM2 and
MM3, that you want to upgrade to MailMarshal 2006 nodes. Connect the
upgraded nodes to the MailMarshal 2006 Array Manager (MM4)
•
Run the Migration Wizard on each upgraded node (such as MM2 and MM3)
to transfer your MailMarshal 5.5 data to MailMarshal 2006
Upgrading Additional MailMarshal 5.5 Servers
Complete the following steps on each additional MailMarshal 5.5 email processing
server in your DMZ, such as MM2 and MM3.
To upgrade additional MailMarshal 5.5 servers:
1.
On another MailMarshal 5.5 server in the DMZ, such as MM2 or MM3, run the
MailMarshal 2006 setup program.
2.
Read the License agreement. If you agree with the terms, click I accept the
terms of the license agreement, and then click Next.
3.
On the Setup Type window, click Custom Install and then click Next.
4.
On the Upgrade Type window, click I wish to install the node components
onto this server and then click Next.
24
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
5.
On the Folder Locations window, specify the current location of your MailMarshal
folders. The setup program creates the new folders in the installation folder,
which for new 5.5 installations defaulted to \Program Files\NetIQ\MailMarshal. If
you want to install MailMarshal SMTP on a different location, click Change and
specify the new location, and then click Next.
6.
On the MailMarshal Array window, specify the name or IP address and
credentials for the Array Manager computer (MM4). If the computer is in a DMZ
and not part of the same Windows domain as the Array Manager computer, you
must provide credentials. You can supply credentials for any account to which
you have given proper rights on the Manager Security tab of the MailMarshal
Properties window.
7.
Click Install.
8.
If you have Windows Management Instrumentation (WMI) services installed on
the computer, click Yes to restart the WMI service.
9.
On the Finish window, check the Launch Migration Wizard checkbox.
10. Click Finish.
11. Run the Migration Wizard. For more information, see “Array Step 4: Install and
Run the Migration Wizard” on page 22.
12. Repeat Steps 1 to 11 from this task on each additional MailMarshal 5.5 server,
such as MM3 or others.
13. On the MailMarshal SMTP Array Manager computer (MM4), run the MailMarshal
Configurator. Ensure the MailMarshal SMTP service on each node is started and
running. From the Tools menu, click Commit Configuration Changes.
Note: This final step ensures that any changed configuration from the Array
Manager is immediately applied to the nodes.
Additional Resources
If the upgrade process described in this document does not apply to your environment,
or if you have questions, contact Marshal Technical Support.
For more information about upgrade issues, see Marshal Knowledge Base article
Q11025: Upgrading from MailMarshal 5.5 to MailMarshal 2006.
25
WHITEPAPER – MailMarshal SMTP – Upgrading to MailMarshal SMTP 2006
For more information about configuring and administering MailMarshal SMTP 2006,
see the User Guide for MailMarshal SMTP 2006.
26
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE
TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE
AGREEMENT OR NON-DISCLOSURE AGREEMENT, MARSHAL LIMITED PROVIDES THIS DOCUMENT AND THE SOFTWARE
DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME
JURISDICTIONS DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS;
THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
This document and the software described in this document may not be lent, sold, or given away without the prior written
permission of Marshal, except as otherwise permitted by law. Except as expressly set forth in such license agreement or nondisclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a
retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written
consent of Marshal. Some companies, names, and data in this document are used for illustration purposes and may not represent
real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein. These changes may be incorporated in new editions of this document. Marshal may
make improvements in or changes to the software described in this document at any time.
© 2006 Marshal Limited, all rights reserved.
U.S. Government Restricted Rights: The software and the documentation are commercial computer software and documentation
developed at private expense. Use, duplication, or disclosure by the U.S. Government is subject to the terms of the Marshal
standard commercial license for the software, and where applicable, the restrictions set forth in the Rights in Technical Data and
Computer Software clauses and any successor rules or regulations.
Marshal, MailMarshal, the Marshal logo, WebMarshal, Security Reporting Center and Firewall Suite are trademarks or registered
trademarks of Marshal Limited or its subsidiaries in the United Kingdom and other jurisdictions. All other company and product
names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective
companies.
Marshal’s Worldwide and EMEA HQ
Marshal Limited,
Renaissance 2200,
Basing View,
Basingstoke,
Hampshire RG21 4EQ
United Kingdom
Americas
Marshal Inc.
5555 Glenridge Connector,
Suite 200,
Atlanta,
GA 30342
USA
Asia-Pacific
Marshal Software (NZ) Ltd
Suite 1, Level 1, Building C
Millennium Centre
600 Great South Road
Greenlane, Auckland
New Zealand
Phone: +44 (0) 1256 848080
Fax:
+44 (0) 1256 848060
Phone: +1 404 459 2890
Fax
+1 404 759 2549
Phone: +64 9 984 5700
Fax:
+64 9 984 5720
Email:emea.sales@marshal.com
Email: americas.sales@marshal.com
info@marshal.com | www.marshal.com
Email: apac.sales@marshal.com
27