On-Premise Staging Server Creation

Introduction

This document will outline not only the options for creating a Staging server within an On-Premise environment but how it needs to be done along with the responsibilities of both Claromentis & Client teams.

 

Server Resources / Requirements

Number of Users Number of CPU's Memory (RAM/GB) Network Speed
1-100 2 6 100Mbit
100-500 4 8 100Mbit
500+  We recommend setting up a load balanced environment for any system with more than 500 users     

The above are guidelines based on our Live server requirements. As a staging server will not have the same traffic as a Live server they can be created as a lesser specification if required.

Disk space - this will need to mirror your Live server as we will be using your Live data to create a like for like Staging server.

 

Option 1

Cloning your Live webserver.

- This entails you (the client) to clone your Claromentis web server and create a new VM from this snapshot. This will then become your staging server and will contain the Claromentis data, ready for the Claromentis team to configure. 

- We ask that the cloned server is not accessed and IIS is turned off to avoid any users trying to reach said server until it has been configured by our team

IMPORTANT - Both the webserver clone and database creation/backup need to be from the same day to avoid potential data mismatch. If these don't match we will be unable to continue with the installation.

Database

MySQL

- If MySQL is contained on the webserver, no further action will be required as Claromentis will be able to use the existing login details of the live MySQL instance

MSSQL

- If your database is held on the live web server this will also be part of this clone, meaning no further action is required regarding the database

- If your database is external to the web server and is hosted on MSSQL we will require you to create a clone of this database using a backup from the live database, providing Claromentis with the following:

1. Database name (for example claromentis_staging)

2. Database user & password. Create a 'claromentis_staging' user using 'SQL authentication' (we do not support Windows Authentication for the SQL user) and set the password to never expire.

3. Enter ‘dbo’ in the default schema field and select 'db_owner' under both the 'Schemas owned by this user' and 'database role membership' sections 

4. Ensure that the Database is created with UTF-8 collation.

IMPORTANT, without the above, we will not be able to connect the staging webserver to the database.

Connection details

Once the above has been completed the Claromentis team will need to be made aware of how to connect to this server with the same method as we currently connect to your Live server(s). This can either be through the use of Splashtop or your VPN.

The Claromentis team will then be scheduled to connect to the new clone and configure this server as a Staging server.

 

Option 2

Provisioning a blank web server for Claromentis to install on.

This option is more involved from both the Claromentis team and the client team. If a blank web server is going to be provisioned, Claromentis will need to perform a full installation on this server. Before we can do this, we will require the data to be transferred to this server.

IMPORTANT, this server must be left blank, please ensure no software is installed or configured.

Data Transfer

- Claromentis will ask for the entire of the C:/Claromentis (drive letter may vary and the Claromentis team will check this prior to asking for it to be transferred) directory to be transferred to the new server and the directory where this has been placed made known to the team

If there is a separate data directory outside of the Claromentis directory we will also ask this to be transferred across.

Database Transfer 

MySQL - If MySQL is being used, Claromentis will ask for a dump to be taken alongside the data transfer and placed on the newly created server. Claromentis will then be able to install MySQL on the new server.

MSSQL - If MSSQL is being used, Claromentis will ask for the same information as outlined in Option 1 (Database)Claromentis doesn't support the installation and configuration of MSSQL by our team.

Connection details

Once the above has been completed the Claromentis team will need to be made aware of how to connect to this server with the same method as we currently connect to your Live server(s). This can either be through the use of Splashtop or your VPN.

The Claromentis team will then be scheduled to connect to the new server and perform a full installation using the data provided.

 

Responsibility Outline

For more detailed information surrounding the responsibilities as a client for On-Premise installations please refer to the following article.

Created on 28 April 2022 by Mike Leggatt. Last modified on 29 April 2022

Was this helpful?  

Share