Upgrade TC9 to TC2017 (and migrate to new box)
We're planning to upgrade our TC instance from 9 to 2017 soon. At the same time we are also wanting to move onto a newer OS.
We're running TC9 on 2008R2 and we're currently planning to install on 2012R2 (this time fully orchestrated so that we can move it to 2016 easily once we as an organisation have implemented 2016).
While I know it is totally possible to upgrade from TC9 to TC2017 without anything in between, we are wanting to sync/migrate the file system and database to the new server, and then install TC2017 at the migrated storage and database (using MSSQL as the DB provider)
Alternatively, should we upgrade the old box to TC2017, and then migrate to the new OS. This takes away our super easy back-out option of simply starting the old TC9 instance up should we foo bar it up.
Any thoughts/feedback on experiences would be awesome!
Please sign in to leave a comment.
Hi Andrew,
As you point out, we suggest not mixing the two steps, but the order isn't that big a deal, and each option has its advantages and disadvantages. Providing you have a proper backup of the data, upgrading in the first server shouldn't be a big difference either.
The other way around would allow you to test the server with a hardware you know to work properly for your scenario, so after testing that it works, migrating to the new server and having issues would almost immediately point at a difference in the environment. Both options are good and it's up to your scenario to evaluate what is more likely/dangerous)
Thanks Denis! This is helpful in confirming our thoughts.