Microsoft SQL Server (Hot Backup)

Overview

This section describes how to update TSS/Console version when system is using SQL replication. This upgrades system without any interruption for turrets/TPO devices.

Initial situation:

•All turrets are connected to primary TSS

•Boot Settings (Turrets & TPOs) define proper primary and secondary server

•SQL replication is running properly

•Primary TSS is running properly

•Secondary TSS is running properly

•Primary/secondary FTP is in use

Migration procedure:

Here is an overview of upgrade procedure. In this example, migration to 10.1 version.

FTP

If you have a system that replicate/synchronize data of FTP folder from primary server to secondary server you have to deactivate it.

On primary server do a backup of FTP folder. Keep this backup in a protected folder.

Stop SQL Reporting Service

On primary server, go to Control panel > Administrative Tools > Services > Right click on service SQL Server Reporting Service (MSSQLSERVER) > Stop

This is necessary because this server produce HTTP response on port 80 (even when IIS is stopped). This prevents turrets devices to switch correctly on secondary server.

Modify HTTP binding port

On primary server, you have to change HTTP default port from 80 to 8000. This describes procedure on IIS7 (Windows Server 2008).

On IIS7

Open Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Right click on ‘Default Web Site’ > Edit Bindings…

Select http row and click on "Edit" button.

Change port from 80 to 8000. Click "OK" button.

Click "Close" button.

Modify FTP binding port

On primary server, you have to change TCP port from 21 to 2100.

Open Control Panel > Administrative Tools > Internet Information Services (IIS) 6.0 Manager. Right click on ‘Default FTP Site’ > Properties.

Change FTP port from 21 to 2100. Click OK button.

Restart IIS! Check FTP server is restarting properly.

Remove SQL Replication

This step explains how to remove subscribers and publisher.

Remove subscriber

On secondary server, open SQL server management studio. In Object Explorer, right click on Replication / Local Subscription / <Your_Subscription> and click on Delete button.

A deletion confirmation message appears: click on Yes button.

Remove publisher

On primary server, open SQL server management studio. In Object Explorer, right click on Replication / Local Publications / <Your_Publication> and click on Delete button.

A deletion confirmation message appears: click on "Yes" button.

Update primary TSS/Console

This step must be executed on primary server.

Proceed as follows:

Extract the archive TSS-Console-10.1.Y.Z.cab.

Start the application UIM.exe.

Select option Update of TSS/Console and press "Next" button.

Next step ask you to choose some options:

•Version: Version to upgrade. Server will be determined depending of selected version.

•Server: Server where database is stored. Server will be determined depending of selected version.

•Authentication: Type of authentication to connect to SQL Server (not used with mySQL).

oWindows Authentication

oSQL Server Authentication (Important: User administrator used to log on Windows must have sysadmin role into SQL Server - this is required to copy database)

oAzure managed identities

•Login: Login to connect to DBMS. Client ID when paired with Azure managed identitites.

•Password:  Password to connect to DBMS.

•Database: Database will be determined depending of selected version.

Press "Next" button.

Next step ask you to choose some options:

•Site: HTTP site that will be used. Choose your recently created Site.

•Application Pool: application pool will be used to install application on.

•Integrated Security: security mode used to connect to the SQL database. If Domain Authentication is selected, the TSS will use the Application Pool virtual account.

•SQL Login: login application will use to connect to SQL Server or mySQL. Client ID when paired with Azure managed identities. The login is not required with Domain Authentication.

•SQL Password: password application will use to connect to SQL Server or mySQL. The password is not required with Domain Authentication nor Azure managed identities.

•FTP Path: the local directory of the FTP site (used for devices upgrades and configuration). Note that its value is automatically retrieved and the field is not editable when upgrading from an 8.x or greater version, as a single common FTP site is required.

Press "Install" button.

Next step ask you to choose some options about Syslog configuration:

•Enable: Enable syslog log (Enable the automatic start on the Windows Service)

•Path: Path of syslog log

•Cleaning period: Delete syslog files that are older than this value (in day)

•File truncation: Maximum file size (in mo) of each syslog log

•Cleaning size: Maximum total file size (in mo) of all syslog log

•Port: Port of syslog log

Next step is status step.

At the end of the process the following screen is displayed:

The application is now installed in the displayed location and ready to be used. Note the displayed URL for future use.

For more information about IptradeNet application see corresponding section: IptradeNet/TSS/Console: Quick Start Guide.

Upload new firmware

On primary server, open Console application (Do not forget port is now 8000. Console Url should be something like this: http://localhost:8000/IptradeNet.Console.RC33).

Go to system > Firmware management > Click on button Add new.

On ‘Firmware Level Edition’ screen browse for new firmware (EK, Turret Lite, VIP Phone) and click Add and Go Back to finalize operation

Configure and restart test turrets

Choose some turret to test that migration run correctly: 2 or 3 should be enough. We will test that migration run properly.

Change turret firmware version

•Set turrets to upgrade to this firmware.

•Go to device edition, change value of Firmware Version.

•Click on "Update" button.

•Click on tab Boot Settings.

•Click on tab Basic Mode.

•Click on group TSS.

•Set new TSS url for Service base URI.

•Click on Update button.

Change FTP port

Reconfigure FTP port of these turrets. On each Web Administration page of turret, click on Begin configuration button than click on IP Trading Turret button and change URL of primary FTP server by pressing "Edit" button

<YOUR_FTP_SERVER> to <YOUR_FTP_SERVER>:2100

Reboot test turrets

Reboot test turrets by pressing Next button on Web Administration page and pressing Apply Configuration button.

This saves FTP change on turret and reboot device.

Set new firmware as default firmware

The test has run properly, new firmware can be chosen as final default firmware.

On primary server, open Console and go to System > Firmware management.

In Tool frame, choose new firmware version as Version and concerned Device Type by selecting checkboxes. Click on Apply button.

Change General TSS URL

Check FTP settings (Turrets & TPOs) of target version are using same primary and secondary TSS as previously.

·Version : rc10.1.xxxx

·File: ipt.ProfileEK.cfg (and eventually Lite and VIP)

Modify HTTP binding port to default value

On primary server, you have to change HTTP port from 8000 to default value 80.  For more details about how to proceed please refer to previous section ‘Modify HTTP binding port’.

Modify FTP binding port to default value

On primary server, you have to change HTTP port from 2100 to default value 21.  For more details about how to proceed please refer to previous section ‘Modify FTP binding port’.

Restart IIS.

Start SQL Reporting Service

On primary server, go to Control panel > Administrative Tools > Services > Right click on service ‘SQL Server Reporting Service (MSSQLSERVER)’ > Start

Deactivate Master zone management on previous version

This step concerns you only if you have different major version installed on server.

On all previous Console versions, add following TSS setting to deactivate master zone management (only one soft at a time is authorzed to manage it):

zone.management.disable = true

Restart all remaining devices

On secondary server, go to system > Sessions > Device session and reboot all remaining device (turrets and TPO).

Good practice: Reboot one turret device. Wait to check if it upgrades and switch correctly. Then reboot the rest of turrets devices.

RndTurret11 was testing turret – session is marked as dead.

RndTurret09 is remaining turret – reboot it.

Update secondary TSS/Console

This step must be executed on secondary server.

Proceed as follows:

Extract the archive TSS-Console-7.X.YYYY.cab.

Start the application UIM.exe.

Select option Update of TSS/Console and press Next button.

Next step ask you to choose some options:

•Version: Version to upgrade. Server will be determined depending of selected version.

•Server: Server where database is stored. Server will be determined depending of selected version.

•Authentication: Type of authentication to connect to SQL Server (not used with mySQL).

oWindows Authentication

oSQL Server Authentication (Important: User administrator used to log on Windows must have sysadmin role into SQL Server - this is required to copy database)

•Login: Login to connect to DBMS.

•Password:  Password to connect to DBMS.

•Database: Database will be determined depending of selected version..

Press Next button.

Next step ask you to choose some options:

•Site: HTTP site that will be used. Choose your recently created Site.

•Application Pool: application pool will be used to install application on.

•SQL Login: login application will use to connect to SQL Server or mySQL.

•SQL Password: password application will use to connect to SQL Server or mySQL.

Press Install button.

Next step is status step.

At the end of the process the following screen is displayed:

The application is now installed in the displayed location and ready to be used. Note the displayed URL for future use.

For more information about IptradeNet application see corresponding section: IptradeNet/TSS/Console: Quick Start Guide.

Do this step for each other instance of TSS/Console.

Create SQL Publisher

On primary server, open SQL Server management studio.

Right click on Replication/Local Publication > New Publication. Distributor willl be created if necessary.

Wizard appears and display introduction page. Click next button.

If you have not done replication installation, this box will appear to set distributor. Choose option 1 (default): primary server is distributor.

Set default folder:

Choose database that will be replicated.

Select ‘Merge publication’ as publication type.

If both servers are running with SQL Server 2012 select SQL Server 2008 or later.

Select all tables

Message information is displayed. Click ‘Next’ button.

No filter to add. Click ‘Next’ button.

Leave both checkbox selected. Click ‘Next’ button.

Click on ‘Security Setting..’ to select user. Best practice suggests creating a user especially for this task. Do not forget to take care about password expiration policy.

Process Account: Enter domain\username or computername\username

Password: Enter password of related user.

Leave 1st checkbox checked – 2nd checkbox is uncheck.

Enter name for publication and click on ‘Finish’ button

Publication creation result

The new created publication appears now in the Object Explorer under folder ‘Replication/Local Publications’.

Create SQL Subscriber

Stay connected on primary server with SQL Server Management Studio.

Right click on local subscriptions > ‘New subscriptions..’

Select publication that has been created in previous step.

Select 1st option

Select the server that will be used as subscriber. If it is not in the list (should not be), click on ‘Add SQL Server subscriber’  - this should be the case if you create the subscription from publisher server.

Enter server logical name (not IP) of subscriber server and click ‘Connect’

Select secondary database

Configure connection to publisher and subscriber by clicking on

Enter valid account – you can use same user as step 11 of publisher creation. Best practice suggests creating a user especially for this task. In case of servers are running under domain same user can be used, in the other way use user with same name on both servers. Do not forget to take care about password expiration policy.

Process Account: Enter domain\username or computername\username

Password: Enter password of related user.

Click ‘Next’ button.

Select ‘Run continuously’ in the dropdown list as synchronization schedule and click ‘Next’

Select ‘Immediately’ for subscription initialization.

Select ‘Server’ as subscription type

Select 1st checkbox

Click ‘Finish’ to validate wizard.

Press ‘Close’ button

Once it is done, you can use ‘Replication monitor’ (Right click on replication > Launch Replication Monitor) to get status of replication and check if configuration is done correctly. If status is displaying OK, replication is properly configured.

Copy FTP

Copy content of FTP folder of primary server to FTP folder of secondary server.

If you are using FTP replication you can reactive your replication system.

Update Component Manager URLs for Secure Access

As part of the TSS Server Install Operating System > Configuring IIS guide, you were instructed To Configure TLS on IIS

All TSS Servers should be secured with certificates.

By default the UIM installer will create Console and TSS links with HTTP and the IP address of the server.

To update these links to use HTTPS and FQDN follow this guide: Update Component Manager URLs