[KBA-00602] How to migrate an Omnicast™ server to another machine - Omnicast™ 4.0 - 4.8

series
Omnicast™ 4.0 - 4.8
revised_modified
2013-05-09

[KBA-00602] How to migrate an Omnicast™ server to another machine

This article details the steps necessary to move an Omnicast™ server to another machine.

Summary

When moving an Omnicast server to a new machine, it is important to follow the steps listed below to ensure no data is lost in the process.

More Information

1- Backing Up Databases and Registry Entries

a) Back up your databases (DirectorySQL, AlarmSQL, VideoArchiveSQL, etc) using either Microsoft SQL Management Studio or the Omnicast Backup Tool (link available below).

b) Export the Genetec registry key listed below (depending on your OS bit size):
  • 32-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\GENETEC
  • 64-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\GENETEC

This can be done using the Omnicast Backup Tool.

Note that if you plan on installing Security Center in a different path on the new machine (going from C:\Security Center on the old machine to D:\Security Center on the new machine, for example), it is recommended to only export the registry keys for the current version and services you need.

2- Moving the Physical Video Files to the New Server (optional)

Archived video files will need to be copied over to your new machine manually if you wish to host them there. It is important that they are copied to the same path on the destination machine.

For example, if they were originally in D:\Omnicast\VideoArchives on server 1, they need to go to D:\Omnicast\VideoArchives on server 2.

3- Restoring the Registry Entries to the New Machine

Depending on the bit version of the new machine, you will restore the registry keys following one of two possible methods:

SCENARIO A- Migrating to the same bit version:

a) If the Windows OS on the new machine is of the same “bit size” as the old machine (going from 32-bit to 32-bit, for example), restore your exported registry keys onto the new machine before installing Omnicast. To do this, use the Omnicast Backup Tool.

Alternatively, you can restore them by re-zipping them on the new machine and using the Omnicast Backup Tool. Ensure to use the "-reg" command in order to avoid restoring the databases (see the OmnicastBackup Release Notes.pdf, page 6).

b) Once that has been completed, we need to clear out the old license information on the new machine, since it is no longer valid. Run the Windows Registry Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\Genetec\Genetec Omnicast 4.x and delete two values on the right-hand side: “Challenge” and “LicenseKey”.

c) Once they have been deleted, close the Windows Registry Editor.

SCENARIO B- Migrating between bit versions:

a) If the Windows OS on the new machine is of a different “bit size” than the old machine (going from 32-bit to 64-bit, for example), you will need to modify the backed up registry keys prior to restoring them on the new machine, which is done prior to installing Omnicast.

To do this, extract the keys from the backup zip file, open each with a text editor and find all instances of the following path (depending on your OS bit size):
  • 32-bit path: HKEY_LOCAL_MACHINE\SOFTWARE\Genetec
  • 64-bit path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Genetec

If you find the 32-bit path, replace it with the 64-bit path.

If you find the 64-bit path, replace it with the 32-bit path.

b) Once that is done and the changes saved, copy your keys over to the new machine and then double-click each to restore them.

Alternatively, you can restore them by re-zipping them on the new machine and using the Omnicast Backup Tool. Ensure to use the "-reg" command in order to avoid restoring the databases (see the OmnicastBackup Release Notes.pdf, page 6).

c) Once that has been completed, we need to clear out the old license information on the new machine, since it is no longer valid. Run the Windows Registry Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Genetec\Genetec Omnicast 4.x and delete two values on the right-hand side: “Challenge” and “LicenseKey”.

d) Once they have been deleted, close the Windows Registry Editor.

4- Installing Omnicast on the New Machine

Run the Omnicast Server installation, following the instructions in the Installation and Upgrade Guide.

When asked if you want to use a new database or an existing database, choose a new database (unless you already have an existing SQL installed) for step 5 (below). At the end of the installation, activate the license and close the Server Admin to complete this step.

5- Restoring your Databases on the New Machine

a) Once you’ve installed Omnicast, stop your services and restore your database backups into the databases of the same name on the new machine. This can be done using Microsoft SQL Management Studio or the Omnicast Backup Tool. If using the Backup Tool, ensure to use the "-db" command in order to avoid restoring the registry keys a second time (see the OmnicastBackup Release Notes.pdf, page 6).

b) After restoring, you can restart your services.

The migration is now complete.