BackupBuddy Restore Error Code 9005 – File extraction process unsuccessful

The Problem

I botched up an upgrade and set out to restore my site using BackupBuddy.

The Error

I promptly followed the recommended steps of uploading the importbuddy.php and backup zip files to my site http://test.com. I then deleted all the contents of my site as the process demanded.

On executing the importbuddy.php from my browser using the URL http://test.com/importbuddy.php, I encountered the following error –

Failed unzipping archive.
File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to “Skip File Extraction” from the advanced options on Step 1. ImportBuddy Error Code 9005.

Before attempting a manual extraction, I quickly looked up what error code 9005 means and this is what the iThemes website said –

9005


File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to “Skip File Extraction” from the advanced options on Step 1. (importbuddy.php)

  • This ZIP file was unable to be extracted for some reason.
    • Unzipping may have taken too long and the PHP process halted.
    • Server memory usage may have been exceeded.
    • Server configuration may be blocking extracting of ZIP files.
  • Attempt manual extraction & disable File Extraction from the advanced debugging options of Step 1.

I knew file size and memory weren’t the issues as my backup file was hardly 30MB. Wondering if it has anything to do with server configuration, I proceeded to extract the backup file manually. Unfortunately, that failed too and the following error popped up –

End-of-central-directory signature not found. Either file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk of this archive.

As a last ditch attempt, I tried to unzip the backup file manually on my local system and realized that it can’t be extracted. It seemed that the backup file is corrupted and hence unusable.

The Fix

The only way to fix the problem was to retry with another backup file. Thankfully I had opted for offsite storage and hence could fall back on another backup to restore my site.

Did you know?
blogVault has a test-restore feature that lets you test if a specific backup works fine before going live with it. That way you can avoid surprises later and be 100% sure that your backup works perfectly well.