Migrating to Single Service Provider server

This procedure describes how to migrate an existing configuration and data from OVOC version 8.2.1382 installed on Service Provider Cluster to OVOC 8.4.3500 installed on a single Service Provider server. Before starting the process:

Extract current OVOC backup files to an external machine (see OVOC Server Backup Processes).
Stop OVOC from OvocServerManager (see Start or Restart the Application).

'EmsServerManager' has been renamed to 'OvocServerManager'. Both command strings can be typed in the SSH console.

Make sure both Postgres and Cassandra database processes are active (see Viewing Process Statuses).
If you have more than one disk in the new HP Proliant DL320 Gen12 server, then configure RAID 0 to create a single drive (see Configuring RAID-0 for OVOC on HP ProLiant DL360p Gen10 Servers).
Do the following:
1. Install the new Rocky Linux Operating System on the new Gen12 server (see Installing DVD1).
2. Download the DVD3-OVOC Server Application Installation OVOC 8.4.3500 GA .ISO file to your PC.
3. Using the WinSCP utility (see Transferring Files), transfer the .ISO file to the new Gen12 server acems user home directory: /home/acems .
4. Install the new OVOC 8.4.3500 GA version on the new Gen12 server (see DVD3: OVOC Server Application Installation).
5. Load the OVOC License (see OVOC License).
6. Verify that all processes are up and running (Viewing Process Statuses) and that you can login to the OVOC Web client.
7. Take snapshots from the three Virtual machine servers of the Service Provider Cluster.
8. In the OVOC Server manager Application Maintenance > Service Provider Cluster menu, do the following (refer to the OVOC 8.2.1000 IOM manual LTRT-94187):
Remove VQM server
Remove PM server
9. Download the DVD3-OVOC Server Application Installation OVOC version 8.2.3122 GA .ISO file to your PC.
10. Using the WinSCP utility (see Transferring Files), transfer the .ISO file to the existing OVOC version 8.2.1382 Management server acems user home directory: /home/acems

Don’t proceed with the upgrade until both the PM and VQM servers are removed.

11. Upgrade the OVOC version 8.2.1382 Management server to OVOC version 8.2.3122 (see Upgrading the OVOC Server using an ISO File).
12. Login into the OVOC server as 'acems' user with password 'acems' (or customer-defined password).
13. Switch to 'root' user and provide root password (default password is root):
su – root
14. Start the OVOC Server Manager utility by specifying the following command:
# OvocServerManager
15. Verify that all processes are up and running (Viewing Process Statuses) and verify login to the OVOC Web client is successful.
16. Using the WinSCP utility (see Transferring Files), transfer the OVOC version 8.4.3500 GA .ISO file to the upgraded OVOC version 8.2.3122 server acems user home directory: /home/acems.
17. Mount the iso file:       
mount /home/acems/DVD3_EMS_8.4.35xx.iso /mnt/
18. Create new backup files by running these commands: Note: this action will partially migrate the server to 8.4.35XX, It is forbidden to start and use OVOC application on this server after completing this step.
cd /mnt/EmsServerInstall/
perl upgrade_DBs_centos.pl
19. Copy all new backup files from /data/NBIF/emsBackup directory to the new Gen12 server /data/NBIF directory.
20. In the OVOC Server manager on the new Gen12 server, run the option 'Restore from CentOS' (Application Maintenance menu > Restore). At the end of the process, the OVOC server is rebooted.

The restore process may take a few minutes.

21. Verify that all processes are up and running (Viewing Process Statuses), configuration and data has been restored, and verify that you can login to the OVOC Web client.
22. Specify the following command:
cd /ACEMS/auto_config_scripts
23. Edit the DiskSizeFlag file as follows: change VERSION:V2 to VERSION:V3
24. Run the configDbParams.sh script:
[root@OVOC auto_config_scripts]# ./configDbParams.sh
========== Starting configuring Oracle parameters ==========
29 Dec 2025 09:39:38:813 Start entity manager initialization
29 Dec 2025 09:39:39:400 Entity manager initialization completed