Maintenance and Service

Verified SEMS maintenance scope for backup, restore, support bundle collection and software update workflow boundaries.

Verified maintenance functions in the current UI

The inspected SEMS settings and API surface confirm public documentation for:

  • EMS configuration backup
  • backup restore
  • support-bundle download
  • board update upload/apply workflow
CyberSun SEMS settings page for maintenance tasks
Maintenance and service actions are anchored in the current Settings area, including backup scope and setup/board context.

Configuration backup scope

The current settings UI states that the EMS backup covers /config/ems.

The current backup description explicitly says it includes:

  • EMS database
  • users
  • device configuration
  • TLS material

The same UI also explicitly says it does not include:

  • system/network state
  • telemetry history
  • spools
  • logs

Restore behavior

The current restore warning says that restoring a backup replaces /config/ems and restarts EMS.

Support bundle

The current event/support tooling exposes a support-bundle download path. Publicly, this can be described as a sanitized diagnostic export used for troubleshooting and support review.

Software update boundary

The current product contains upload/apply routes and UI for board update handling. Public documentation may state that an update workflow exists, but project-specific production update approval and maintenance windows must still be followed.

Requires engineering verification

The current public sources do not yet justify publishing a universal safe-shutdown, board-replacement or factory-reset procedure for every SEMS deployment.

Was this helpful?

Did this article answer your question?