Upgrade from base version 2.5 to 2.9 - Best practice?

The link to see the best pathway to upgrade isn’t working. Can anyone give some general direction? I have a customer that is on v2.5, base version, no service packs or CU’s installed. running 13 - iStar Edge controllers. The controllers are sitting on firmware Customer is running windows server 2012. I think I need to update the firmware first, upgrade to 2.8 on the current server, then move the services to a new server (customer has already built a new server to v2.9 specs). I need to know if I need to install all of the service packs or how can I best get this customer up to date?

Thank you for any assistance!!

Hey Mija,

to go to 2.8 you have first to go to 2.6. Then you could go from 2.8 to 2.9 and then install the latest SP. I believe it’s SP6. Have you ever performed an upgrade and move to another server? There is some things you have to notice when restoring the DBs.
You have to create a new 2.5 installation to the new server, restore DBs, repair Victor Application server (because probably the operator and the server name would not be the same as the old ones) and finally register for the new host ID. After that make a backup just in case.
Then you upgrade to 2.6 > new license > backup > upgrade to 2.8 > new license > backup > 2.9 > SP6 and SP6 CU1. After all these steps and after registering for the new version make a backup and you are free to run!

1 Like

Thank you. Can you clarify, did you mean go from v2.5 to 2.6? Do I need all the service packs for v2.5? Or can I go from the base v2.5, directly to base v2.6? I then move up to v2.6/SP6 and then move to v2.8, new license>backup>2.9>SP6, and then SP6/CU1

I have moved servers previously, and know that the machine name needs to remain the same or there are issues with the tables. Again, thank you for your time.

Since you upgrade to the latest version, all the base versions 2.5, 2.6 and 2.8 don’t need to have any SP updates. As long as the final version (in your case 2.9) have the latest updates.
Regarding the server name, it is good to keep the same name and IP, but if you cannot after the upgrade just run a repair to get the name and the IP of the server into the tables.
And as I mentioned before backup at every version upgrade just in case something needs to be reinstalled.

Perfect!! Thank you very much! I appreciate your time~

If you are on 2.5 you can jump to 2.7.

If you move the 2.5 database to another SQL instance, you do not have to install 2.5 again, you can freshly install 2.7 against a 2.5 database and it will upgrade it.

There is an issue with 2.5 and SQL Express that may have a different collation that will cause 2.7 to fail to install. You can open a support case to get the collations fixed or ensure that the new SQL instances match the collation of the 2.5 SQL instances.

To get the collations of the server and the databases run this in SSMS:

SELECT CONVERT (varchar(256), SERVERPROPERTY('collation'))

SELECT Name, Collation_name from sys.databases


Thank you very much for everyone’s input! I greatly appreciate it!

FYI, moving from 2.5 to 2.7 changed the host id. I pre-planned and requested the licenses ahead of time, however when I went to apply the license, the host ID had changed. Just wanted to report this as I think others should know. Thank you~

Hi Mija,

The HostID’s are common between the following versions:

V2.01 → V2.40
V2.50 → V2.60
V2.70 → V2.90

So when you plan to upgrade to V3.00 at a later stage, be aware it will also change at that moment.

Kind regards,


Thank you @Stefaan.Cornelis373 !! I hadn’t located this information prior!!

Kind regards~

One thing that wasn’t expressly mentioned, you can only upgrade two minor versions at a time, for example 2.50 to 2.70, 2.60 to 2.80, etc. Your path would then be 2.50 to 2.70 to 2.90.