Installing a server with existing server archive¶

When installing a octoplant server with an existing server archive, the octoplant server applications are installed and an existing server archive is integrated. With this type of installation, existing server archive data can continue to be used. No new server archive needs to be created and no data is lost.

The client applications that are required for the configuration and administration of the octoplant server must be set up separately. For details on setting up the client applications, see Installing client applications.

Requirements for the installation¶

• The octoplant setup file is accessible.
• You have a valid license file.
• The user performing the installation or the user account through which the installation is performed has administrative rights.
• Executing files must be permitted on the drive that is intended as the storage location for the server archive. Any existing security policies that prevent the execution of files must be deactivated.

• If the execution of files is not permitted, an error message (SQLException) is displayed later when logging into the system. A login is not possible.

• It is recommended not to install the octoplant hub on a computer on which a octoplant server is already installed. If this has already been done, the postgres service octoplant hub PostgreSQL 14 must be stopped manually when installing/updating the octoplant server.

Procedure¶

1. Execute the Setup.exe file on the computer intended for the installation as administrator.
2. The installation wizard will then open.
3. Select a language. English and German are currently available.
4. On the welcome page of the installation wizard, select Next.

5. Select the option Install octoplant applications and then select Next.

   

6. Select the option I agree. and then select Next. If you do not agree to the license agreements, the installation will not continue.

7. Select the option Install server applications and select Next.

   

8. Select the Server with existing server archive option and select Next.

   

9. In the next step, you will be asked to create a backup of your server archive or to confirm that you have already created a backup of the server archive. Data backup is required as a database migration is being performed, during which the server archive may be damaged and data may be lost.

10. Enter a path to the directory for the program files of the octoplant server applications. You can enter the path directly or select it using the Browse... button.

    

    We recommend keeping the path suggested in the installation wizard. Example:

    • C:\Program Files\vdogServer

    The field Path to the client applications: is grayed out. If no client applications are installed, no entries can be made in the field.

11. Select Next.

12. Specify where the existing server archive is stored:
    • Local: The server archive is stored in a local directory.
    • Remote: The server archive is stored in a remote directory.
13. Select Next.

14. Enter the path to the existing server archive and a directory for the client setup files. You can enter paths and directories directly or select them using the Browse... button.

    

    We recommend keeping the paths suggested in the installation wizard.
    Examples:

    • D:\vdServerArchive
    • D:\vdServerArchive\vdog client setup

    If the server archive is stored in a remote directory, the user or the user account from which the installation is carried out requires read and write access to the remote system. If no octoplant server archive exists at the specified address, an error message appears. The setup cannot be continued until all entries are correct.

15. Select Next.

    TCP port 64023 is required for octoplant. If you are updating from an versiondog version older than 9.5, will display a note stating that this port must be enabled. Confirm the note by entering the required text.

16. Windows XP Professional SP3, Windows Vista SP2 and Windows Server 2003 are no longer supported by octoplant. A note is displayed in the setup. This contains a link to a detailed list of the options available to you, if you are using older systems. Read the text carefully and confirm it if necessary, by entering "I understand" in the input field.

    

17. If you want to make the octoplant client setup files available on the network, activate the option Create the above network share. The Create the above network share option is deactivated by default.

    

18. Select Next.

19. Specify the user account from which the octoplant services are to be started. You have the choice between the Local system account and Username options.

    

    The account must have full access rights to the server archive directory. We recommend selecting the Username option and specifying an account with administrative rights. The system account may not have the necessary rights. The domain must always be specified for a domain account. Format:{Domain}\{Username} (example: DATAMAN\TomT)

20. Select Next.

21. The dialog for entering the password for the versiondog superuser opens.

    

    Info

    The password change-it must not be used. If the password change-it is set for the user versiondog at server start, a critical error is written to the Event log of octoplant. The next time you log in, you must then change the password.

22. Check the data displayed. If everything is correct, select Next.

23. The setup is executed. The completion of the installation process is indicated by a message. If the Windows Firewall service has not been started on the system on which you want to install octoplant, a note will be displayed. To continue the installation process, select Continue.
24. After successful installation, select Finish to close the wizard.

Related topics¶

• Installing client applications
• Options for supporting old operating systems