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 8.0.
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.
Testing Upgrade from 5.0-7.8 to 8.0
1. Open a command prompt on the old machine, and change to the ListManager directory.
2. Run lm configlist for a list of the machine names in ListManager's database. Note the name.
Testing Upgrade from 5.0-7.8 to 8.0
1. Open the file lmcfg.txt (located in C:\Program Files\ListManager or ~/ListManager/bin) using a plain-text editor (such as Notepad or vi).
2. Note the value of $node_name.
3. Install ListManager 8.0 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 enter your evaluation serial code:
lm serial xxxxxx
Where xxxxxx is your evaluation serial code.
10. At the command prompt, run the following command to upgrade the database to be used by ListManager 8.0:
lm dbupgrade
This process may take several hours, depending on how large your database is.
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.
More
1. Important Upgrade Information
3. Testing Production Data on a Test Server
3. Upgrading ListManager from 4.2 .1
4. Upgrading ListManager 5.0 or Higher
5. After Upgrading ListManager
1. Shut down ListManager on the old machine.
2. You need to know the name of this ListManager machine as it is configured in your database.
Moving from 5.0-7.8 to 8.0
1. Open a command prompt on the old machine, and change to the ListManager directory.
2. Run lm configlist for a list of the machine names in ListManager's database. Note the name.
Moving from 8.0 or Later
1. Open the file lmcfg.txt (located in C:\Program Files\ListManager or ~/ListManager/bin) using a plain-text editor (such as Notepad or vi).
2. Note the value of $node_name.
3. Start the installer ListManager on the new machine. On Unix cd to the lm/bin directory, and run from the command prompt:
./install_lm.pl
4. Select "New Install".
5. 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.
6. Shut down ListManager if you started it after the installation.
7. Open the file lmcfg.txt (located in ~/ListManager/bin) using a plain-text editor (such as pico or vi).
8. Change the value of $node_name to be the name of your old ListManager installation.
9. To upgrade your database, open a command prompt, and change to the ListManager directory. On the command line, type
lm dbupgrade
This process may take several hours, depending on how large your database is.
10. Start ListManager.
11. 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.
12. 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!
|
|