Hi there – how have you tested this theory? I ask because usually when I test this kind of issue out, the temporary file never is deleted because the backup process is never signaled as ‘completed’ according to the plugin. This is usually because of some type of server limit, like max_execution_time or sometimes memory_limit, which kills the process but doesn’t pass that information on correctly. Generally when it happens like this, it is happening at almost the same time as the backup would be completing, which is why the backup appears to be complete.
Deleting the temporary file is definitely the trigger to complete the backup, but usually the fact that it isn’t being deleted is due to some specific reason.
Kat
Thread Starter
commpc
(@commpc)
What is this thing “tested” you speak of? 😉
I just noticed the lock file wasn’t deleted and what happened when I deleted it manually.
I looked around the forum before I posted and didn’t see anything about this. I’ll take a look for the issues you mentioned above.
Thanks much for your patience.
No worries at all – it’s a valid observation and solution for sure. I just know because I have tested it on a few different sites where I had server access and where we uncovered limits that caused the issue. 😉
Definitely let me know what you find out!
Kat
Thread Starter
commpc
(@commpc)
Sorry for the delay. I cut the backup size down from 1.1 GB to 259 MB and it still fails to delete the lockfile. The backup files are usable though. I thoroughly checked that.
I’m enabling Support from the admin. Thanks!
That’s great – I’ll follow up from there!
Thanks,
Kat
Can you remind me of whether we were able to make headway on this over our support channel? I’ve seen others reporting that the lock file isn’t being deleted and I’d love to pin a cause down if we can!
Thanks,
Kat
