Back up and restore the configuration
The configuration backup is a password-protected transfer of supported Obelisk settings and users. Use it before significant administrative changes and keep it outside the PBX. It complements a complete system backup, whose database, recordings and installation files have a different recovery scope.
Know what the archive contains
The archive includes users, permissions, two-factor authentication data, preferences, operational views, saved scenarios and supported application settings such as aliases, line selection and telephone normalization. It does not include the license, recordings, AI analysis history, CDR or queue log sources, or custom SQL routine and event definitions. Restoring preserves the destination’s database and AMI connections, paths and IP/proxy rules. These boundaries allow configuration recovery without silently replacing the destination’s infrastructure settings.
Create, preview and restore
Download a protected copy
Open Administration, Backup and restore. Choose an archive password of at least 12 Unicode characters, up to 1,024 UTF-8 bytes, and confirm your current administrator password. Store the archive and its password separately. Spaces and accented characters in the archive password are significant.
Read the restore preview
Upload an archive created by this function and supply its password and your current administrator password. Review the preview before explicitly replacing users and settings. Know the administrator credentials and any second factor contained in the archive before confirming.
Verify access after restoration
Existing sessions are closed. Sign in using the restored account, verify its permissions and preferences, and regenerate two-factor recovery codes: authenticator applications remain valid, while old recovery codes do not. Review any recipient corrections shown during the restore preview.
Check dependencies and recovery boundaries
Web PHP needs Sodium, zlib and a 64-bit environment. The application limit is 16 MiB; supporting that full size also requires upload_max_filesize of at least 16M and post_max_size of at least 20M. The screen reports the effective PHP limits; a proxy can reject uploads earlier. Before replacement, Obelisk retains a protected copy of the current settings using the same archive password entered for the restore. If recovery is interrupted, follow the generated recovery command and preserve its maintenance state.
Use the controls, understand what changes
Open the restore preview and review what will be replaced before confirmation. Keep the archive password available for the protected safety copy. Configuration backup and full SQL/audio backup cover different material; a successful configuration restore does not restore call history or recordings.
Complete product screenshots
Illustrative data. Open the screenshot to enlarge it and match the controls to the instructions in this chapter.
Open complete screenshot
Read the workspace section by section
Match the numbers and panels below to the complete workspace. These screenshots use illustrative data; the procedures above explain how to work with your own installation.
Restore preview
Review the archive, accounts and sensitive setting changes before confirming a restore.