Once you’ve got your Trixbox all set up, you need to think about backups â€“ what happens if your system needs to be restored, or if you’re doing and upgrade (say from version 2.0 to 2.2)?
The FreePBX module in Trixbox has a handy â€œSystem Backupâ€ feature â€“ in FreePBX, go to Tools->Backup & Restore.
Click on the â€œAdd Backup Scheduleâ€ link and name your new schedule â€“ I personally take the simple approach of just doing a weekly backup on Sunday night.
When your backup is created, Trixbox places a â€œ.tar.gzâ€ file in the /var/lib/asterisk/backups/ directory. So, if you created a schedule called â€œWeeklyâ€ your backup file would be placed in the directory /var/lib/asterisk/backups/Weekly/. Here these files will stay â€“ a new one is created each time your scheduled backup is run â€“ unless you do something with them.
For obvious reasons, we want to move these backup files to another server for safe keeping. Additionally, one we’ve successfully moved our backup, we want to clean up the old files from our backup directory.
There are any number of ways of doing this. Here is my preferred method:
Create a new user on your Trixbox machine, and add that user to the â€œasteriskâ€ group. (The user will need to be a part of this group to access the backups directory.)
useradd -G asterisk backup
Log in as this new user, and create a key pair for ssh connections. When prompted to enter a pass phrase, simply hit enter (blank pass phrase).
ssh-keygen -t dsa
Export your public key to the machine where you will be storing your backups.
scp ~/.ssh/id_dsa.pub firstname.lastname@example.org:.ssh/authorized_keys
Make sure you can SSH to the machine where you will store your back up files. You’ll want to make sure that key-based authentication is working (i.e., that your not prompted for a password).
Make sure you can securely copy files to the machine where you will store your back up files (again, make sure that your not prompted for a password).
scp /var/lib/asterisk/backups/Weekly/* email@example.com:trixbox_backups/
If all of the above steps went successfully, you are now ready to set up your automated process. We’ll use CRON to do this.
Log on as the new backup user on your Trixbox machine.
Create a new crontab for this user.
Insert cron entries to copy backup files to the remote machine, and to clean up old files after they have been moved.
01 0 * * 1 scp /var/lib/asterisk/backups/Weekly/* firstname.lastname@example.org:trixbox_backups/
01 1 * * 1 rm -f /var/lib/asterisk/backups/Weekly/*
The first entry will move our weekly backup file at 12:01 a.m. on Monday morning to our remote server. The second entry will clear the Weekly directory an hour later. This way, when you go to the office on Monday, all of your backup process are done and your ready to start the week on a good note.
In the next article, we’ll discuss how to monitor your Trixbox to make sure that it is performing properly.