Migrating a GNSS Spider Network Server

When to use this procedure

Use this procedure when an existing Leica GNSS Spider Network Server (NWS) is being replaced by another machine, when an NWS database is restored onto another host, or when operational recovery requires the active system to take over the role of a retired server.

Background: In SBC, real-time products are synchronized from the GNSS Spider Network Server. These products can be assigned to articles. A successful NWS migration must, therefore, preserve not only the product data seen in SBC but also the downstream usability of those article assignments with subscriptions.

Prerequisites

Administrative access to the retired/source NWS machine and the replacement/target NWS machine.
Access to the NWS database backup and restore process.
Administrative access to the SBC Central Server machine to restart services and validate results.
Planned maintenance window, because services on the involved machines must be stopped and restarted.

Procedure

Step 1: Prepare the retired/source Network Server

The objective of this step is to capture the source NWS state safely before the replacement server takes over.

Step	Actions	Resources
1.1	Confirm which machine is the retired or source NWS and verify that it is the correct system to migrate from.	Hostname, environment notes, maintenance plan
1.2	Stop the Network Server service on the retired/source machine to prevent further changes during backup.	Spider Server Control or Windows Services or equivalent service management access
1.3	Create a backup of the NWS database.	Database Management Tool or SQL backup procedure

Step 2: Restore the NWS on the replacement/active machine

The objective of this step is to establish the replacement machine as the active NWS using the backed-up source database.

Step	Actions	Resources
2.1	Stop the Network Server service on the replacement/active machine.	Spider Server Control or Windows Services on target machine
2.2	Restore the backup from the retired/source NWS onto the replacement machine.	Database Management Tool or SQL restore procedure
2.3	Start the Network Server service on the replacement machine.	Spider Server Control or Windows Services on target machine
2.4	Open GNSS Spider GUI for NWS Navigate to Tools > Configuration > General Review the SBC Central Server connection information	GNSS Spider GUI

Network Server UUID caution: The NWS unique identifier is stored in the NWS database. Restoring the database backup will therefore reproduce the same identifier on another machine. This works for replacement or hot/cold swap scenarios, but it will create ambiguity and conflicts if the original retired/source system later comes back online or if two active systems operate with the same identifier.

Step 3: Reconnect and refresh SBC

The objective of this step is to ensure SBC fully recognizes and operates with the replacement NWS.

Step	Actions	Resources
3.1	Restart the SBC Central Server.	Spider Server Control or Windows Services

Step 4: Validate the migration result

The objective of this step is to verify that the operational result matches the intended business outcome.

Therefore, log in to SBC as System Admin.

Validation Item	Expected Result
Products visible at Service Data > Real-Time Products	Products from the replacement NWS are shown correctly with correct Network Server Name and Network Server Host.
Article assignments at Service Data > Articles	Existing article assignments remain preserved and usable. Network Server Host is correct.
System connectivity	SBC Central Server communicates successfully with the replacement NWS. Live Status > Map View shows correct status of sites.
Real-Time Service end users can connect	A user with a previously existing subscription is able to connect and successfully authenticate to a real-time product. Use a real rover device or TestRTK application. shipped together with Leica GNSS Spider.