Migrating EdgeVis Server to a different machine
If you are replacing an existing EdgeVis Server with new server hardware, you can use the Multi-Site Resilience (Server Clustering) feature to migrate your system without needing to reconfigure your deployed encoders or viewing clients.
This approach can be used when the existing and new server PCs are connected to the same local network during the migration, or if they are on separate networks that are connected to each other using a VPN.
Before you begin
Make sure that:
The new PC has been installed and is connected to the same local network as the existing EdgeVis Server PC (or on two separate networks that are connected to each other using a VPN).
EdgeVis Server has been installed on the new PC.
The existing EdgeVis Server remains operational while the migration is carried out.
Both servers can communicate with each other over the network/VPN.
Both servers use the same operating system flavour. The operating system versions do not need to be the same; for example, RHEL 8 and RHEL 9 can be used together.
The new server has the required firewall and networking configuration to allow encoders and viewing clients to connect to it.
If the existing EdgeVis Server uses a proxy server, configure the proxy settings on the new server as required.
Important: Any network infrastructure or security configuration that applies to the existing EdgeVis Server may also need to be replicated or updated for the new EdgeVis Server. This can include firewall rules, port forwarding, proxy configuration, DNS records, or other network access controls.
Step 1: Add the new EdgeVis Server to the cluster
Follow the steps in the Scaling up EdgeVis Server using clustering articles to add the new EdgeVis Server to the cluster.
Once the servers have been clustered, both servers will be part of the same server cluster and can advertise their IP addresses/hostnames to connected encoders and viewing clients.
Leave both servers running and connected to the network while the database sync (status displayed on the EdgeVis Server web management portal → MSR settings page) is in progress.
Step 2: Allow connected encoders & viewing clients to update
Once the new EdgeVis Server has been added to the cluster and the database sync has completed, allow your deployed encoders and viewing clients to remain online.
You do not need to manually change the server IP address configured on each encoder/viewing client, as the IP address entered during the initial encoder or viewing client setup is only used for initial server discovery (see below section Do I need to reconfigure my encoders/viewing clients? for further details).
Provided the encoders and clients have been online while the new server is part of the cluster, they will automatically learn about the new server.
Do not decommission the existing server immediately after adding the new server. Allow the deployed encoders and clients sufficient time to connect while both servers are available.
Existing encoders and viewing clients must be online and connected while the new server is part of the cluster so that they can receive the updated cluster configuration.
Before decommissioning the old server, ensure that the encoders and viewing clients that need to remain connected are online and have successfully connected to the server cluster.
If an encoder is offline during the migration, it may not have received the updated cluster configuration. Such encoders should be brought online while the old server is still available.
Step 3: Decommission the old EdgeVis Server
When you are ready to complete the migration:
Shut down the old EdgeVis Server PC.
Confirm that the new EdgeVis Server is operating correctly.
Open the MSR settings page on the web management interface of the new EdgeVis Server.
Delete the old EdgeVis Server from the cluster.
The new server can then operate as the remaining server in the cluster.
What if the new server uses a different IP address?
Server Clustering allows existing encoders and viewing clients to transition to the new server without requiring them to be manually reconfigured.
However, there is an important distinction between existing deployed encoders and new encoders being deployed after the migration.
Existing encoders and viewing clients
Existing devices can use the Server Clustering (MSR) migration process described above. They will learn the new server address from the cluster when they are online while both servers are available.
New encoders and viewing clients
If the new server is configured with a different IP address from the old server, use the new server's IP address when configuring any new encoders or viewing clients after the migration.
For example:
Old server:
192.168.1.100New server:
192.168.1.200
Existing devices can transition to the new server through clustering, but newly deployed devices should be configured to use 192.168.1.200.
What if the new server takes over the old server's IP address?
If the new server will take over the same IP address previously used by the old server, newly deployed encoders and viewing clients can continue to be configured using that existing server address.
You should still complete the Server Clustering migration process before decommissioning the old server to allow existing devices to learn about the new server.
Firewall and network configuration
The new server must have the necessary firewall and network configuration in place before it can replace the existing server.
Depending on your network configuration, this may include:
Windows or Linux firewall rules on the new server
Network firewall rules
Port forwarding rules
NAT configuration
Network access control rules
DNS configuration, where applicable.
Any rules that currently allow encoders and viewing clients to communicate with the existing server may need to be updated to allow connections to the new server.
Refer to this article for the required ports and networking configuration.
Proxy configuration
If the existing EdgeVis Server is configured to use a proxy server for outbound connections, the proxy configuration should also be applied to the new server.
This may be required for connections such as:
The Central Licensing Service (CLS)
SSO providers
Webhook endpoints
Any other external services accessed by EdgeVis Server.
Main article: How do I use a proxy server to allow EdgeVis Server to connect to CLS or third-party services?
Refer to this article for instructions on configuring EdgeVis Server to use a proxy server.
Do I need to reconfigure my encoders/viewing clients?
No - when the migration is performed using Server Clustering (MSR), deployed encoders/viewing clients do not need to be manually reconfigured with the new server's IP address. This is because the server IP address entered when an encoder/viewing client was originally set up is only used for initial discovery. After connecting to the server, the encoder/viewing client stores and uses all IP addresses advertised by the server cluster. As long as the encoder/viewing client has been online and connected while the new server was added to the cluster, it can automatically transition to the new server.