Moving severs to a new 'instance'

General
1

Now accepting that I may not have fully read all the documentation, I do have a few questions about some of the Otto related parts of a server move

Simplified process:
1 Set up new server, access it by IP address
2 Take backups and copy files over to new server
3 Export schedules (with all turned off) and then import to new server
4 Get and install SSL
5 When all is ready close all files, change DNS to point to new IP, when moved open all relevant files

Somewhere between 4 and 5, I want and need to install Otto. Will that work if there is an SSL even though the domain name is pointing to another server? Can I get into the Otto control panel via ip.ip.ip.ip/Otto/ ?
I have quite a few Webhooks, is there a way to export them (as json or something) to import to the new server even with a wrong KEY so that they can just be updated and (open Receiver file first) tested before going to the relevant services and modifying the web hook that is called?
I presume I will need to set up the offsite backup details again? Will it use the copied OTTO_OFFSITE schedule that is now there? or are there any config files that can be copied to the new instance?

2

Hi John,

At this time, not much will work without SSL and fully qualified domain name.

We do not have a way to export webhooks, yet. It is on the list.

If you copy the db.sqlite and the rclone.conf file over to the new server, that should cover just about everything you need, including webhooks, and backup schedule configs.

You will still need to copy the backup schedules over as you mentioned.

Does that help?

Thanks

Todd

1 Like
3

Yes…

Thanks.
Just trying to work out how to make the process work with the shortest downtime and highest success rate!

4

@john_r I’d love to hear more about how you get on with this. My current approach is to use a wildcard cert on my ‘primary’ simpleq instance - this means I can spin up another instance with the same cert, and then change the DNS to move the web hooks over as required - although I haven’t tested this in anger yet.

5

@jamesG its not wildcard, although TBF it really could be, I’m passing on the cost to the customer.
The move is linked to the fact that the SSL is due for renewal quite soon, and this was a demo server, that ended up being a quick move out of an in-house server 17, but then the project has multiplied this year and they need something better, now there are no real complaints about performance since moving off the LAN (in many places by removing the most ridiculous unstored calcs off layouts !)

Its also timing as I want to ensure the webhooks are down for as short a time as possible

6

Hey y’all,

For anyone who comes across this later, there is some new official documentation covering the server migration process for OttoFMS. you can find it here.

Let me know if there is anything missing from the new guide that you think would be helpful to have!!

-Kyle

7

OttoFMS path, as a reminder?
Need to set permissions once file is moved to fmserver:fmsadmin?

1 Like
8

Also stop the service first??
If you don’t change the permissions you cant get back in to Otto!

9

@JamesG This seems to work.
I moved my receiver file over in advance of any others and set up a webhook for it.

Did the copying files from old server and both the offsite info and webhooks are all there, and seem to have picked up the API key created above.

10

Just done this again and really impressed that it works.
Note to self though, don’t change the admin console user or pass until everything is up and running, does seem to cause a few problems
And in this case the SSL was renewed for the new IP but only the old server even though I now go in by IP not FQDN otto still works to make sure that everything is copied