Testing Production Data on a Test Server

You are here: Upgrading ListManager > Testing ListManager Upgrades > Testing Production Data on a Test Server

PLEASE READ ALL THESE INSTRUCTIONS CAREFULLY BEFORE PROCEEDING.

Failing to follow these instructions can cause you to inadvertently upgrade your production database, or to send out duplicate mailings. If you are uncertain about following these instructions, contact your account representative, who can arrange a demonstration of the new features in ListManager.

You should NOT send or receive test mailings using this method, since doing so will interfere with your production server.

1. Obtain an evaluation serial code from your Lyris account representative.

2. Make a copy of your production ListManager database to be used for evaluation purposes.

3. Create a blank database to be used during installation.

4 You need to know the name of this ListManager machine as it is configured in your database.

Upgrading

The upgrade process to ListManager 9.x varies depending on which version you are currently using:

To upgrade from v6.x or lower

1. Upgrade to v7.0

2. Upgrade from v7.0 to v.8.9c.

3. Upgrade from v8.9c to v9.x.

To upgrade from v.7x

1. Upgrade to v8.9c.

2. Upgrade from v8.9c to v9.x.

To upgrade from v8.x

Upgrade to v9.x.

Preparing for Testing

1. For Testing Upgrade from 5.0-7.8 to 9.x

Open a command prompt on the old machine, and change to the ListManager directory.\
Run lm configlist for a list of the machine names in ListManager's database. Note the name.

2. ForTesting Upgrade from 7.8 to 8.9

Open the file lmcfg.txt (located in C:\Program Files\ListManager or ~/ListManager/bin) using a plain-text editor (such as Notepad or vi).
Note the value of $node_name.

3. Install ListManager on a test server, using the blank database.

4. Select "New Install".

5. When the installer requests the database information, be sure to specify the blank database during installation, not your production database or your test database.

6. Shut down ListManager if you started it after the installation.

7. Open the file lmcfg.txt with a plain text editor, and edit it so ListManager now uses your test database instead of the blank database.

8. Change the value of $node_name to be the name of your old ListManager installation.

9. At the command prompt, run the following command to upgrade the database to be used by ListManager:

lm dbupgrade

This process may take several hours, depending on how large your database is.

10. At the command prompt, run the following command to enter your evaluation serial code:

lm serial xxxxxx

Where xxxxxx is your evaluation serial code.

11. IMPORTANT: Start ListManager so it does not send or receive mail. To do so, start it at the command prompt like so:

lm start noincoming nomail

12. Start the ListManager Web Server.

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

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

1. Important Upgrade Information

1. Testing ListManager

2. Testing on a Test Server

3. Testing Production Data on a Test Server

2. Preparing to Upgrade

3. Upgrading ListManager from 4.2 .1

4. Upgrading ListManager 5.0 or Higher

5. After Upgrading ListManager