One way you can end up with missing posts is restoring an incomplete backup or if it times out while restoring a complete backup.
Both are caused by php's max_execution_time being reached. It's common to see this on posts and search table because they are typically largest tables increasing the chance that is where it will occur.
Easy way to see if the file is truncated is open it with text editor, the last insert statement should be for the phpbb_zebra table. If it's truncated there is no recourse, it's only good for partial restoration. If it's complete backup you need to increase max_execution_time in php.ini or use SSH.
Both are caused by php's max_execution_time being reached. It's common to see this on posts and search table because they are typically largest tables increasing the chance that is where it will occur.
Easy way to see if the file is truncated is open it with text editor, the last insert statement should be for the phpbb_zebra table. If it's truncated there is no recourse, it's only good for partial restoration. If it's complete backup you need to increase max_execution_time in php.ini or use SSH.
Caution with this, it's not really your backup but their backup for disaster recovery if for example the server is using RAID5 array and loses two disks. They typically only have one and you could end restoring something that is corrupted depending on when the backup was created.Kind of regardless of what has happened, you could restore your site from backup on the host.
Statistics: Posted by thecoalman — Thu Feb 06, 2025 12:39 pm