Backup and Restore PortSIP SBC
This article describes how to back up and restore a PortSIP SBC server on Linux. These procedures are intended to ensure no data loss during system upgrades, migrations, or disaster recovery scenarios.
Backup files and data must be stored on a separate server or external storage device, not on the SBC used for daily operations.
All procedures are performed from the command line and require root-level access.
❗Important
Linux SBC backup data can only be restored to another Linux SBC.
Always validate backups by performing periodic test restores in a non-production environment.
Backup Methods
Using Virtual Machine or Cloud Snapshots (Recommended)
If your PortSIP SBC is running in a virtualized environment (such as VMware, KVM) or on a cloud platform, you can create a snapshot using the platform’s native tools.
Snapshots capture the complete system state and provide a fast and reliable backup mechanism.
❗Best Practice Regularly test snapshot restores to ensure the SBC can be successfully recovered in the event of a failure.
Restoring from a Snapshot
To restore the SBC from a snapshot:
Follow the restore procedure provided by your virtualization or cloud platform.
Start the SBC services.
Verify SIP signaling, media traversal, and network connectivity.
Backing Up SBC Data on Linux
When installing PortSIP SBC on Linux, the -p parameter specifies the parent directory used to store SBC data.
Installation Examples
SBC v11.x
SBC v10.x
The SBC data is stored in the following subdirectory of the parent path:
❗Important Only the
sbcsubfolder must be backed up.
Backing Up Using the Default Data Path
If the default parent path /var/lib/portsip is used:
SBC v11.x
SBC v10.x
Backing Up Using a Custom Data Path
If the SBC was installed with a custom parent path, for example:
Back up the following directory instead:
After completing the backup, store the data securely on a separate system.
Restoring Backup Data on Linux (SBC v11.x)
Restore to the Same Server
1. Stop the SBC and Remove Existing Data
2. Restore the Backup Data
Copy the backup data to the SBC server:
Ensure that the restored directory, all subdirectories, and files have UID:GID set to 888:888.
3. Start the SBC with Restored Data
Result: The SBC is successfully restored on the same server.
Restore to a New Linux Server (SBC v11.x)
❗Note When restoring to a new server, the SBC will be automatically upgraded to the latest v11.x release.
Prepare the new Linux server without installing PortSIP SBC.
Copy the backup data to the new server:
Ensure permissions are set to
888:888.Install PortSIP SBC v11.x and specify the restored data path using the
-pparameter.Sign in to the SBC Web Portal.
Navigate to Settings > Network and update the SBC IP addresses to match the new server.
Save the changes.
Restoring Backup Data on Linux (SBC v10.x)
The restore procedure for SBC v10.x is identical to v11.x, except that the Docker image tag is portsip/sbc:10.
Restore to the Same Server
Restore the data and start the SBC:
Restore to a New Linux Server (SBC v10.x)
❗Note When restoring to a new server, the SBC will be automatically upgraded to the latest v10.x release.
Prepare the new Linux server.
Copy the backup data to the server.
Install PortSIP SBC v10.x using the restored data path (
-p).Sign in to the SBC Web Portal.
Go to Settings > Network, update the SBC IP addresses, and save the changes.
Notes and Best Practices
Permissions (
888:888) Incorrect ownership or permissions may prevent the SBC from starting correctly.IP Address Changes Always update SBC network settings after restoring to a different server to ensure proper SIP signaling and media routing.
Backup Validation Periodically test restores to confirm backup integrity and recovery readiness.
Last updated