On occasion, a system administrator may need to move SmarterMail, and all its domains and data, to a different server. For example, if they are moving their SmarterMail customers to more powerful hardware.
SmarterTools makes it easy by allowing you to have 2 instances of your SmarterMail license running on 2 different servers for up to 30 days. At the end of the 30 days, the "old" license then needs to be uninstalled and should no longer call back to the SmarterTools' licensing servers.
Before starting the move process, add new (lower priority) MX records to your domains in DNS for the new server and allow 24-48 hours for the records to propagate through the internet. This will establish the new server address as an MX, but will prevent mail being delivered to it until you've completed the move.
SmarterTools also recommends ensuring your license key can be activated again before beginning the migration process. This information can be found by visiting the SmarterTools website and clicking on the account icon in the upper right. Once logged in, select Licenses from the dropdown. Select the license being migrated from the list and, if it has used up its allotted activations, a Reset Activations button can be seen. If you are unable to reset the activations yourself, contact sales@smartertools.com and we can reset the activation limit for you.
IMPORTANT NOTES:
- If you have SSL or TLS configured on any ports, the certificate being used must be exported (containing the private key) from the original servers certificate store. It then needs to be imported into the new server’s Personal folder within the certificate store.
- If Declude is being used on the original server, you will want to ensure the Declude service also gets setup on the new server prior to the deployment. Failure to install the Declude service on the new server will result in all mail landing in the SmarterMail Spool's Proc folder and will not be delivered.
- Previously established POP and IMAP Retrieval connections may need to be re-established post-migration to ensure proper authentication.
- When multiple Volume Mounts are being used, these need to be set up on the new server prior to any moving of data. Ideally, these should match what's set up on the "old" server in order to avoid any possible data loss. This includes placing mount/unmount scripts in the Assets folder on the new server (Windows Default: c:\Program Files (x86)\SmarterTools\SmarterMail\Service\Assets | Linux Default: /opt/smartermail/assets)
Follow these steps to migrate a SmarterMail installation to a different server:
- Install the same SmarterMail Build being used on the old hardware on the new server. (NOTE: Legacy Builds of SmarterMail can be found within your account on the SmarterTools website.)
- Set up SmarterMail in IIS on the new server, using the KB article "Set up SmarterMail as an IIS Site in IIS10" as a guide.
- Depending on the amount of data to be migrated, you are able to start an initial migration from the old server to the new one while SmarterMail is running. You can use something like Hobocopy (Windows, as it offers VSS to avoid file locking) or rsync (Linux) for this.
- Copy the Settings folder from your old server to your new one. (Windows Default: C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Settings\ | Linux Default: /etc/smartermail/). See Important Note regarding the use of Volume Mounts.
- Copy the Domains folder from your old server to your new one. (Windows Default: C:\SmarterMail\Domains | Linux Default: /var/lib/smartermail/Domains). See Important Note regarding the use of Volume Mounts.
- If you have Certificates, copy the Certificates folder from your old server to your new one. (Windows Default: C:\SmarterMail\Certificates | Linux Default: /var/lib/smartermail/Certificates). See Important Note regarding the use of Volume Mounts.
- If you have custom login images, move the Images folder from your old server to your new one. (Windows Default: C:\Program Files (x86)\SmarterTools\SmarterMail\Service\App_Data\Images | Linux Default: /etc/smartermail/App_Data/Images). See Important Note regarding the use of Volume Mounts.
- Once the initial migration is complete, you can do an incremental migration of any new data. For this, you'll want to stop the SmarterMail service on the old server, then do the following:
- Copy the Settings folder: (Windows: C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Settings\ | Linux: /etc/smartermail/)
- Run Robocopy for Domains, Certificates, and all mounted volume locations to sync only changed data.
- Copy the Spool directory to preserve queued messages.
- Copy custom Images if applicable (from App_Data\Images folder).
- If you change the path to your domains, you would need to edit your domains.json file accordingly to reflect the new paths.
- If your IP address or other DNS info changes, update the corresponding settings in SmarterMail.
- Start the SmarterMail Service on the new server, and any IIS sites/application pools as needed.
- Log in and make sure SmarterMail is properly activated on the new server.