Moving Loupe Server Standard Edition

With Standard Edition, most Loupe and configuration is stored locally.  Since Standard Edition is not cluster-aware it assumes that it has exclusive access to its data while it runs.  There are three components of data that must be relocated:

  1. SQL Database: The Loupe SQL Database will need to be made accessible to the new server.  If it is stored locally on the Loupe Server it will need to be moved to the new Loupe Server or to a separate SQL Server.  The simplest way to do this (if moving between the same SQL Server versions) is to detatch and reattach the database using SQL Server Management Studio.  Alternately, a backup can be used.
  2. File Repository: Loupe stores all of the log files it keeps along with temporary upload files, full text search index, and server extension packages, in its file repository.  This location is specified in the configuration file for Loupe Server and is displayed in the Storage area of Loupe Server Administrator.
  3. Configuration:  There are two configuration components on the Loupe Server that should be copied to the new server:
    1. Configuration File:  Located in the %ALLUSERSPROFILE%\Gibraltar\Configuration folder (typically C:\ProgramData\Gibraltar\Configuration), this specifies the configuration information entered using Loupe Server Administrator including where the SQL database is, the file repository, and other dependencies that Loupe needs.
    2. Encryption Key: To handle sensitive encryption tasks, Loupe Server stores an Encryption key pair in the RSA Key store of the OS.  This can't be moved using file utilities, instead use Loupe Server Administrator to export the key to a file so it can be imported on the new server.

Migration Procedure

Step 1: Install Loupe Server on the new Server

Activate using your same Loupe Server license keys, remembering to use both the Loupe Server and Loupe Server User keys.

Step 2: Migrate the Encryption Keys

Migrate the Encryption key by starting Loupe Server Administrator on the original Loupe Server.  Skip the initial configuration wizard and then:

  1. Click on the Backstage Area (the top left tab).
  2. Selecting Encryption
  3. Export the key.  This will create a .grsa file with the public and private keys.  It's recommended you keep control of these keys and not post them publicly.  

On the new server start Loupe Server Administrator and then:

  1. Click on the Backstage Area (the top left tab).
  2. Selecting Encryption
  3. Import the key, providing it the *.grsa file created on the original server.
  4. Exit Loupe Server Administrator.

Step 3: Migrate the Configuration

With Loupe Server Administrator not running on either server, copy the configuration file from your original Loupe Server to the same location on the new server.  You can verify the file by starting Loupe Server Administrator.  If the SQL Database can be remotely accessed, Loupe Server Administrator should start without errors.

Step 4: Migrate the Data

With all Loupe processes stopped on both servers it's time to migrate the data.

  1. Copy the entire Loupe Repository folder to the same path on the destination server.  Loupe stores fully qualified path names in the SQL Database to refer to files, so the path needs to be the same.  
  2. If a local SQL Server is used, move the Loupe Database.  We recommend detaching it from the source SQL Server and reattaching it to the destination server.  If the server name or database name is changing this can be addressed by starting Loupe Server Administrator and changing the connection information when prompted.

Step 5: Verify Permissions

  1. If you are using Integrated Authentication to connect to the SQL Server then ensure the Loupe Service and the App Pool used by Loupe are running as a user with access to the SQL database (either local or remote).  
  2. Ensure the IIS User has access to the entire file repository.  When it was originally created, Loupe attempted to do this for you but these permissions do not always transfer appropriately when copying between computers.  

Step 6: Verify Migration

  1. Start Loupe Server Administrator which will automatically verify the SQL database and basic file store information.  
  2. Start the Loupe Server Service.  If it starts and stays running after 60 seconds then it is able to access the database and file store.
  3. Restart the Loupe Server web site in IIS.  Once it has restarted, you can use the Loupe Server Administrator to verify the web site by looking at the Web Site Status information on the top of the Start content.  This will issue a request to the Loupe server just like a Loupe Agent and verify that it gets back the correct response to be able to transfer data.

We're Here to Help

If you run into any issues, contact Support immediately.  We're happy to lend a hand during your migration.  You can also contact us ahead of time and we'll arrange to be available during your migration to ensure it goes smoothly.