Open Source Training Seminar FreePBX Paid Support

Ticket #2743 (closed Bugs: fixed)

Opened 6 months ago

Last modified 4 weeks ago

backup should detect corrupt astdb.dump files at backup and at restore and try to deal with them

Reported by: InsolentDreams Assigned to:
Priority: minor Milestone: 2.5
Component: Backup & Restore Version: 2.4.0
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version: 1.4.17

Description

Attempting a migration from one computer to another, I did a backup now which resulted in a 0 byte astdb.dump file. Not knowing that this was bad, I've been trying to get another server up and running with this backup unsuccessfully.

I've attempted to repeat this and am currently unable to, but I have the backup with the file being 0 bytes. I was asked by a IRC user if I was running asterisk during the backup, and I am sure that Asterisk and MySQL were all running, the phone system was fully functional when I ran the backup.

FreePBX should at least notice during importing, preferably also during exporting that this file is empty and at least notify the user that the backup may not work but continue the import/export.

Setup details: Gentoo Linux x86, 8 x Intel(R) Xeon(TM) CPU 3.00GHz (2xQuad Core), 8GB RAM, 2.6.23 Kernel, Asterisk 1.4.17, FreePBX 2.4.0rc1.1

Change History

07/12/08 15:15:28 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • milestone changed from Cut Line to 2.5.

08/02/08 19:51:57 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

(In [6275]) closes #2743, at least partially, so that we will not delete all the current entries if the restore dataset has an empty or blank astdb.dump file which otherise completely breaks the system

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads