How to move an MOBOTIX HUB VMS installation/version from old servers to new servers
This detailed guide will outline all the steps needed in order to move “as is” your original MOBOTIX HUB VMS system (incl. L1 up to L5) from older hardware to newer hardware. It is for users who have a lot of experience using, configuring, and managing MOBOTIX HUB VMS systems.
Disclaimer: The following instructions are for experienced/certified MOBOTIX HUB professionals only. Even following the below steps to the letter, no liability or support will be provided in case of any possible undesired effects. Most of the process requires local- or network administrative privileges, so log in- or run “as Administrator”.
- Start by installing the same version MOBOTIX HUB VMS on the new servers. The number of servers and their type should match the old installation.
Example: The old installation contains 1 Management Server and 2 Recording Servers, so the new installation should consist of 1 new Management Server and 2 new Recording Servers of the same MOBOTIX HUB version.
-
On the old Management Server, make a backup of the MOBOTIX HUB SQL databases (Surveillance and SurveillanceLogServer). Copy the backup to the new Management Server.
-
On the new Management Server, stop all services. Then detach both databases — the new ones that are almost empty. Go to the folder where the mdf and ldf files are located and rename these to something else (do not overwrite them).
-
Restore the two backups of the databases that you copied from the old server to the new one. (You will restore the backups of the original databases on the new server.)
-
If any of the new servers have different computer names or Domain/Workgroup names than the old ones, run the script (SearchandReplace.sql) to replace your server names in the SQL databases. You need to run this script as many times as the number of servers that you have.
Note: You can download the script from this location:
SearchandReplace.zip (918 Bytes)
In our example, there is 1 Management Server and 2 Recording Servers. The values to replace in the script are the following:
SET @stringToFind = ‘OLDMANAGEMENTSERVER’
SET @stringToReplace = ‘NEWMANAGEMENTSERVER’
SET @stringToFind = ‘OLDRECORDINGSERVER’
SET @stringToReplace = ‘NEWRECORDINGSERVER’
SET @stringToFind = ‘OLDRECORDINGSERVER1’
SET @stringToReplace = ‘NEWRECORDINGSERVER1’
(Every time you run the script you need to modify just the server name that you would like to replace.)
-
Stop the MOBOTIX HUB Recording Server service on the new Recording Servers.
-
On your new Recording Server machines, rename the following file to something else (do not overwrite it):
C:\ProgramData\MOBOTIX\MOBOTIX HUB Recording Server*RecorderConfig.xml* -
Copy from each of the old Recording Servers the following file to the new Recording Server that is going to “replace” it: RecorderConfig.xml.
-
On each of the new Recording Servers, edit the RecorderConfig.xml that you copied from the old Recording Server and change the following values to match with the new Recording Server name and IP addresses.
YourNewRecordingFQDN
- Repeat this on each Recording Server.
Note: In the values marked with red you should find the old FQDN/NetBIOS name that you will replace for the new ones.
- If you have more than 1 Recording Server instance, you should also change in the RecorderConfig.xml the following values for the correct ones (IP addresses IPv6 and IPv4), even if IPv6 is not implemented in your environment.
Example:
-
Stop all MOBOTIX HUB services on the old Recording Server and make sure that on the new servers all services are already stopped.
-
Copy the live database and the archive database from the old Recording Server(s) to the new one(s). Make sure to respect the file/folder security for the new Recording Server service account (default is “Network Service”), and copy/paste the entire folder structure to the same path — for example:
D:\MediaDatabase\ -
When the folder structure is copied completely, start the Management Server services and, when running, start the Recording Server services.
-
Wait a few minutes and then check in your Desk Client if you can playback the videos.
Update (21-Mar-2023): This article is only valid for MOBOTIX HUB versions where the Surveillance_IDP SQL database is not present — this includes MOBOTIX HUB VMS 2020 R3 and earlier.
From 2021 R1 and onwards, moving an MOBOTIX HUB VMS installation requires the backup and restore of Surveillance, Surveillance_IDP, SurveillanceLoServer SQL databases (and Surveillance_IM SQL database, if present).