PBXCenter supports backup policy, protected package export, import and controlled restore. The process covers configuration and the environment data explicitly included in the deployment scope.
Backup policy
Scope, frequency and retention follow business risk
Export and import
A protected package is checked before restoration
Recovery test
Services, routing and critical data are verified after restore
Backup policy
Scope, frequency and retention follow business risk
Administrators define a policy suitable for change frequency, recording value and target recovery time. Backup should not keep data longer than the organization's agreed purpose.
- Configuration, operational data and recordings may need different retention.
- Backup location should not share the environment's single point of failure.
- Only maintenance roles receive export and restore access.
Export and import
A protected package is checked before restoration
Export produces a package intended for controlled storage. Import validates material before a restore is requested instead of silently overwriting a running environment.
- The package is not a public archive for ordinary email attachment.
- Import and restore are distinct operations with visible results.
- Invalid material stops with an actionable error before replacement.
Recovery test
Services, routing and critical data are verified after restore
Recovering files is not the end of the test. Service health, provider, call flows, accounts, endpoints, included recordings and both call directions must be checked.
- The test records date, environment, scope and outcome.
- Recovery time is measured rather than inferred from archive size.
- Findings update both the backup scope and incident procedure.
FAQ
Direct answers before the conversation.
Does backup include call recordings?
That depends on the configured policy and agreed data package. Backup retention should not extend recording storage without a defined purpose.
How often should recovery be tested?
Frequency follows risk and change rate. The important requirement is a regular, documented test of working services rather than merely opening an archive.
Next steps
Move from answers to the right decision.
Deployment for your company
Define what must return after failure and how to prove it.
Describe critical numbers, data, recordings and acceptable interruption. That provides the basis for a backup policy and recovery exercise.