2
Move a domain from ver 15 to ver 17 (latest beta) on new server
Question asked by Heimir Eidskrem - 3/4/2020 at 2:41 PM
Answered
Im a bit confused reading a few kb articles.

Can I move a domain from the older server running version 15 to a new version 17 beta server?

Reading this:

It seems I can't without upgrading the old server? 

9 Replies

Reply to Thread
1
Matt Petty Replied
Employee Post Marked As Answer
Yes it is possible to do a per-domain conversion. Keep in mind, once you upgrade a domain it cannot be moved back.

1. [17 Server] Add a domain that's the same name as the one you plan on adding.
2. [17 Server] Shutdown the server.
3. [15 -> 17] Copy the domain folder with all the data ontop of the domain you just created on the new system.
(OLD server)C:\SmarterMail\Domains\<domain> -> (NEW server)C:\SmarterMail\Domains\<domain>
4. [17 Server] Boot up the server, log into a user in the new domain it should be working.
5. Make sure to fix your DNS and addressing to go to your new server.

Let me know if you have an issue with any of these steps. I would log into a user in your 17 box and verify it's working before getting rid of the domain on 15.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Heimir Eidskrem Replied
Perfect.

Thanks Matt.

H.

0
Heimir Eidskrem Replied
Matt,

I just did this (twice actually) and the users are not showing up on the new server.

Tried to login as one of the users but it says username or password not correct.

Can you please assist.

0
Matt Petty Replied
Employee Post
In the folder structure for your domain, there should be an accounts.json in it. Could you open up a support ticket with us, mention the issue, this thread, and include the file. I may be able to identify the problem looking at that file.

Curious, do any of your users have an "@" symbol in their username?
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Heimir Eidskrem Replied
Will open a ticket.
No @ in name.


0
Kyle Kerst Replied
Employee Post
I was able to test this further and I believe we need some slightly adjusted instructions on this. Including those for reference now:

1. Add a domain (in 17) with the same name as the one you're migrating to 17.
2. Stop the SmarterMail system service, IIS site, and application pool.
3. Navigate to the folder for this newly added domain, and remove all files/folders from within it.
4. Paste in the full backup of the original domain from the 15 environment into this now blank folder.
5. Start the SmarterMail system service, then the application pool, and finally the IIS site.


It looks like the presence of the settings.json and accounts.json files from the initial attempt at creating a blank placeholder domain caused SmarterMail not to attempt conversion.  When I test this process here it works as expected and the domain comes online smoothly.
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Heimir Eidskrem Replied
Kyle,

Thank you for the response.
I will test this shortly and report back.

H.

0
Heimir Eidskrem Replied
Just did a quick test and so far everything looks correct.

Thanks..

H.


4
Robert Emmett Replied
Employee Post
I'd like to chime in on this conversation. With the next beta release, we have added an Unload Domain and an Attach Domain options to the web interface. System administrators will now be able to unload a domain, modify any settings manually, if necessary, or even move the domain to a new location.  With the Attach Domain option, system administrators can now add a new domain or previously unloaded domain.  If the domain is from a previous version, it will converted showing a spinner while the conversion occurs.  All of this can be accomplished without the necessity to stop the mail service.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread