Migration elastix 2.5 to Freepbx 15

Hello!
convert.freepbx.org is closed and I did not have time to migrate to freepbx 15 the last old elastix 2.5.0-1 server in one of the branches. ((
Is it possible to somehow simplify the configuration transfer using the standard freepbx 15 tools?

I don’t understand the question. If you have a 15 system running, you should only need to restore a backup from the old system.

We have an old Elastic server and we want migrate to freepbx 15!

Click through to the FreePBX GUI within Elastix. They have a button for that someplace.

make a backup
move backup to your FreePBX 15 system
restore it.

This method doesn’t work. At startup, an error appears:

[root@freepbx ~]# fwconsole chown
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Установка прав…
Setting base permissions…Завершено
Setting specific permissions…
_ 55006 [============================]_
Finished setting permissions

[root@freepbx ~]# fwconsole backup --restore /var/lib/asterisk/elastixbackup-20201208123201-l6.tar
Transaction ID is: fb907cd9-66cb-47b7-b0a1-7d8accc3a995
Determining backup file type…type is legacy
Legacy CDR Restore Option: 0
Starting restore job with file: /var/lib/asterisk/elastixbackup-20201208123201-l6.tar
Extracting backup…
Parsing out SQL tables. This may take a moment depending on backup size.
Found 0 database files in the backup.
Restore completed successfully

For example, I posted a full backup archive without recording conversations and voice mail

https://drive.google.com/file/d/1a1b4-IuaRlXvf085KeDpecDxN08IG-sP/view?usp=sharing

No one can help me?
Perhaps i need to bring the archive to the required data structure?:roll_eyes:

I may have missed it, but what is the error you are getting?

An error occurs when trying to restore a full backup from Elastix 2.5

" Starting restore job with file: /var/lib/asterisk/elastixbackup-20201208123201-l6.tar
Extracting backup…
Parsing out SQL tables. This may take a moment depending on backup size.
Found 0 database files in the backup.
Restore completed successfully"

Is this not the same conversation from this thread: Restore from 13 to 15 not working. Hangs at 99.97% on upload ?

The backup tarball is not the right format, how was the backup made? Are you using the FreePBX Backup module?

The backup was created directly via Elastix 2.5

Please tell me if it is possible to somehow perform the migration from elastix to freepbx ?

I told you already

Hello, i have same problem to migration config from Elastix 2.5.0 13.
On Elastix from GUI i made a full backup.
Install new FreePBX server 15.0.16.81
Open GUI > Backup&Restore > Restore> load my backup from Elastix > Run Restore …
It’s after restore:

Running with: /usr/sbin/fwconsole backup --restore=’/var/spool/asterisk/backup/uploads/elastixbackup-20201224144606-o6.tar’ --transaction=‘c440e0ea-4b11-4617-91f2-3f424986b38f’
Determining backup file type…type is legacy
Legacy CDR Restore Option: 0
Starting restore job with file: /var/spool/asterisk/backup/uploads/elastixbackup-20201224144606-o6.tar
Extracting backup…
Parsing out SQL tables. This may take a moment depending on backup size.
Found 0 database files in the backup.
Restore completed successfully

Any have idea ?

Post the output of

tar -tvf  /var/spool/asterisk/backup/uploads/elastixbackup-20201224144606-o6.tar

[root@freepbx ~]# tar -tvf /var/spool/asterisk/backup/uploads/elastixbackup.tar
drwxr-xr-x root/root 0 2020-12-24 14:46 backup/
-rw-r–r-- root/root 3072 2020-12-24 14:46 backup/control_panel_design.db
-rw-r–r-- root/root 10488 2020-12-24 14:46 backup/fw_fop.tgz
-rw-r–r-- root/root 3072 2020-12-24 14:46 backup/address_book.db
-rw-r–r-- root/root 1253 2020-12-24 14:46 backup/meetme_mysql.tgz
-rw-r–r-- root/root 6826 2020-12-24 14:46 backup/endpointconfig_mysql.tgz
-rw-r–r-- root/root 1564 2020-12-24 14:46 backup/roundcubedb_mysql.tgz
-rw-r–r-- root/root 1128496 2020-12-24 14:46 backup/tftpboot.tgz
-rw-r–r-- root/root 10139590 2020-12-24 14:46 backup/var.www.html.admin.tgz
-rw-r–r-- root/root 7168 2020-12-24 14:46 backup/fax.db
-rw-r–r-- root/root 44032 2020-12-24 14:46 backup/email.db
-rw-r–r-- root/root 748 2020-12-24 14:46 backup/versions.xml
-rw-r–r-- root/root 10106 2020-12-24 14:46 backup/etc.dahdi.tgz
-rw-r–r-- root/root 119610 2020-12-24 14:46 backup/mysql_mysql.tgz
-rw-r–r-- root/root 2983788 2020-12-24 14:46 backup/mysqldb_asterisk.tgz
-rw-r–r-- root/root 833 2020-12-24 14:46 backup/a_options.xml
-rw-r–r-- root/root 270567 2020-12-24 14:46 backup/etc.asterisk.tgz
-rw-r–r-- root/root 59834 2020-12-24 14:46 backup/mya2billing_mysql.tgz
-rw-r–r-- root/root 23552 2020-12-24 14:46 backup/acl.db
-rw-r–r-- root/root 36628 2020-12-24 14:46 backup/var.spool.asterisk.voicemail.tgz
-rw-r–r-- root/root 7168 2020-12-24 14:46 backup/menu.db
-rw-r–r-- root/root 178 2020-12-24 14:46 backup/var.www.faxes.tgz
-rw-r–r-- root/root 2048 2020-12-24 14:46 backup/calendar.db
-rw-r–r-- root/root 119 2020-12-24 14:46 backup/var.spool.asterisk.monitor.tgz
-rw-r–r-- root/root 116 2020-12-24 14:46 backup/var.lib.asterisk.moh.tgz
-rw-r–r-- root/root 5011856 2020-12-24 14:46 backup/var.lib.asterisk.mohmp3.tgz
-rw-r–r-- root/root 119 2020-12-24 14:46 backup/var.lib.asterisk.sounds.custom.tgz
-rw-r–r-- root/root 117 2020-12-24 14:46 backup/var.spool.imap.tgz
-rw-r–r-- root/root 41984 2020-12-24 14:46 backup/astdb.sqlite3
[root@freepbx ~]#

That doesn’t look like a backup generated by the FreePBX backup/restore module.

That is an elastix backup.

The OP was told to go to the FreePBX GUI to make a backup. The same applies to you.

1 Like

I made all task from GUI.

Wrong gooey, if i remember correctly you need ‘unembedded freepbx’, maybe my friend @danardf can help, he is a lot younger than me and French.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

Ho, Maybe try to use FreePBX 13 or 14 and try again.
once the restore done, you could make a backup in 14 and restore the data on 15.

From Elastix 2.5 to FreePBX 14 the works.
I just used the scipt to migrate it and I’ve had 99% of config migrated successfully.