Upgrading ListManager 4.2.1 or Lower

 

Note that Lyris Technologies no longer tests upgrades from versions 5.x and earlier. Although upgrades from these versions directly to 8.0 may work, some users may need to upgrade to 7.0 before upgrading to 8.0.

 

Previous versions of ListManager may be found here:

 

http://www.lyris.com/products/listmanager/archives.html

 

Be sure you read Important Upgrade Information and Preparing to Upgrade first.

 

Preparing Your Data

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 8.0 can migrate your old Foxpro-format database to your SQL database automatically.

 

We recommend you perform a "dbupgrade" before upgrading. 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.

 

Upgrading without Moving ListManager

Be sure that ListManager is not running when you upgrade it.

 

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.

 

For details on how to upgrade ListManager on Unix, see How to Upgrade ListManager by Hand.

 

Moving and Upgrading from 4.2 or Earlier

Be sure that ListManager is not running when you upgrade it.

 

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. Start ListManager.

 

6. 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. Also assign the IP addresses ListManager should use for SMTP and NNTP on each site.

 

7. Go to Utilities: Administration: Server: Server Settings: Machine Settings: IP Addresses, and specify what IP addresses ListManager should bind to for DNS lookups.

 

You're done!

More

 

1.   Important Upgrade Information

2.   Preparing to Upgrade

3.   Testing ListManager

4.   Upgrading ListManager from 4.2 .1

5.   Upgrading ListManager 5.0 or Higher

6.   After Upgrading ListManager

 



Upgrading PostgreSQL Upgrading ListManager 5.0 or Higher