We have an older instance of Octopus Deploy (3.15.7) which needs to move from one server instance to a new server instance; due to the hosts being decommissioned.
I have seen the migration document and everything looks straight forward:
My concerns come from the number of tentacles; Which numbers close to 2000 polling tentacles and making a change that causes irreversible impact on such a large number of machines.
Octopus deploy instance
SQL Server instance
2000 Polling tentacles.
1.) For a dry-run I will install the new Octopus server and point it to the newly restore database and then start the service running, I will login and set this server into maintenance mode. However there will be a small window when it’s running as a live server. Are there any tasks, back dated schedule events (The database was baked up for dry-run purposes about a week ago) that could start running between switching the service on and disabling maintenance mode?
2.) Is there anything with the newly installed dry-run server that can impact the existing tentacles? These tentacles are all installed as polling and pointing to the existing server via a CNAME.
3.) As part of the go-live migration I will switch off the existing octopus server, backup the databases, restore the databases, move the artifacts/task logs etc, repoint the cnames. There will be a period of time when the tentacles will be polling a server that doesn’t exist. The current settings suggest the tentacles won’t be removed; Is there anything I need to check to make sure this is the case?
4.) When I install a new server will the thumb print change? Or will this be the same as it comes from the database or master key? Are there any scenarios I need to be aware of if the thumbprint changes?
Thanks in advance