Bug: Plesk automatically starts scheduled backupjobs

[kaizer]

We have just set up a new server with Debian 6 and 10.3, and migrated from a 10.0 server (with Debian 5).

When I create a scheduled backup task, it seems that Plesk starts the backupjob immediately. This must be a bug.

 

[IgorG]

Why do you think so? I can't reproduce it on fresh Plesk installation on Debian 6 server. Need more details, investigation, logs, etc.

 

[kaizer]

Of course this must be a bug.
Because when you create a new scheduled backup task, it shouldn't start before the time I choose.

I am running top command, and I noticed backup tasks for these domains. The files was also uploaded on the FTP respository.

I have no idea on how to investigate this, but it is not my job. But you can of course get access to our server to look through the logs, no problem. Just send me a PM or e-mail, and I will provide you with server credentials.

 

[IgorG]

Sorry, but you should prove that you have found a bug, instead of we should find it on your server. Otherwise it looks like request for free support. Prove to us that you have found a bug and if you can't - contact support team. If they really find there a bug - they will send bugreport to developers and you will be refunded for support. I think that it is correct workflow.

 

[105547111]

Hi IgorG,

Actually, I know on my Centos 6 server that happened but only once when you first set a backup. I really consider it not a bug worth fixing.

As you know there is a scheduled backup in cron. All that happens is when cron runs the script, plesk sees it's time to start the backup (true maybe minutes to hours late).

However backups are critical, I see no problem with a single backup running after you first schedule one. It's like a test run. Also I see a very real issue if trying to stop this with a fix and destroying backups until another fix is done.

Simply put it's not worth it and the next time The time comes around it runs on time. If the server is so stressed it can't handle running the backup it's inadequate or what your trying to host. I do suggest you dont suspend domains during backup.

Cheers

 

[kaizer]

I am not the only one with this problem.
Please take a look at this thread: http://forum.parallels.com/showthread.php?p=457226

As I said earlier, it's not my job to investigate bugs in Plesk. I pay for the software and support, so Parallels needs to start listening to their customers.

 

[EricRB]

First time only

I think what the previous user might be correct. It happened to me to when I first set scheduled backups, and I think it is because whatever database table or file holds the information for when scheduled backups have run IF there is a schedule set, thinks that because that value is empty that it must run the backup immediately. Once the table/file/record is populated with one record, it doesn't happen again. Simple fix if I am right, if there is no entry, do nothing until the scheduled time set for the first scheduled backup.