Incremental backup fail

Submitted by PatTzZ on Sun, 01/25/2015 - 08:43 Pro Licensee

Hi!

I scheduled an automated incremental backup for all virtual servers and i use ssh to upload it to another server somewhere.

One day it stopped to work in automated mode but it was possible to do the backup manually and it was working.

Now, for a while, it fail all the time giving error "Failed to lock the file, like this:

HTTP/1.0 500 Perl execution failed Server: MiniServ/1.730 Date: Sun, 25 Jan 2015 14:11:57 GMT Content-type: text/html; Charset=iso-8859-1 Connection: close

Error - Perl execution failed

Failed to lock file /home/airmat2/.backup after 5 minutes. Last error was : at /usr/libexec/webmin/web-lib-funcs.pl line 1397

Can you help me to fix this issue please?

Thanks in advance!

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Sun, 01/25/2015 - 12:27

Is there another backup running of the same domain at the same time?

If not, check the file /home/airmat2/.backup.lock for the PID of the process that has locked the domain. It may be a stuck backup which can be killed, thus freeing up the lock.

Submitted by PatTzZ on Sun, 01/25/2015 - 14:59 Pro Licensee

Hmm. Yes, i'm doing a full backup on local drive at 00:00 and an incremental backup that i upload on another server that start at 01:00 .. I seen that my full backup runned around 10 hours, so, it's possible that some domain has been backup at the same time.

However, when i do it manually like now, no backup is running and it give me the same error.

Submitted by JamieCameron on Sun, 01/25/2015 - 18:10

Does it help if you delete that .backup.lock file (or kill the process whose PID is in the file) ?

Submitted by PatTzZ on Mon, 01/26/2015 - 07:13 Pro Licensee

In fact, you got it. It was coming from another backup running at the same time. I just switched my incremental backup to run before the full backup, so, it has time to finish and everything is ok.

Thanks for you help.

Submitted by Issues on Mon, 02/09/2015 - 21:40

Automatically closed -- issue fixed for 2 weeks with no activity.