Hi MixHa,
Unfortunately, whatever fixes you applied to the latest release of Backup Migration failed to address this issue. I note that the PHP code in the getAvailableBackups function is unchanged. As mentioned previously, when the client browser makes a request for the current backups status, it opens (and locks) the zip to read out the manifest, and simultaneously the backup process is attempting to access the zip to add additional files, but gets an error as the zip archive is locked and the backup aborts with the “maybe out of space” error. Applying my patch, at approx. line 218 in the getAvailableBackups function of the ./include/scanner/backups.php file, to check for the existence of a ‘./running’ file, and skipping access/retrieval of the zip archive that is the current backup in progress is how I have addressed this issue.
$path = $backup['path'] . '/' . $backup['filename'];
// If backup is running and temp file exists, skip it
if ( file_exists( BMI_BACKUPS . '/.running' ) && !empty( glob( $path . '.?*' ) ) ) {
continue;
}
...
Let me know what you think,
Regards,
Mark
