VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Protecting PBX backups

Treat recovery files as sensitive assets containing more than route names.

Reviewed 2026-10-16Foundational

Backups can contain the keys to the system

Configuration backups can include endpoint and carrier secrets, user information and network settings. Depending on scope, voicemail or recordings may also be present. A backup repository therefore needs access protection comparable to the production data it can restore.

A backup becomes useful through a restore test
Configuration, secrets and required media enter a protected off-host backup. Restore to an isolated environment, validate behavior and record recovery time before relying on the backup.

Keep production trunk identities from registering during a restore exercise. Include the dependencies needed to decrypt and use the backup.

Separate storage and authority

Keep a recovery copy away from the PBX host and limit who can read or delete it. Protect encryption keys and storage credentials, while ensuring authorized recovery operators can obtain them during an outage.

Inspect job scope

Compare installed modules and custom files with the backup selection. Verify completion logs and that the artifact reached its destination. A scheduled job definition is not evidence that usable backups exist.

Restore without creating a second production PBX

Use an isolated target so copied trunk credentials cannot register or place calls unexpectedly. Validate routes, selected content and manual recovery steps. Record missing items and restore duration. Use the FreePBX recovery guide for its module-aware process.

Authenticate the recovery input

FreePBX's 2026 restore advisories explicitly treat backup archives as a security boundary. Record a hash when the artifact is created, preserve provenance and custody, restrict restore privileges and network access, update the restore module before import, and verify administrator authentication after recovery. Encryption protects confidentiality but does not by itself prove origin or integrity.

Scope FreePBX destination identities to one recovery purpose

FreePBX Filestore can hold passwords, tokens, SSH keys and cloud credentials for several destination types. The destination guide keeps secret custody, path scope, rotation, retention and independent retrieval explicit.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Hub

VoIP security

Reduce PBX exposure, constrain calling permissions and prepare for accountable recovery.

Explore topic →
Guide · Asterisk 22 LTS

Secure an Asterisk PBX before adding paid calling

Review management access, endpoint identities and dialplan permissions as separate layers.

Read guide →
Guide · FreePBX Backup & Restore release/17.0 source, FreePBX advisories GHSA-5v7h-49gr-jcwr and GHSA-f6hc-rqxg-ch86, and Sangoma Filestore, backup, fwconsole and FreePBX 17 migration documentation reviewed October 12, 2026; the advisories identify affected Backup & Restore versions below 17.0.6 and 17.0.30 respectively, but repository or advisory state does not prove the installed module, archive custody, target handlers or restored runtime, and no PBX, archive, storage destination, credential, job, restore, module, endpoint, trunk or call was inspected or tested

FreePBX backup and restore: prove the recovery path

Choose backup scope, protect off-host storage and validate an isolated restore before relying on it.

Read guide →
Guide · Sangoma FreePBX 15+ Filestore and Backup & Restore documentation plus the FreePBX release/17.0 Filestore and Backup & Restore repositories reviewed October 16, 2026. The Filestore release branch exposed module version 17.0.3.2 when reviewed; that repository state does not prove the version installed on a selected PBX. Documented destinations include email, FTP or SFTP, local paths, Dropbox, SSH and S3, while credentials, reachability, permissions, retention, encryption, object state, region, quota and provider behavior remain destination specific. No PBX, credential, destination, backup job, archive, restore or call was inspected or tested

FreePBX Filestore destinations: qualify backup transport and custody

Choose and accept a FreePBX Filestore destination by separating saved configuration, connection tests, archive creation, remote transfer, retention, custody and restore evidence.

Read guide →
Troubleshooting · Sangoma FreePBX 15+ Filestore and Backup & Restore documentation plus the FreePBX release/17.0 Filestore and Backup & Restore repositories reviewed October 16, 2026. The Filestore release branch exposed module version 17.0.3.2 when reviewed; that repository state does not prove the version installed on a selected PBX. Documented destinations include email, FTP or SFTP, local paths, Dropbox, SSH and S3, while credentials, reachability, permissions, retention, encryption, object state, region, quota and provider behavior remain destination specific. No PBX, credential, destination, backup job, archive, restore or call was inspected or tested

FreePBX backup destination test passes but the archive is missing

Trace the selected job, local archive, handler result, remote object and retention action before rotating credentials or widening destination permissions.

Read guide →