Skip to content
Thirdlane

Updates and Maintenance

Keeping your Thirdlane Platform current is what protects it over the long run: updates deliver security patches, bug fixes, and new features, while regular backups and monitoring keep a small problem from becoming an outage. This page brings those maintenance responsibilities - updating, backing up, licensing, and monitoring - together so you can build them into a routine.

System Updates

Use the Update Manager in Configuration Manager under Tools to check for and apply updates.

Update Process

  1. Check for updates - The Update Manager shows available updates with release notes
  2. Review changes - Read what’s included in the update before applying
  3. Backup first - Always create a backup before updating
  4. Apply update - The update process handles database migrations, file updates, and service restarts
  5. Verify - After update, check System Logs and run a System Audit

Cluster Updates

A cluster is updated a tier at a time rather than all at once:

  1. Update the manager first. It writes the configuration the other servers run from, so it should not be behind them.
  2. Update the User Access server and the telephony frontend.
  3. Update the telephony workers one at a time. While one is being updated the frontend routes calls to the others, so calls keep being handled throughout.

Calls in progress on a server being updated are still affected, so plan each tier for a quiet period. What a cluster avoids is having to take the whole platform offline at once.

Backup and Restore

The Backup and Restore tool creates comprehensive backups of:

  • Database (configuration, CDR)
  • Configuration files (PBX, Kamailio, provisioning)
  • Custom sound files and recordings
  • Certificates and keys

Schedule regular backups and test restores periodically.

License Management

The License page shows your current license status, features, and limits. Contact your provider for license changes.

Monitoring

For ongoing health monitoring:

Best practices

  • Never update without a fresh, verified backup or snapshot. It is the one step that lets you recover cleanly if an update goes wrong.
  • Read the release notes first so you know which features or settings the update touches before it lands on a production system.
  • Update during a maintenance window on All-in-One deployments (services restart); use the rolling cluster process for zero-downtime updates.
  • Verify after every update - check System Logs and run a System Audit before declaring the update done.
  • Test your restores, not just your backups. A backup you have never restored is an assumption, not a safety net; restore periodically into a test environment.
  • Keep only Thirdlane RPM repositories enabled so updates pull matching, tested package versions.