Hi,
I have a problem with database corruption in a 3CX self-hosted debian instance. The new calls are not being logged and reports cannot be issued anymore since the corruption of database a couple of weeks ago. The customer wants to rescue / save all call reports and records in the database up until the moment of corruption. I did try to see if i can export data using CDR, only it exports a small part. I can imagine that exporting via web interface does not give full information since the database itself is corrupt.
I have two questions concerning this matter. 1) can the full database somehow be exported to a large CSV to be imported in Excel at a later point? 2) Will a full purge of all logs reset a corrupt database, or would the whole 3CX instance need to be rebuilt to restore normal functionality with call logs and reports functioning normal again?
This log output hints to database corruption
The main problem is that next to no call logs, the corruption leads to a abnormally high CPU usage constantly on our 3CX machine.
I have a problem with database corruption in a 3CX self-hosted debian instance. The new calls are not being logged and reports cannot be issued anymore since the corruption of database a couple of weeks ago. The customer wants to rescue / save all call reports and records in the database up until the moment of corruption. I did try to see if i can export data using CDR, only it exports a small part. I can imagine that exporting via web interface does not give full information since the database itself is corrupt.
I have two questions concerning this matter. 1) can the full database somehow be exported to a large CSV to be imported in Excel at a later point? 2) Will a full purge of all logs reset a corrupt database, or would the whole 3CX instance need to be rebuilt to restore normal functionality with call logs and reports functioning normal again?
This log output hints to database corruption
The main problem is that next to no call logs, the corruption leads to a abnormally high CPU usage constantly on our 3CX machine.
