SOLVED Incredible Backup for RasPi

[RPi-Fan]

Is there any way to quickly migrate the entire FreePBX configuration of an IncrediblePi 3.11.10 system to a freshly installed IncrediblePi 3.11.11 system? I have an up-to-date backup file of the 3.11.10 system (using FreePBX Backup & Restore), but when I try to restore it to the 3.11.11 system, no files are displayed to select for the restore. The same backup file will restore properly on the 3.11.10 system.

I have a very elaborate configuration and it's several hours of work to reconstruct it manually.

 

[wardmundy]

http://nerdvittles.com/?p=682

 

[RPi-Fan]

http://nerdvittles.com/?p=682

Ward,

The referenced backup and restore scripts don't appear to be compatible with IncrediblePi.

 

[wardmundy]

Sorry. Try this:

http://incrediblepbx.com/incrediblebackup11.tar.gz

 

[RPi-Fan]

Sorry. Try this:

http://incrediblepbx.com/incrediblebackup11.tar.gz

I'm afraid that one doesn't work either (it appears Asterisk, MySQL, and Apache cannot be stopped):

KILLING AMP PROCESSES
mpg123: no process found
kill: invalid option -- '9'
Usage:
kill [options] <pid> [...]
Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table
-h, --help display this help and exit
-V, --version output version information and exit
For more details see kill(1).
op_server.pl: no process found
mysqld: unrecognized service
httpd: unrecognized service
tar: 2.11.tar: Cannot stat: No such file or directory

The portion of the script being executed is:

amportal kill
service mysqld stop
service httpd stop
cd /tmp
tar -cf $BACKUP /var/www /var/lib/mysql /var/lib/asterisk /tftpboot /root /etc/asterisk /etc/crontab /var/spool/asterisk

 

[RPi-Fan]

I got this working with the following changes:

amportal stop
service mysql stop
service apache2 stop

...

service apache2 start
service mysql start
amportal start

Will there be any problems using amportal stop instead of amportal kill?

 

[wardmundy]

Will there be any problems using amportal stop instead of amportal kill?

Nope. Just takes longer. Kill doesn't wait for ongoing calls to end while stop does.

There were a couple other wrinkles. The filename algorithm no longer worked with newer versions of FreePBX. Should be good to go now. Just download incrediblebackup11.tar.gz again.

File naming convention for Incredible Backups...
Five arrows show: (1) Backup date (2) Backup time (3) Asterisk version (4) FreePBX version (5) Incredible version

Before you restore the backup to a new machine...
1. The Asterisk major release (i.e. 11) and FreePBX version (i.e. 2.11) on the restore machine need to match the backup filename numbers (i.e. arrows 3 & 4) BEFORE you begin a restore.

2. If the minor version of Asterisk or FreePBX is different, it shouldn't affect the success of the restore operation.

3. While I have not yet tried it, I see no reason that you couldn't restore a backup from a CentOS-based server to a Debian/Ubuntu-based server and vice versa so long as the Asterisk and FreePBX versions are the same.

 

[RPi-Fan]

Should be good to go now. Just download incrediblebackup11.tar.gz again.

amportal kill still produces the following on a Raspberry Pi:

root@incrediblepbx:~# amportal kill
Please wait...

KILLING AMP PROCESSES
mpg123: no process found
kill: invalid option -- '9'
Usage:
kill [options] <pid> [...]
Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table
-h, --help display this help and exit
-V, --version output version information and exit
For more details see kill(1).
op_server.pl: no process found
root@incrediblepbx:~#

 

[wardmundy]

upstream problem. harmless error.

 

[RPi-Fan]

Ward,

Thank you for the updated incrediblebackup11.tar.gz. It appears to work correctly to migrate IncrediblePi 3.11.10 to 3.11.11. Assuming no surprises surface, it saved me many hours of manual configuration.

Ron