ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon 2020 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Documentation & Release Information
DrillDown Icon Known Issues (non-release related)
DrillDown Icon Configuration Information
DrillDown Icon modusGate & modusMail
DrillDown Icon How-To: Configure TLS for POP, IMAP, SMTP
DrillDown Icon How-To: Install modus Web Components on a Separate Server
DrillDown Icon Info: Configuring modus with a Proxy Server
DrillDown Icon Info: BATV Default Subject Tags
DrillDown Icon How-To: Force Spam Updates
DrillDown Icon How-to: Repair databases that are missing objects such as indexes or constraints
DrillDown Icon How-to: Log Modus Logs to a *nix Host
DrillDown Icon How-To: Bypass Attachment Filtering TO: Certain Users or FROM: Certain Users
DrillDown Icon Info: What is an .ASY File Extension
DrillDown Icon How-To: Reduce Image Spam by Using Dynamic IP Blocklists
DrillDown Icon How-To: Enable Persist Sorting Order
DrillDown Icon Info: Fingerprinting Explained
DrillDown Icon Info: RBL Check After AUTH LOGIN
DrillDown Icon How-To: Configure ODBC for a 64-bit environment
DrillDown Icon Info: Quarantine Clean-up Process in Modus
DrillDown Icon How-To: Completely Uninstall Your Modus Product
DrillDown Icon Info: SNMP OIDs Used by Modus
DrillDown Icon Info: Testing SMTP Connections
DrillDown Icon Info: Upgrading From a Previous Version to Modus 5.x
DrillDown Icon How-To: Allow Users to Disable Quarantine Reports
DrillDown Icon How-To: Archive Messages in Modus
DrillDown Icon How-To: Attach Original Messages to Forbidden Attachment Notices
DrillDown Icon How-To: Change the Banner Greeting
DrillDown Icon How-To: Change the SMTP Parameters for the Customer Support Feature
DrillDown Icon How-To: Configure the Quarantine Database in PostgreSQL
DrillDown Icon How-To: Configure the Mailbox Directory on a Share
DrillDown Icon How-To: Delete Viruses and Forbidden Attachments from Quarantine
DrillDown Icon How-To: Disable Outbound Filtering for Specific Users
DrillDown Icon How-To: Disable Scanning for Trusted Sources
DrillDown Icon How-To: Effectively Set-up the Spam and Virus Performance Tabs
DrillDown Icon How-To: Enable Attachment Release from the Quarantine Reports
DrillDown Icon How-To: Improve the Speed of an Extended Database for Authentication
DrillDown Icon How-To: Increase the Maximum Number of Headers / Hops
DrillDown Icon How-To: Manually Compact the Quarantine Database in Access
DrillDown Icon How-To: Move ModusMail or ModusGate from One Machine to Another
DrillDown Icon How-To: Properly Test the Modus Scan Engine
DrillDown Icon How-To: Run Both MS and Modus SMTP Services
DrillDown Icon How-To: Configure the Modus Remote Console
DrillDown Icon How-To: Specify an SMTPDS IP Address
DrillDown Icon How-To: Switch Mailboxes from Registry to the Extended DB
DrillDown Icon How-To: Turn Off Corrupt Attachment Scanning
DrillDown Icon Announcement: ORDB has Shut Down
DrillDown Icon How-To: Upgrade modusMail & modusGate
DrillDown Icon Info: SCAV2 requires specific port to be opened
DrillDown Icon Sonicwall blocking Avira updates
DrillDown Icon Info: Help Improve modusGate
DrillDown Icon modusGate Only
DrillDown Icon modusMail Only
DrillDown Icon SQL Server Information
DrillDown Icon MySQL Information
DrillDown Icon Security
DrillDown Icon Sieve
DrillDown Icon Spam and False-Positives
DrillDown Icon Statistics and Monitoring Section
DrillDown Icon Web Components
DrillDown Icon Troubleshooting
DrillDown Icon Hardware & OS System Requirements
DrillDown Icon Tools
DrillDown Icon Other Product Technical Information
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
 
How-To: Move ModusMail or ModusGate from One Machine to Another

 

Product: All

Version & Build: All

 

 
We recommend using the following procedure for moving ModusMail or ModusGate to a new server *
 
ModusGate:

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 saves the config to a *.reg file
  • The 32bit or 64bit file registry should look similar as it is listed below



  • Now copy the edited registry file to the new server

 

2) Install ModusGate and Restore on the new server

  • Ensure that new server is functioning properly with all windows updates applied
  • Download and install the exact same version of Modusgate that exists on the old server
  • You can download modus versions from our website http://my.vircom.com and use your license key to login to your profile
  • Once the download is complete launch the installer and follow the steps on the screen
  • If the installer does not detect any version of SQL on the local server, it will download it and install it automatically for you during the Modusgate install to complete the installation of Modusgate
  • During the SQL install it will request an “sa” account password to be used for SQL. Please apply the same “sa” password during the new installation of SQL that was used on the old installation of SQL 
  • Once done, if on the new server, you installed Modus under a directory that is different from that of the old server, you will have to edit the backup registry file 
  • EXAMPLE: If the old Modus server has the installation on the C: drive and the new server has the installation on the D: drive, then the following must be modified in the registry backup file as shown below
  • Edit the registry backup file with notepad
  • Then click the Edit menu in notepad and select Replace from the menu 
  • In the Replace text box type in the entries to modify the installation directory path and click Replace All
  • The registry file should now look similar to the image below




  • Save the changes to the back file and then import it into the new Modus server
  • From the Modus Administration console, click on File and select Restore configuration...
  • Now you’re new ModusGate server should be running  

 

3) Migrate SQL Database to the new server
 

  • If you plan on having new SQL databases used for your migration then this section can be skipped to step 4
  • To migrate your current SQL servers from on server to another, there is a great blog posted on our website located at http://www.vircom.com/blog/how-to-a-quick-and-easy-way-to-move-your-sql-databases/
  • Once the SQL migration is complete, log back into the Modus Administration console and verify if Modusgate are pointed to the correct databases which have been imported
  • This option can be found in the Modus Administration console under SYSTEM – SYSTEM DATABASE
  • Then restart all the Modusgate services by going under SYSTEM – SERVICES, select all services holding the “Shift” button. Then click STOP and START button to restart services as shown below

 
 
4) Migrate Access Database to the new server

  • If your environment does not have any Access databases, then you can skip to step 5
  • To move your sieve database or whitelist\blacklist entries to your new server you must first locate it on the old server
  • In the root installation of Modusgate on the old server, you will find a directory named SieveData. Open that folder to locate a file named SieveStore.mdb. The image below shows the location
  • Copy that SieveStore.mdb file from the old server the same root installation path of Modusgate on the new server in the SieveData directory
  • Replace any existing .mdb file in that directory and then restart all Modusgate services as shown in step 3


5) Migrate Quarantine folder

 

  • Although you moved over the quarantine database as indicated in step 3, the actual message files are still stored on the old Modus server. 
  • To located the quarantine emails login to the old Modus server and open the registry
  • Then in the hive HKLM\Software\Vircom\VOPMAIL locate the registry key named “VsQuarantineDestinationPath”
  • This is the path that stores all the quarantined email for your Modusgate which must be copied to your new Modusgate server
  • Go to that path and copy the entire folder to the new server to C:\respool
  • Once the copy is completed to the new server all the folder from the @quarantine folder will now be listed in C:\respool
  • Then extract all the .msg files from each of there individual folders and copy them into C:\respool folder
  • Now we have to respool the spam messages into the quarantine database on the new server
  • There is a knowledge base article on how to prep the messages before respool, use the link to locate the knowledge base article: RCP Creator Utility for Respooling Messages   
  • Now that the messages are prepped, you can respool them by following the instructions in the following knowledge base article: How-To: Respool Messages
  • Once all is done you can restart all Modusgate services as shown in step 3
  • The modusgate migration is now complete
  •     
 
6) "Optional" Web folders and .INI


  • Your webquarantine or webadmin pages may have some customization for logos, colors… etc.
  • To move the settings over you must copy some of the web folders from the old server to the new server
  • On the old Modusgate server, locate the directory which holds the web page configuration \Web\Quarantine\Webroot\Themes
  • In this directory you will find some folders which hold the custom images for your domain
  • You will have to copy the entire folder to the new server in the same location under Web\Quarantine\Webroot\Themes
  • Once the copy is done, open up the webmailsvr.ini file located under \Web\Quarantine\ and modify any IP address which were once pointing to the old server to the new servers IP address.
  • Once that is done restart the iis service and restart the webmail services in Modusgate located under SYSTEM – SERVICES


________________________________________________________________________________________________________________________________________________


ModusMail:

Day 1

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 saves the config to a *.reg file   
  • The 32bit or 64bit file registry should look similar as it is listed below

  • Now copy the edited registry file to the new server


2) Install ModusMail and Restore on the new server


  • Ensure that new server is functioning properly with all windows updates applied
  • Download and install the exact same version of Modusmail that exists on the old server
  • You can download modus versions from our website http://my.vircom.com and use your license key to login to your profile
  • Once the download is complete launch the installer and follow the steps on the screen
  • If the installer does not detect any version of SQL on the local server, it will download it and install it automatically for you during the Modusmail install to complete the installation of Modusmail
  • During the SQL install it will request an “sa” account password to be used for SQL. Please apply the same “sa” password during the new installation of SQL that was used on the old installation of SQL
  • Once done, if on the new server, you installed Modus under a directory that is different from that of the old server, you will have to edit the backup registry file
  • EXAMPLE: If the old Modus server has the installation on the C: drive and the new server has the installation on the D: drive, then the following must be modified in the registry backup file as shown below
  • Edit the registry backup file with notepad
  • Then click the Edit menu in notepad and select Replace from the menu
  • In the Replace text box type in the entries to modify the installation directory path and click Replace All
  • The registry file should now look similar to the image below

  • Save the changes to the back file and then import it into the new Modus server
  • From the Modus Administration console, click on File and select Restore configuration...
  • Now you’re new Modusmail server should be running


3) Robocopy the Mailbox Webmail & Quarantine data

 

  • This section of the copy of data is strongly recommended to be done after hours, reason being is that the data copy can take many hours and can cause traffic load
  • Both the old and the new server have to be shared and able to see each other on the network
  • On the old server make sure Robocopy is installed to be used to copy the data over
  • Once Robocopy is installed we can now run the command in the command prompt to copy the mailboxes, webmail and @quarantine folder
  • On the old server open the command prompt and locate the directory path of where robocopy was installed
  • Then from the path execute the commands listed below
  • These commands will copy all the mailbox folders, quarantine, and webmail folders to the remote server, the /w:1 and /:r1 means that if the mailbox is in use wait 1 second if a file is in use and then retry to copy 1 second later

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\ModusMail\MAILBOX" "\\NewServer\MAILBOX" /e /s /w:1 /r:1

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\ModusMail\MAILBOX\@Quarantine" "\\NewServer\@Quarantine" /e /s /w:1 /r:1

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\Web\Webmail\Users" "\\NewServer\Webmail\Users" /e /s /w:1 /r:1


Day 2

4) Migrate SQL Database to the new server


  • If you plan on having new SQL databases used for your migration then this section can be skipped to step 5
  • To migrate your current SQL servers from on server to another, there is a great blog posted on our website located at http://www.vircom.com/blog/how-to-a-quick-and-easy-way-to-move-your-sql-databases/
  • Once the SQL migration is complete, log back into the Modus Administration console and verify if Modusmail are pointed to the correct databases which have been imported
  • This option can be found in the Modus Administration console under SYSTEM – SYSTEM DATABASE
  • Then restart all the Modusmail services by going under SYSTEM – SERVICES, select all services holding the “Shift” button. Then click STOP and START button to restart services as shown below



5) Cut-over and re-Robocopy


  • Once the cut-over to the new server is done on the second day, there are still some files in the mailbox, webmail, and @quarantine folder that need to be copied over that was missed from the previous overnight copy
  • So once the cut-over is done you will need to redo the commands listed on step 3 to complete the entire copy

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\ModusMail\MAILBOX" "\\NewServer\MAILBOX" /e /s /w:1 /r:1

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\ModusMail\MAILBOX\@Quarantine" "\\NewServer\@Quarantine" /e /s /w:1 /r:1

C:\Windows\System32\Robocopy.exe "C:\Program Files\Vircom\Web\Webmail" "\\NewServer\Webmail" /e /s /w:1 /r:1



6)  Migrate Access Database to the new server


  • If your environment does not have any Access databases, then you can skip to step 7
  • To move your sieve database or whitelist\blacklist entries to your new server you must first locate it on the old server
  • In the root installation of Modusmail on the old server, you will find a directory named SieveData. Open that folder to locate a file named SieveStore.mdb. The image below shows the location
  • Copy that SieveStore.mdb file from the old server the same root installation path of Modusmail on the new server in the SieveData directory
  • Replace any existing .mdb file in that directory and then restart all Modusmail services as shown in step 4


7) "Optional" Web folders and .INI


  • Your webmail or webadmin pages may have some customization for logos, colors… etc.
  • To move the settings over you must copy some of the web folders from the old server to the new server
  • On the old Modusmail server, locate the directory which holds the web page configuration \Web\webmail\Webroot\Themes
  • In this directory you will find some folders which hold the custom images for your domain
  • You will have to copy the entire folder to the new server in the same location under Web\Webmail\Webroot\Themes
  • Once the copy is done, open up the webmailsvr.ini file located under \Web\WebMail\ and modify any IP address which were once pointing to the old server to the new servers IP address.
  • Once that is done restart the iis service and restart the webmail services in Modusmail located under SYSTEM – SERVICES

 






Modified 9/11/2017
Keywords: move servers backup migration migrate
Article ID: 1299