Vote for Enhancement Request ER116815

I have put in an enhancement request for a proper server move routine for Opera 3 SE. Currently the advise is to install on new server set up all the users and companies and then restore the data from an Opera backup.

But I have a couple of SE sites that have a lot of users and one that has set permissions down to what can be seen on the action buttons they really wouldn't want to set up all their users from scratch.

Also any payroll sites will lose the ability to resend historical payslips and P60s as this is held in the Core database which we can't restore.

Please vote so they look at this properly.

ISCO Presentation.mp4

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

claire-craig

Goodness, that doesn't sound very productive or helpful. I'll certainly give this my vote.

Regards
Claire

michaelc

I am not sure why Pegasus are advising to backup of restore the company database to move SE it is possible to move all the databases including the core and system databases, we had to go to development but they provided the following rough steps a couple of years ago

We have ran this as a proof of concept test but the live move never happened, I would advise to test off site first, as it is easy to miss a part and you then have to remove SE and start again.

Hope this Helps

Michael

Instructions for moving the SE Server installation.

This covers the scenario where the SQL databases are on a separate SQL Server that will not be moving.

CRITICIAL: Please DO NOT have the SE Server services running at the same time pointing at the same SQL databases!

Install SE Server on NEW machine. DO NOT CONFIGURE.
Do relevant data file copies if needed.

If there is bespoke, copy the following folders from the Program Files on the old SE server to the new one: ModelLive and ModelNext.

If the data folders (e.g. containing Common, Repository, etc.) reside on a fileserver share, then there is no need for any data file copying.
If the data folders are being moved to the new SE server copy them over. They need to be copied to the new server and some of the following records will need to be changed in the Opera3SECore database
• Settings table*, “Opera.Folders” Group:
o FixedDynamic – location for non-company fields.
o FixedCommon – this is used for non-company files (e.g. BackupTemp). This is normally only set the first time SAM is used to edit the Common path to a share.
o Dynamic – location used when creating new companies. This is changed every time SAM is used to edit the Data path.
o Common – this is used when creating new companies. This is changed every time SAM is used to edit the Common path.
• DataRepositories table: Common field, and possibly Path field.

These are stored encrypted by default. To replace the Value with an unencrypted one, you must also update the Secured field to 0. To see the current values of these on the old server, the Server Information report in SAM shows them (in the same order as above) in the “Server information summary” table at the top of the report.
CRITICIAL: DO NOT have to SE Server services running at the same time pointing at the same SQL databases!

To point the new SE Server to the current databases, the following registry keys can be copied from the old SE Server:
[HKEY_LOCAL_MACHINESOFTWAREWOW6432NodePegasusO3 SE]
"Core SQL Server"="sqlservername"
"Core SQL Database"="Opera3SECore"
"Core SQL Credentials"="#"

To point existing clients to the new SE server, the following registry key can be changed on the client machines.
[HKEY_LOCAL_MACHINESOFTWAREWOW6432NodePegasusO3 SE]
"Client Target"="net.tcp://NEWSESERVERNAME:51999/Opera"

Change setup.peg (next to setup.exe) in the client installer folder so that new clients point to the new server.

Scheduled recurring tasks (e.g. Backups) will need to be set up again so they run on the new SE Server.

fzw

They sent me something very similar but it stated this was for moving the SE Server installation and not the data. When I asked about moving the data as well that's when it all got complicated.

And eventually they came up with the rather limp plan of setting everything up again and restoring just the data.

Which is just a bit rubbish really.

Felicity

fzw

Thank You

michaelc

Hi Felicity

The above works for migrating the data as well, backup the SQL databases (Core, System and Company Data) on the old server and then restore them onto the new server you will then need to amend the paths in the DataRepositories table in the core database changing the ServerName, Path and Common fields to point to the new server. You will also need to amend the seqco table in the system database changing the value in the co_servername to point to the new SQL server.

Once this has been done you should be able to start the Pegasus Opera service on the new server and log into SAM to complete the configuration of the new server.

Michael

fzw

This is pretty much what I suggested to them and this was the response I got:

'A senior colleague has looked at this and said we do not recommend server moves in the way you have described for SE:'

jason-warner

SE wasnt designed to be ever moved im my opinion, we've moved it a couple of times and have had to set the system (SAM) up from scratch both times as there are hardcoded paths that cannot be changed.

rm_benefit_administration_aca_training.pptx

Copyright © 2025 Infor. All rights reserved.