My server has plenty of space. And this doesnt usually happen.
The MySql repair process can't create a temp(orary) file needed to copy the table content, because the current table file needs to be deleted and re-created during repair.
There can be many reason only your host can answer, eg.
for that error
Ask your host, there must be server error logs about the crash - usually that don't happen either
As said earlier: Because nobody here knows your server setup, it is a question you have to ask the people who should know the answer - and that is your host support staff:
You will need shell access
You will need to ask your hosts - all servers are different.
No - that is why you make backups.
Try Mr Google
If you cannot download it then it is unlikely that anyone else can.
Because I'm on VPS and only have 30 GB hosting space. Not enough for backups. VPS sucks. I'm paying more and it's less stable than shared hosting. A total ripoff. Everyone told me VPS was better. Turned out to be false. I would have to pay more to add more disc space. I was gonna do that. But I've never had a database table that was unrepairable before.warmweer wrote: ↑Wed Dec 13, 2017 11:44 pm
You had problems upgrading and finally succeeded: viewtopic.php?f=556&t=2446631&p=14870161#p14870161.
If I interpret your message (the one I just quoted) correctly, then your (personal) backup is either your phpBB3.0.x board or a 3.2.1 board from around November 22.
a) With all the problems you've had in upgrading: how can you not take backups before installing a whole bunch of extensions on your live board???
b) You've had weekly crashes? Backup alert!!!
c) What about your host: don't they have backups?
d) If this gets sorted out, considering the size of your database, take some time to read up on incremental backups (so that you don't have to download the whole database each time, and can have an almost up to date offline (backup)board available in case of calamities).
Your database is 2.5 GB and you only have 30 GB hosting space. Correct me if I am wrong but that leaves 27.5 GB available for other things. Seems to me that there's room for a copy of the whole forum.
Extensions are modifications and are tested as such. It's hard to guarantee that certain combinations of extensions won't cause conflicts somewhere, no matter how thoroughly they've been tested. And it's not exactly easy to test extensions in crash situations either.Extensions here don't usually crash databases. They are safe and tested and approved.
Well, there's also another principle which comes in handy sometimes: DIYNo my host doesn't do automatic backups unless I'm on shared hosting.
Only backup the differences between the current state and the state of the previous backup. BTW the previous backup could thus also be an incremental backup. I'ld suggest going for differential backups so that your last backup contains the differences with your latest full backup.How do you do incremental backups?
Actually (the dead horse is being flogged to gibberish now). If the database cannot be repaired online, what would you download to repair? With some luck it's only one table which is corrupt (you didn't even mention which table) but that one table may be linked to others.What if I do a backup now and then try to download the corrupted database and repair it offline?
No. As mentioned above, this is one of the reasons one backs up.
Users browsing this forum: Google [Bot] and 37 guests