Upgrading ListManager
The ListManager installer makes upgrading easy! Simply select upgrade when prompted. However, there are some steps you should take before upgrading to prepare yourself.
WARNING: Please back up your database before upgrading. If you encounter a problem while upgrading, you may not be able to recover your data without a backup.
Important PostgreSQL note: earlier versions of ListManager supported PostgreSQL 7.1.3 only. To upgrade to ListManager 7.1.3 using PostgreSQL, you will need to upgrade your version of PostgreSQL to 7.3.2 in order to have ListManager run properly. See PostgreSQL and ListManager for more information.
IMPORTANT NOTE FOR USERS OF 5.0 AND EARLIER: Headers and footers are no longer automatically appended to mailings sent via the admin web interface. You must add the unsubscribe information for your mailings manually. See Content: Insert Field: Unsubscribe for more information on how to do so quickly and easily.
Getting Ready
- We recommend that you evaluate ListManager 7.0 on a test machine. If you prefer to use your production ListManager server, only do so if you plan to upgrade it to version 7.0.
DO NOT use the 7.0 release on your production server if you might want to go back to an older (pre-v5.0) version of ListManager. Once you upgrade to 7.0, you will not be able to downgrade back to the older version.
- Be sure that ListManager is not running when you upgrade it.
- ListManager 7.0 uses its own ListManager web server. If you are running another web server on the machine that is running ListManager, and you only use it for ListManager, you should stop it before installing. ListManager's web server may coexist with your web server, and will be installed on a higher port if port 80 is taken.
- ListManager 6.0h and higher now uses its own DNS resolver. If you have a firewall, you must
configure it so that ListManager can resolve DNS on port 53. If you have a firewall and you are
upgrading from an earlier version, we HIGHLY recommend testing ListManager on a development
server before you upgrade your production server to ensure ListManager can perform its DNS
resolutions properly. See Your Firewall and ListManager for more information.
- The old words table will no longer be available after upgrading, which may affect some custom programs. For more information about the new database table structure, see the Programmer's Guide.
Preparing Your Data
4.2 and earlier versions:
ListManager 5.0 and higher no longer uses FoxPro as its database format; see Supported Platforms for a list of databases you may use with ListManager. ListManager 7.0 can migrate your old Foxpro-format database to your SQL database automatically.
We recommend you perform a "dbupgrade" before upgrading to 7.0. To perform dbupgrade, stop ListManager, and open a command prompt. Cd to the directory which contains lyris.exe. Type:
lyris dbupgrade
Dbupgrade may take several hours, depending on the size of your data.
Be sure to back up your "db" directory (found in your Lyris directory) before upgrading.
Special Note: If you are upgrading from 4.x and using the embedded database MSDE, check the total size of your db directory. MSDE is limited to 2 GB for all its tables, so if you have too much data, the upgrade will not succeed. Your account representative can tell you more about external databases you can use with ListManager.
5.0 and later versions:
It is recommended that you back up your database before upgrading. For information on backing up MSDE, see Backing Up MSDE.
Get a Serial Number
You can use the MSDE and PostgreSQL versions of ListManager 7.0 "Standard" without a Serial Number in a limited capacity (200 members max, MSDE and PostgreSQL installed locally).
If you want to test a larger or external database, evaluate the "Pro" feature set, or connect ListManager to Microsoft SQL Server or Oracle, please contact your account representative to obtain an evaluation Serial Number.
Serial codes from versions 4.2 and lower are no longer valid with ListManager 5.0 and higher, so contact an account representative to purchase an upgrade and to receive a new serial code. Your account representative can also tell you if your 5.0 and higher serial code allows you to upgrade to the current version.
Upgrading ListManager
Upgrading without Moving ListManager
When running the ListManager installer, select "upgrade" instead of "new install", and provide the installer with the path where ListManager is currently installed. The installer will automatically copy the data if necessary and upgrade the database
Moving and Upgrading from 4.2 or Earlier
1. Install ListManager on the new machine. Select "New Install" when prompted by the installer, and complete the installation.
2. Shut down ListManager if you started it after the installation.
3. Copy the db directory from your old ListManager installation to the ListManager directory on your new ListManager machine. On Unix, copy the /db directory to the ListManager /bin subdirectory.
4. To copy over your old data, open a command prompt, and cd to the ListManager directory. On the command line, type
lm copy2sql
This process may take several hours, depending on how large your database is.
5. Set your serial code on the command line with the following command;
lm serial yourcode
6. Make sure ListManager is listening to all IP addresses on the machine by running the following command from the command line:
lm tcpip
7. Start ListManager.
8. Go to Utilities: Administration: Sites, and edit any sites you have, so that the Internet Host Name field for each site is the name of your new ListManager machine.
You're done!
Moving and Upgrading from 5.0 or Later
1. Install ListManager on the new machine. Select "New Install".
2. When the installer requests the database information, you may provide the information for your earlier ListManager installation—but DO NOT have the installer create the tables for you—this will delete your database!
Alternatively, you may create a database or user just for the installation, and change which database ListManager uses by editing lmcfg.txt with a plain text editor. See Connecting to Your Database with lmcfg.txt for more information about editing this file.
3. Shut down ListManager if you started it after the installation.
4. To allow your database to be used with your new ListManager machine, you'll need to change the machine name in the Config_ table. To do so, run the following command on the command line:
lm configmove
5. To upgrade your database, open a command prompt. On the command line, type
lm dbupgrade
This process may take several hours, depending on how large your database is.
6. Make sure ListManager is listening to all IP addresses on the machine by running the following command from the command line:
lm tcpip
7. Start ListManager.
8. Go to Utilities: Administration: Sites, and edit any sites you have, so that the Internet Host Name field for each site is the name of your new ListManager machine.
You're done!
After Upgrading ListManager
Message threading and searchable archives will not be available immediately after upgrading from versions 5.0 and earlier. ListManager 7.0 has new methods of threading and indexing archives so they are searchable.
After upgrading to 7.0, ListManager will attempt to determine whether a message is a response to a previous
message in that same list or whether it is starting a new 'thread' of discussion. This threading will
be shown in the ListManager web interface.
ListManager 7.0 also has a new improved method for full-text archive searching. The database design
has been changed to make searching faster and more efficient, while also using less disk space. Additionally,
the new web interface will allow new options for message searching include 'not equal' words, i.e., exclude
messages that contain a set of words.
The database will be altered during the dbupgrade process to enable these features, and then as ListManager runs, the message-threading and full-text archives will be built. This means that any searches of the full-text archive may not find any data when ListManager is started for the first time. ListManager will be busily rebuilding the full-text archive in the background, and once it has completed it will remain up-to-date, since every message is archived when it is received.
More
1. Installing ListManager on Windows Index
3. Oracle and ListManager (Windows)
4. Installing Lyris ListManager As A Windows Service
2. Installing Lyris ListManager On Unix
1. Basic Unix Installing Instructions
2. Oracle and ListManager (Unix)
3. PostgreSQL and ListManager (Unix)
4. After Installing ListManager On Unix
5. How To Install ListManager By Hand
6. How To Upgrade ListManager By Hand
7. How To Install The Web Interface On A Separate Machine
8. If ListManager Will Not Run
9. Making Your Unix Mail Server And ListManager Coexist
|
|