A backup of the database and the data are launched every day with a logrotate task. It is run at 06:25 a.m. and backups are kept for 7 days.
Retrieve the backup¶
You can retrieve the backup from the web-interface inpage.
Otherwise, with shell access, you can retrieve them in
In this directory you will find
data.tgz files for the database and data
What is actually backed-up?¶
Here is the list of folders and files that are backed-up:
The following files/folders are excluded from this backup:
- log files, coredump files
- audio recordings
- and, files greater than 10 MiB or folders containing more than 100 files if they belong to one of
asterisk from PostgreSQL is backed up. This include almost everything that is
configured via the web interface.
Creating backup files manually¶
A backup file may take a lot of space on the disk. You should check the free space on the partition before creating one.
You can manually create a database backup file named
issuing the following commands:
xivo-backup db /var/tmp/db-manual
You can manually create a data backup file named
issuing the following commands:
xivo-backup data /var/tmp/data-manual
A backup of both the configuration files and the database used by a Wazo installation is done
automatically every day.
These backups are created in the
/var/backups/xivo directory and are kept for 7 days.
- You must restore a backup on the same version of Wazo that was backed up (though the
amd64– may differ)
- You must restore a backup on a machine with the same hostname and IP address
- Be aware that this procedure applies only to XiVO/Wazo >= 14.08 (see 14.08).
Before Restoring the System¶
Before restoring a Wazo on a fresh install you have to setup Wazo using the wizard (see Running the Wizard section).
Stop monit and all the Wazo services:
Restoring System Files¶
System files are stored in the data.tgz file located in the
This file contains for example, voicemail files, musics, voice guides, phone sets firmwares, provisioning server configuration database.
To restore the file
tar xvfp /var/backups/xivo/data.tgz -C /
Restoring the Database¶
- This will destroy all the current data in your database.
- You have to check the free space on your system partition before extracting the backups.
Database backups are created as
db.tgz files in the
These tarballs contains a dump of the database used in Wazo.
In this example, we’ll restore the database from a backup file named
placed in the home directory of root.
First, extract the content of the
db.tgz file into the
/var/tmp directory and go inside
the newly created directory:
tar xvf db.tgz -C /var/tmp cd /var/tmp/pg-backup
Drop the asterisk database and restore it with the one from the backup:
sudo -u postgres dropdb asterisk sudo -u postgres pg_restore -C -d postgres asterisk-*.dump
To finalize the restore, see After Restoring The System.
When restoring the database, if you encounter problems related to the system locale, see PostgreSQL localization errors.
Alternative: Restoring and Keeping System Configuration¶
System configuration like network interfaces is stored in the database. It is possible to keep this configuration and only restore Wazo data.
Rename the asterisk database to asterisk_previous:
sudo -u postgres psql -c 'ALTER DATABASE asterisk RENAME TO asterisk_previous'
Restore the asterisk database from the backup:
sudo -u postgres pg_restore -C -d postgres asterisk-*.dump
Restore the system configuration tables from the asterisk_previous database:
sudo -u postgres pg_dump -c -t dhcp -t netiface -t resolvconf asterisk_previous | sudo -u postgres psql asterisk
Drop the asterisk_previous database:
sudo -u postgres dropdb asterisk_previous
Restoring the data.tgz file also restores system files such as host hostname, network interfaces, etc. You will need to reapply the network configuration if you restore the data.tgz file.
After Restoring The System¶
Resynchronize the xivo-auth keys:
Update systemd runtime configuration:
source /etc/profile.d/xivo_uuid.sh systemctl set-environment XIVO_UUID=$XIVO_UUID systemctl daemon-reload
Restart the services you stopped in the first step:
You may also reboot the system.