Back up the system's actual state
A recoverable FusionPBX deployment needs more than a database dump. Inventory application configuration, FreeSWITCH scripts and configuration, required recordings and voicemail, certificates and any external integrations. The official backup examples distinguish package and source installation paths; adapt the inventory to the actual installation. Inspect the installed backup job rather than assuming every example archive command is enabled. Confirm what was included, where it is stored, how failures are reported and how long copies remain available.
Protect sensitive material
Backups can contain SIP credentials, database access and private call content. Encrypt and restrict them, separate backup access from ordinary tenant administration and retain a copy outside the primary host's failure boundary. Restrict web administration, database and Event Socket exposure. Use current application and engine security updates. Tenant-facing permissions should be tested for recordings, device settings and domain selection, especially after customization.
Restore without competing with production
Use an isolated recovery environment that cannot place unintended calls, claim live registrations or send user notifications. Restore a compatible application/database/runtime set, then validate administrative access, tenant isolation, extensions, routes and required media assets. Measure the time to recover and identify any manual dependency, including certificate renewal and provider address changes. Keep the observed result with exact versions. A backup job returning success is a useful collection result; restoration and a working controlled call establish a different, stronger result.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.