Backup/restore module caused my FreePBX 2.11 to downgrade to 2.10

I am trying to do a migration from FreePBX distro 1.814.210.58-2 to 4.211.64-5. I had setup the new server, done all the base configs and had everything setup good for the most part.

I ran a backup of the old 2.10 server and restored on the 2.11 server. After the restore though it took me back to 2.10.

I could use some assistance on bringing only the data over from the old server that I need vs reverting myself to the same version of the old server. I am backing up the following

/etc/dahdi
/tftpboot
ASTSPOOLDIR/voicemail
ASTVARLIBDIR/moh
AMPBIN
AMPWEBROOT
ASTETCDIR
ASTVARLIBDIR/sounds/custom

MySQL: CDR Server, Config server

Asterisk DB

When I did the restore I selected all the folders, FreePBX settings, and CDR database.

You can’t do that. Either upgrade just FreePBX from the web interface or run the distro update scrips.

Actually it is quite easy, just uninstall 2.11 from the new box and install 2.10 much like:-

http://www.freepbx.org/forum/distro-discussion-help/29-download-or-import-from-backup-to-211

then just restore the backup to that machine and then upgrade to 2.11 from the gui.

So at this point I am running on CentOS 6.4 with Asterisk 11 as it was the distro install of 4.211.64-5. Is there a way to put everything back to the way it was before the restore but leave the configs if that makes sense? I want FreePBX back up to the 2.11 version that came with the distro but all my backup information.

As far as upgrade scripts I don’t think that will work, the reason I am doing this migration is there was no upgrade path from 1.814.210.58-2 to 4.211.64-5.

dicko, I am trying to go from 2.10 to 2.11 but thank you.

OK so I just found the FreePBX 2.11 module and went that route to bring everything back up to 2.11 with my settings. I need to do some verification but should I be OK? Obviously this is not the cleanest method of migration and I fear going back and forth like that has caused some issues.

Doing some spot checking, the follow things are incorrect

cat /etc/asterisk/version
Asterisk 1.8.13.0

System Admin Module

PBX Firmware: 1.814.210.58-2

Not sure where else things might be incorrect but I would at least like to fix these

Why is that “incorrect” ?

There is a fair chance that any commercial modules will not migrate correctly, so I suggest you uninstall them after the restore if you take this path. I only do the open source bit of FreePBX.

Well there happened to be an upgrade script to go to 4.211.64-6 which is good because I wanted to test an upgrade and it seemed OK but I did get an error which shouldn’t matter cause I don’t use it.

It also fixed the PBX firmware in the system admin module but /etc/asterisk/version is incorrect

Failed:
kmod-dahdi-linux.x86_64 0:2.7.0-43_centos6.2.6.32_358.0.1.el6.x86_64

Personally I build everything from scratch, I am sure they will fix it eventually.

Ya stuff is not working after the back and forth.

[2013-09-04 15:01:18] ERROR[5682]: config_options.c:495 aco_process_config: Attempting to process uninitialized aco_info
[2013-09-04 15:01:18] ERROR[5682]: config_options.c:495 aco_process_config: Attempting to process uninitialized aco_info
[2013-09-04 15:01:18] WARNING[5682]: named_acl.c:414 ast_named_acl_reload: Could not reload ACL config
[2013-09-04 15:01:18] WARNING[5682]: named_acl.c:414 ast_named_acl_reload: Could not reload ACL config
[2013-09-04 15:01:18] WARNING[5682]: manager.c:7808 __init_manager: Invalid writetimeout value ‘’ at line 19
[2013-09-04 15:01:18] WARNING[5682]: manager.c:7808 __init_manager: Invalid writetimeout value ‘’ at line 19
[2013-09-04 15:01:18] ERROR[5682]: config_options.c:512 aco_process_config: Unable to load config file ‘udptl.conf’
[2013-09-04 15:01:18] ERROR[5682]: config_options.c:512 aco_process_config: Unable to load config file ‘udptl.conf’
[2013-09-04 15:01:18] WARNING[5682]: udptl.c:1423 __ast_udptl_reload: Could not reload udptl config
[2013-09-04 15:01:18] WARNING[5682]: udptl.c:1423 __ast_udptl_reload: Could not reload udptl config

My guess is you over engineered everything, choose one route and stick to it.

All FreePBX needs to work is a working LAAMP stack, all the various distro’s provide that, or roll your own. Do not try to install FreePBX over another extant version, remove/uninstall the extant version first.

I say because you have managed to get two /etc/asterisk/logger* entries to write to /var/log/asterisk/full,