Backup

This page describes how to create a backup of the SIWENOID v2 installation using the built-in Safety Backup function. Regular backups are essential for every SIWENOID v2 installation. A current backup allows the system to be fully restored after a hardware failure, software corruption, accidental misconfiguration, or a server migration.

The backup function creates a single .swnbackup file that contains the selected components of the SIWENOID v2 installation. This file can be used with the Restore procedure described on the Restore page.

Prev ← Restore Next → CerberusPro Configuration SIWENOID v2

A SIWENOID v2 backup created from the application contains:

• Server component — the server application configuration including all subsystem definitions, datapoint configurations, categories, treatments, tasks, forced actions, logical containers, maps, user accounts, object permissions, modules, and intervention texts.
• Client component — the client application configuration including workspace layouts and display preferences.
• Database — the event log and all historical event data recorded by the system.

The backup file size depends on the number of configured datapoints and the volume of event log data accumulated since the system was commissioned. On large installations with thousands of datapoints and months of operation, backup files can be several gigabytes in size.

Navigate to File → Options → Safety Backup.

Step 1 — Select components

Check the components to include in the backup:

• Server — always include this. It contains the complete system configuration.
• Client — include this to preserve workspace layouts and client preferences. In a single-machine installation, always back up both.

It is strongly recommended to select both Server and Client on every backup.

Step 2 — Select the backup destination

Click Browse to open a file save dialog. Navigate to the destination folder and enter a filename for the backup. Use a naming convention that includes the date and site name so backups can be easily identified later — for example: SiteName_SIWENOID_backup_2026-03-17.swnbackup.

Step 3 — Start the backup

Click Start backup to begin the backup process. Progress bars indicate the status. SIWENOID v2 remains fully operational during the backup — monitoring is not interrupted.

On large installations the backup process may take a significant amount of time. Do not shut down the server or close the application while the backup is in progress.

When the process is complete, a confirmation message is displayed. Verify that the backup file has been created at the specified location and that its file size is consistent with expectations before closing the backup screen.

SIWENOID v2 does not include an automatic scheduled backup feature — backups must be initiated manually by an engineer or administrator. Establish a regular backup schedule appropriate for the site:

• Before any planned maintenance — always create a backup before connecting a new subsystem, before making significant configuration changes, or before a software upgrade.
• After commissioning milestones — create a backup after completing each major phase of system configuration so a stable known-good state is preserved.
• Regular operational backups — on active installations, create a backup at least weekly to limit the amount of configuration and event log data that could be lost in a failure.

Storage location: Never store the backup file on the same physical machine as the SIWENOID v2 installation. A hardware failure that affects the server will also destroy any backups stored locally on that machine. Always copy the backup file to at least one of the following:

• A separate server or NAS on the local network.
• An external USB drive stored off-site.
• A secure cloud storage location accessible from the site network.

Maintain at least two generations of backup (the current backup and the previous one) so that if a newly created backup is itself corrupted, a fallback is available.

• The backup file format is .swnbackup. Only the SIWENOID v2 installer's Restore function can read this format — it cannot be opened or inspected with standard archiving tools.
• Backups created from within the application (this procedure) contain the Server and Client components. Backups created automatically by the installer during a version upgrade additionally contain the Application Settings, License Utility, and Database as separate restorable components. See the Restore page for details on restoring each backup type.
• The event log database grows continuously over time and is the largest part of the backup. On very large installations, consider archiving and purging old event log data periodically in consultation with SIWENOID support to keep backup sizes manageable.

—

Prev ← Restore Next → CerberusPro Configuration SIWENOID v2