Backing up and restoring your 3CX system
How to schedule 3CX backups, what they include, and how to restore your system quickly if something goes wrong.
Your 3CX system holds a lot of work: every extension, your inbound and outbound rules, digital receptionist greetings, ring groups, queues, business hours and trunk settings. If a server dies, a cloud instance is rebuilt, or someone breaks call routing, a recent backup is the difference between a five-minute restore and a day of rebuilding from memory. The good news is that 3CX makes this easy, and once scheduled, backups run without anyone thinking about them.
This guide covers what a 3CX backup includes, how to schedule one, where to store it, and how to restore quickly — written for the person who has to act when the phones are down.
What a 3CX backup actually includes
The built-in Backup & Restore tool in the Admin Console captures your whole configuration in a single file. A backup can include:
System configuration
extensions, SIP trunks, inbound and outbound rules, ring groups, call queues, the digital receptionist (IVR), office hours and any Call Flow Designer apps.
Voicemail messages
optional, and they can grow the file.
Call recordings
optional, and usually the biggest component.
Call history and reports
your call logs and reporting database.
Provisioning and phone settings
so re-provisioned desk phones come back as they were.
You choose what to include. A configuration-only backup is small, fast and enough to rebuild a working phone system. Include recordings only if you need them — expect a much larger file and plan storage accordingly.
How to schedule automatic backups
A backup is only useful if it is recent, and manual backups get forgotten — so set a schedule and leave it running. In the Admin Console:
Open Backup & Restore and create a scheduled backup.
Choose how often it runs. Daily suits most businesses; if your config rarely changes, a few times a week is fine.
Decide what to include — a daily configuration backup, plus a less frequent full backup if you keep recordings.
Set how many backups to keep (rotation) so old files are pruned automatically and the disk does not fill.
Point it at an off-box storage location — more on that below.
The principle that matters: a backup on the same server it is protecting is not really a backup. Lose the server and you lose the file.
Where to store backups (the part people skip)
Keep at least one copy off the machine. 3CX can send scheduled backups to remote storage such as an FTP/SFTP server, a network share or supported cloud storage. Pick somewhere that survives a hardware failure or a rebuilt instance.
Self-hosted or on-premise 3CX
push backups off that server. If you are weighing where to host, our guide on hosting options covers the trade-offs.
Hosted / cloud 3CX
your provider may handle snapshots, but still keep your own configuration backup somewhere you control. See Hosted PBX.
Before any change
take a manual backup before upgrades, trunk changes or routing edits, so you have a clean rollback point.
How to restore your system
Restoring is straightforward, but know one thing first: a restore overwrites the current configuration with the backup file. It is all-or-nothing, not a merge.
Stand up a 3CX instance on a matching major version — a backup restores cleanly into the version it came from.
Open Backup & Restore and restore from your file.
Let it rebuild, then verify the essentials: extensions register, the SIP trunk shows connected, and a test call routes through your inbound and outbound rules.
If you run a Session Border Controller (SBC) or remote phones, re-check provisioning and registration.
One honest caveat: restoring onto new hardware or a new IP address can mean re-provisioning desk phones and reconfirming trunk and firewall settings. It is usually quick, but it is the step people forget under pressure. If you would rather not learn this during an outage, SIP Connect can set up scheduled backups and document a tested restore — call 1300 747 266 or use our contact page.
It is worth doing a test restore into a spare or cloud instance now and then, so you know the file works before you depend on it. Backups also pair with planning for outages: if staying answerable during a failure matters, read our guide on failover and business continuity. On the 3CX phone system, a recent backup is what makes those plans practical.
What we see installing this in Melbourne
On Melbourne SME sites, the most common pattern we see is a 3CX install that has never actually had its backup tested. Scheduled backups are ticking over, but they are landing on the same VPS or office NUC the PBX is running on — so when the disk fills or the instance gets rebuilt, the backups go with it. Pushing the file to an SFTP target, a Google Drive or a separate AU-region cloud bucket is a ten-minute job that nobody got around to.
The other thing that bites locally is NBN upload. A configuration-only backup is tiny, but once recordings are bundled in we routinely see backup files of several gigabytes trying to crawl off a 20/20 FTTC or worse a 50/20 FTTN line overnight. We usually split it: a daily config backup off-site, a weekly full backup, and recordings archived separately.
Where we add value during installs is the bit teams skip — taking a backup before every change, doing a real restore into a throwaway instance, and writing down which desk phone models and SIP-trunk credentials need re-entering if an IP changes.
Frequently asked questions
How often should I back up my 3CX system?
Daily is the sensible default for a configuration backup, plus a manual backup before any major change such as a version upgrade or trunk swap. A daily backup costs so little there is rarely a reason to skip it.
Do 3CX backups include call recordings and voicemail?
They can, but it is optional. A configuration-only backup is small and rebuilds a fully working phone system. Recordings and voicemail are usually the bulk of the file size, so include them only if you need them.
Can I restore a 3CX backup onto a different server or in the cloud?
Yes. Restore into an instance on the same major 3CX version and your configuration comes back. Be ready to re-provision desk phones and recheck trunk and firewall settings if the IP address or hardware has changed.
What happens to current settings when I restore?
A restore overwrites everything with the backup file; it is not a merge. That is why a backup taken just before a risky change gives you a clean, known-good rollback point.
Get a free bill analysis — and stop overpaying
Send us a recent phone or internet bill. We’ll show you exactly where the waste is — our bill reviews have identified savings of up to 65%.