After upgrading another v14 to v17 we again see backup and restore is empty, again requiring all previous entries to be re-entered.
There is no mention of it anywhere in the freepbx17-install log
Am I missing something, again, or is this a bug? We had about 7 separate types of backups for different things and to multiple places, this will be a PITA if we have to recreate all these for every system we upgrade, thankfully thus far, most are happy to stay on v14 and not be upgraded, but still, a nasty missing things, you know, backups…
Hi @nickzed
We have not faced any 14 to 17 Backup & Restore issue locally and also no known feedback/complaints so far.
Could you please raise Github issue and attach your restore log from system 17 so we can dig further?
Thanks
Kapil
Thanks Kapil, I’m not overly happy with having to create a login there just to be told “unsupported method”.
I found a line I missed early in asterisk/backup.log, saying Restoring only legacy backup ftp servers to filestore, we used ssh, strangely, we also used local on a couple and this was ignored as well. I have verified there was entries in the full backup file we used in mysql2 tar file.
So I guess the restore section for v14 didnt take into account other methods and I somehow missed the warning about that cant be done.
okay. I was concern about restore process in 17. If no issue in 17 then its good as 14 is EOL.
uhg. this was a v14 backup, restored into a fresh v17 as sangoma claims works, I must have read wrong then 
only some things work for 14->17, my bad for missing those warnings whereever you hid them
@kgupta From your lack of further replies do I take that as I’m right? v17 does not fully support a restore from v14 as has been claimed?
Perhaps this issue is that it doesnt know what to do with backup databases, that no longer exist?
grep -c backup_ /var/log/asterisk/backup.log
0
MariaDB [asterisk]> show tables like ‘b%’;
±--------------------------+
| Tables_in_asterisk (b%) |
±--------------------------+
| broadcast_callees |
| broadcast_campaign_groups |
| broadcast_campaigns |
| broadcast_groups |
| broadcast_log |
| broadcast_settings |
±--------------------------+
6 rows in set (0.002 sec)No backups
Hi @nickzed Can you please raise Github issues for all the backup & restore issues you are facing along with backup log from v14 system and restore log from v17 system? Please note Github is publicly visible system so do not share any confidential information.
Best Regards
Kapil
I begrudgingly went there and github showed me a similar thread, upon reading it, you answered the question, so you knew freepbx17 couldnt do it with a v14 backup, WTF did you not just tell me here is bemusement, and why does sangoma say backup and restore is compatible back to v14 when you know its not.
thanks for wasting my time, but at least I still dont have a github account to give my personals to Microsoft yay
Hi @nickzed Can you please point me the GitHub issue which is highlighting backup from 14 to restore 17 is not working ?
As you can understand , we can fix the issue only if it’s reproducible for us and we are depend on issue reporter to share the steps with us to reproduce the issue in house.
If you are having issues then raise GitHub for every single issue and share the steps in the jira to reproduce.
@kgupta you told
Hi @Ressy66 Skipping Legacy Backup module This line means 17v Restore process is not restoring just the "backup" module configuration because 14's Backup module is different then 15+. this is expected behavior.
if you call that compatible, with a major component being ignored, we live in two realities, no warning did I ever see written saying only partial backups restore works. So you knew this, but you could not be bothered answering here, only telling people to go github, when you could have said this here to me 2 weeks ago and not WASTED my time.
Im more than convinced now sangoma is pushing to do to "free"pbx what RH did to centos, slowly, calculatedly, patiently, eliminating it.
Hi @nickzed “none” of your original report in this thread mentioned you are talking about “backup” module itself, your claim was or is that “Backup of v14 to v17” not working and this is what I am trying to find more because v17 is fully compatible to restore the v14 backups.
Backup module is different in v14 and v15+ and your point practically got visible only after checking your log file.
Best Regards
Kapil