This guide covers the upgrade process for Silverback. Silverback versions can be installed over a newer one. It is not necessary, for example, to perform intermediate steps when updating e.g. from Silverback 20.0 Update 3 to Silverback 21.0 Update 2 . Each Silverback version can be considered as a standalone version, as it contains the full installer. This guide will show a common setup, but every environment is different! For advanced configuration or special requirements, talk to your technical contact or raise a support ticket to cover your needs.
Please follow our recommendation to do for every update first a backup of your current system.
For the upgrades ensure that you have on the Silverback server, the installation executable files for the latest version you wish to upgrade to. Ensure that you have a functioning Silverback deployment before commencing an upgrade. This ensures that any issues can be traced to the upgrade process and not an existing issue
Launch the Services.msc application on your Silverback server, and stop all Silverback related services
- Silverback EPiC Service
- Silverback Maintenance Service
- Silverback Listener Service
- Silverback Queuing Service
- World Wide Web Publishing Service (w3svc) or open Internet Information Services (IIS) Manager and Stop the Website
stop-service w3svc,silv*,epic*,mat* (Powershell + Administrative Privileges
Backup Silverback Database
To ensure you can roll back the upgrade in the event of an issue, we will back up the SQL database. Generally, this backup can be requested from the group that manages your SQL databases.
If you need to manually do this:
- Launch the SQL Server Management Studio,
- Right click on your Silverback database
- Select Tasks >
- Select Back Up…
- Ensure the backup type is Full, and specify the backup location
- Click OK
- Click OK after completion
Create Snapshot from Server (optional)
An optional method is to create a Snapshot from your Silverback Server which can be easily restored. This method is very useful if you have Silverback and SQL running on one server.
Backup Configuration Files (optional)
With Silverback 21.0 and newer, the web.config file backup is done automatically during the update process.
To ensure you can rollback the upgrade in the event of an issue, backup the website configuration files. The simplest way to do this is, is to navigate to the location of the Silverback Installation Files on your server’s drive (e.g. C:\Silverback) and create a copy of the web.config file located in the /admin folder. You should ideally preserve this backup until you can verify the upgrade process is complete.