Hi all,
We have been running version 1.3 since release and have been unsuccessful previously with version upgrades to 2.x (2.0.1 & 2.1). Whenever this was attempted there was database corruption and OME itself was unusable. Our only option was to restore an image of the server taken prior to the upgrade.
The staff member who used to manage OME left quite some time ago and I have attempted 1.3 to 2.1 upgrades several times in a test environment with the same results. I have, however, had some success with what I think is quite a dirty way of performing an "upgrade" and I am not sure what may have been missed or may fail. A quick rundown is below:
- Deploy new server & install OME (2.2 and now 2.3)
- point to a new MSSQL server during install to create a fresh DB
- stop services on existing OME and new version
- Backup existing OME DB and restore in to newly created DB
- restart new OME re-enter SQL details
This strangely works, but it just does not feel right. I am not sure what tables or data I may be missing as I presume that there have been changes between 1.3 and 2.x .. although it just seems to work. Does OME re-validate when you have to enter SQL credentials again and perform changes/updates as needed?
Is there a documented process for 1.3 to 2.x upgrades? I have tried to find something in the past, however I just come across the same old info which is run the exe, make sure the SQL account is db_owner and wait a few minutes.
failing that, is the method I have used successfully several times in testing a valid option? I really want to get us off of 1.3, but I also dont want to spend a whole weekend trying to recover our hardware monitoring platform either.
If you need more information i'll provide what I can.
Thanks in advance