Product: All
Version & Build: All
We recommend using the following procedure for moving ModusMail or ModusGate to a new server *:
1) Backup the current configuration on the old server:
- From the Modus Administration console, click on File and select Backup configuration...
- Choose where to save the file and click Save
- This will save the config to a *.reg file
- Copy the *.reg file to the new server
2) Install ModusMail or ModusGate on the new server [Mail and Web Interface]
- Ensure that new server is functioning properly (both Mail/Gate and Web component)
- If, on the new server, you installed Modus under a directory that differs from that of the old server, you will have to edit the .reg file (your Modus configuration backup) so that the file paths correspond to the new directory
- In Notepad, open the .reg file and ensure that the various file paths correspond to the drive mapping on the new server
- Test Modus using a few fake mailboxes to make sure all is functional
- If using ModusGate, create a route to the main mail server and test the connection
- Make sure that all of your database connections are defined on the new server as they were on the old server in System - System Databases in the Modus Console.
3) Restore the current config on the new system
- In the Administration Console, go to the new server
- Click on File - Restore configuration...
- Click OK at the warning message
- Browse for and select your *.reg file (edited version, if applicable)
- A DOS window opens onscreen while the configuration is loading
- Close and reopen the Console to refresh the screen
- For ModusMail, test some mailboxes by telnetting to POP3 (port 110) on the localhost and entering the username & address
- For ModusGate, test a route by telnetting to the localhost and sending a message to a valid local address
4) Start moving the mailbox directory and spool contents from old server to new server
- Once you've verified that mail can be processed on the new server, stop all Modus services and move the mailbox directory and contents from the old server to the new
- Create a network share on the new server pointing to the new mailbox directory (usually under <modus root>\mailbox) and copy the contents from the mailbox folder to the new server
- It is best to use xcopy from DOS to do this
NOTE: if using ModusGate, the mailbox directory only stores the messages that have been quarantined (e.g., <modusgate root>\Mailboxes\@Quarantine\Inbox. If you must keep these messages (in case users need to release them), then the contents should be moved to the new machine. If they're not required, do not copy them.
- If you're moving WebMail or WebQuarantine to the new server, you will also need to move the contents of the Webmail Users directory
- Usually installed under ...\vircom\web\webmail\users or ...\vircom\quarantine\users
- Copy the Users folder to the equivalent location on the new server
- Copy the spool and its contents to the new server
- If you have custom sieve scripts or any whitelist/blacklist items, copy the old sievestore.mdb from the old server to the new (...\vircom\modusmail\sievedata to the same location on the new server)
- This step is only necessary if using the native Access database. If using SQL, the data is stored there and no transfer of files is required. You only need to ensure that the database connection is established in the System - System Databases configuration in the Modus Console.
* If you are planning to move the software AND upgrade to a newer version of Modus, begin by installing the original version (i.e. what is currently on the old server) on the NEW machine and follow the steps outlined above. Use your current license key. After the configuration has been restored and tested on the new server, upgrade to the new version of Modus.
| 
