LUCS upgrade with low downtime
Goal: To perform a quick LUCS update
Complexity: Medium
Preconditions:
- This scenario explains the upgrade procedure with 2 systems up and running. Make sure that one server is active (in this example Server 1
) and one server is passive (in this example Server 2
) as redundant system.
- LUCS Server and Credentials are known
- Admin / DB access rights on all machines are given
- Installers for new LUCS version are held ready, copied to both systems
Related Chapters: How to Upgrade, LUCS General Prerequisites This Use Case is a very minimal approach. For a full instruction set, refer to the related chapters, mainly How to Upgrade.
Related Use Cases: LUCS Preconditions, Basic LUCS installation
2 running LUCS Systems Upgrade
Step | WHERE | USER ACTION | RESULTS / SYSTEM REACTION |
---|---|---|---|
1 | Server with LUCS Database | Back up / Export your existing LUCS database and store it on a safe location. | Database backup is created |
2 | Server 2 Services | Stop all LUCS component services and uninstall them.
| Server 2 |
3 | Server 2 Check LUCS installation folders | Default: C:\Program Files (x86)\Luware AG Make sure that the folders (e.g. ICH, AM… don’t exist anymore), delete leftovers. | Server 2 |
4 | Server 2 (Passive) | Install the new components without starting them ( | Server 2 |
5 | Server 1 Services | Stop PS service (Persistence)
| Server 1 |
6 | Server 1 DB / File System | Using "Database Upgrader" Setup, upgrade the DB to the latest version | Server 1 |
7 | Server 1 and Server 2 | On Server 1 stop all services: Powershell
POWERSHELL
On Server 2 start all services, preferably at the same time for minimal downtime Powershell
POWERSHELL
| Services on Server 1 Services on Server 2 |
8 | Server 1 Services & File System |
→ Also see step 2-3 | Services on Server 1 |
9 | Server 1 (Active) |
| Services on Server 1 |
UCID | UC LUCS Application 028 |