Before the backup is started the iTSec plugin tries to get a file lock.
It might be the file lock creation fails.
The file lock is actually a directory named backup.lock and it is by default created in the wp-content/uploads/ithemes-security/ directory.
After the backup is completed the file lock is (normally) removed.
If the “Enable Scheduled Database Backups” checkbox is ticked in Settings tab\menu option “Database Backups” section first (temporarily) disable it and Save settings.
Then check the wp-content/uploads/ithemes-security/ directory for the file lock and if it exists try to manually delete it. Then retry making a backup.
If this solves your backup problem please mark this topic as “Resolved”.
dwinden
Thread Starter
traid
(@traid)
No did not help. And one more thing. Recently started having problems when loading the administrative part of the site is loaded white screen and the page is refreshed everything was normal. If you disable the plugin iThemes Security, everything works fine. Probyval plugins disable one one thought may conflict with others. It did not help.
Ok, I see. Are you using the latest iTSec plugin release (4.6.6) ?
dwinden
Ok, good. Did the backup.lock folder exist and did you delete it ?
Please update this topic with ALL your current iTSec plugin backup settings.
Dwinden
Thread Starter
traid
(@traid)
I did as you said. Delete this folder. Removed the tick. Make a backup copy. An error and the file appears again.
If the “Enable Scheduled Database Backups” checkbox is ticked in Settings tab\menu option “Database Backups” section first (temporarily) disable it and Save All Settings.
Did you click on the Save All Settings button ?
Please doublecheck.
Also check the Backup folder for any .sql and\or .zip files. If many files exist delete some to free up diskspace.
Dwinden
Thread Starter
traid
(@traid)
There’s no such files. All did as you said does not helps. Okay, let’s not tormented.
Weird, I think this is an issue that can really be solved this way.
I got it solved exactly the same way in another topic.
I’m 100% sure it is related to the backup.lock folder being created.
Well in your case it fails to create probably because it is already there.
Even though you have just deleted it.
The only reason why the backup.lock folder is recreated in the background is because a scheduled backup already kicked off before you can start one manually. So disable the “Enable Scheduled Database Backups” option (unticking the checkbox alone is not enough) and then click on the “Save All Changes” button.
Won’t hurt to check whether the “Enable Scheduled Database Backups” option is disabled …
If it is I give up … hihi
dwinden
