Moving servers
To move the octoplant server, proceed as follows:
- End the MasterService.
- Uninstall the octoplant server.
- Copy the server archive into the new location.If you are working with a remote archive, the local server archive must also be transferred from the old to the new server, as it contains required metadata. In addition, the new local server archive created during installation should be renamed before migration to replace the new setup directories (client and agent setup) it contains in the old server archive.
- Reinstall the octoplant server with the existing server archive.If the directory structure of the new server is different from the old server, this can be adjusted in the
Server.ini
file (<vdServerArchive> > VD$A > Configuration
) in the [Common] section in the following keys:- 5508: Path to remote server archive
- 5509: Path to client setup
- 5521: Path to agent setup
- Check the server installation for the most important functions:
- Check-In /Check-Out
- Project structure
- Event log
- Jobs
Note
Moving the octoplant server will cause the system ID to change, and therefore
octoplant must be reactivated.
Once the installation has been successfully completed, please send us the new system ID in order to receive a new activation code. The new system ID can be found by going into the AdminClient: Menu item Licensing > Dialog Licensing > Tab Activation > Field System ID.
Related Topics
- AdminClient -> Licensing
- Server installation -> Removing the server
- Server installation -> Installing the server with an existing server archive
- Configuration via INI files -> File server.ini
Last update: September 15, 2023