Server Operation and Maintenance

The goal with SystemWeaver is to offer 24/7 continuous operations. A key to this is the proper configuration and operation of installed servers. Note that although much of the operation and maintenance procedures can be automated, the operation organization must be alert for problems that may occur due to problems in the operating environment. Some of these problems are likely to be detected by users and the operating organization should therefore have continuous support available at all times when there are users active. An example is when a SystemWeaver server computer is shut down by mistake during operation. Other problems may not be possible to detect by users until it is too late. The operating organization should define procedures to avoid such problems. An example is when the storage used for database backups runs out of storage space, which may cause back-up copies to be lost.

How to Upgrade SystemWeaver to a Newer Version
Requesting an Upgrade Package Email support@systemite.se to request an upgrade package and include the following information in your request:  Current ve...
Sun, 10 Feb, 2019 at 1:20 PM
How to Upgrade to a SystemWeaver Split Server
Introduction This article describes the SystemWeaver Split Server and how to replace an existing swServer installation. If you are already running a split ...
Mon, 21 Jan, 2019 at 10:32 AM
How to Move SystemWeaver from One Server to Another
Instructions for how to set up a SystemWeaver server can be found here: https://support.systemweaver.se/support/solutions/articles/31000128080-systemweave...
Fri, 17 Nov, 2017 at 12:33 PM
Stopping and Starting a SystemWeaver Server
The following procedure should always be followed to stop the SystemWeaver Server Application and then start it again, e.g., after a database backup restora...
Mon, 26 Mar, 2018 at 1:18 PM