11-21-2018 12:33 AM
We are planning a customer upgrade from GMSC 2015 to GMSC 2018 sp3. As it's a production environment, in order to avoid disruption and have a failover option, we plan to setup the 2018 on a new server in parellel, but connected to the same GMSC database, as below.
|Current Configuration||DB||New Configuration|
|GMSC 2015 Server <-Read Write ->||GIS DB with GMSC schema||<-ReadWrite-> New Server with GMSC 2018 SP3|
|Week 1||in Production||Installation & Testing|
|Week 2||failover / production||Under live testing (production)|
|Week 4||decommission||Fully in production|
Is it advisable to do it this way ? Does the 2018 product update, update / change the DB in any way.. ? Can they co-exist and operate on the same Database, without causing trouble for each other.. ?
Solved! Go to Solution.
11-21-2018 08:54 AM
GMSC 2018 (and 2016) will modify/update the GMSC metadatabase as part of the installation/configuration process. I would not recommend having both GMSC 2015 and GMSC 2018 pointing to the same GMSC metadatabase.
11-26-2018 12:40 AM
So, in that case, what would be a migration best practice.. without down time.. Appreciate if we can get some expert advice on that.
11-26-2018 12:51 AM
You can make a copy of the original GMSC meta-database and point to it during GMSC 2018 installation. The 2018 installation will then update only this new database. As long as there's no change in any of the project settings, the customers shall be fine using both 2015 and 2018.
If anything gets changed (by SCAdmin) on the 2018 system, same change shall be reflected manually on 2015 installation.
Hope that makes sense.
11-26-2018 12:53 AM
Also, make sure that the publishing processes are sync'ed on both 2015 and 2018, so in case of a fail-over event, the users will see the same data. On assumption that the GMSC Warehouse location will be different for 2018 installation.
11-26-2018 01:02 AM
Yes that makes sense.
That'd also mean, the metadatabase doesn't actually have to be named GMSC (tho, the setup document suggestion is to create a schema named GMSC), it can be named anything for eg: GMSC2018schema.
And just point to the GMSC2018schema, in the configuration wizard only ? any other places ? registry ?
11-26-2018 03:58 AM