• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

plesk 11.5.30 Update #39 backup bug

Status
Not open for further replies.

CharlesFC

New Pleskian
Hi,

backup issue with plesk 11.5.30 Update #39 .


Currently, I have set the Maximum number of backups in repository for the website under Scheduled Backup Settings is 3.

After I have upgraded to 11.5.30 Update #39, when the Maximum number of backups in server repository has reached, the new backups does NOT replace oldest backups in the repository. Thus the backup keeps eat the disk space and the system keeps sending me the warning message about the use of space.

Does anyone else have the same problem ? The 11.5.30 Update #38 does not have this issue.

Regards

Charles
 
I've tried to reproduce this issue but no luck.

Is it possible for you to open support ticket?
 
Guys, we can't reproduce it on our test servers. Looks like detailed investigation directly on your servers is required. Therefore I suggest you contact Parallels Support Team. You will be refunded for ticket if it is really our bug.
 
I can't speak for the other posters, but the accounts that I have problems with were migrated via the migration tool from a previous version of Plesk.

The path would have been: migration from Plesk 9.5 to new server with Plesk 10 which has followed the upgrade path to latest version - backups have functioned correctly through out this process until mu #39

It is possible that new accounts created via Plesk 10 or 11 do not exhibit the behavior, hence not possible to recreate.

I licence Plesk through a re-seller and don't have a direct account with Parallels - what would be best method to open a support ticket?
 
Last edited:
That seems to be a lot of money to fix a problem that was introduced at the last update - the backup has worked without issue up until micro update 39
 
That seems to be a lot of money to fix a problem that was introduced at the last update - the backup has worked without issue up until micro update 39

There are no evidence that this is our bug. But if so, you will be refunded as I wrote before.
 
I have the same bug on my server. It started after MU #39.

OS CentOS 5.9 (Final)
Panel version 11.5.30 Update #39
 
Just wanted to chime in and add that I'm also having the same problem. Only started after the upgrade to 11.5.30 MU #39. It's eating my drive space like crazy. I'm having to go in and manually delete backups daily. I'm the 5th person with this problem. This can't be a coincidence. I'm running CentOS 5.10 (Final).
 
the bug is still present
I changed $storage->getMainDumpXmlFile() to $storage->getMainDumpRelativePath() in plesk_agent_manager file
I've CentOS release 6.5 (Final) with 11.5.30 Update #41, last updated at April 14, 2014 10:09 PM
 
Could you please show log of scheduled backup session, it should be stores in /usr/local/psa/PMM/logs/backup-<timestamp>/backup.log
At the end of file there should be something like:

[2014-04-15 12:14:26.206|15146] INFO: pmm-ras finished. Exit code: 0
[2014-04-15 12:14:26.216|15148] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --rotate-dump --dump-rotation=3 --guid=10f1411b-72aa-414a-ac91-406812799e36 --dump-specification=domains/domain.tld/backup_domain.tld_info_1404151214.xml --dump-storage=/var/lib/psa/dumps --storage-structured --session-path=/usr/local/psa/PMM/sessions/2014-04-15-121402.174 --verbose
[2014-04-15 12:14:26.216|15148] INFO: Repository '/var/lib/psa/dumps': Initializing...
[2014-04-15 12:14:26.216|15148] INFO: Repository '/var/lib/psa/dumps': Initialized
[2014-04-15 12:14:26.216|15148] INFO: Repository '/var/lib/psa/dumps': Rotate structured backups is started for owner 10f1411b-72aa-414a-ac91-406812799e36
[2014-04-15 12:14:26.216|15148] INFO: Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_domain.tld_info_1404151204' at path domains/domain.tld
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_domain.tld_info_1404151154' at path domains/domain.tld
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_domain.tld_info_1404151214' at path domains/domain.tld
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_domain.tld_info_1404151144' at path domains/domain.tld
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Rotation: Remove backup:domains/domain.tld/backup_domain.tld_info_1404151144.xml
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Delete backup domains/domain.tld/backup_domain.tld_info_1404151144.xml
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Get items 'dump' for discovered 'backup_domain.tld_info_1404151144' at path domains/domain.tld
[2014-04-15 12:14:26.217|15148] INFO: Repository '/var/lib/psa/dumps': Found 12 files for deleting
[2014-04-15 12:14:26.218|15148] INFO: Repository '/var/lib/psa/dumps': Rotate structured backups is finished for owner 10f1411b-72aa-414a-ac91-406812799e36
[2014-04-15 12:14:26.218|15148] INFO: pmm-ras finished. Exit code: 0
 
Last edited:
tail backup.log
[2014-04-14 23:49:25.091|16043] INFO: Repository '/var/lib/psa/dumps': Create item 'status_OK' for discovered 'backup_xyz.it_info_1404142335' at path domains/xyz.it
[2014-04-14 23:49:25.091|16043] INFO: Repository '/var/lib/psa/dumps': Put info to domains/xyz.it/.discovered/backup_xyz.it_info_1404142335/status_OK
[2014-04-14 23:49:25.091|16043] INFO: Repository '/var/lib/psa/dumps': Get all child backups for domains/xyz.it/backup_xyz.it_info_1404142335.xml
[2014-04-14 23:49:25.212|16043] INFO: pmm-ras finished. Exit code: 0
[2014-04-14 23:49:25.235|16046] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --rotate-dump --dump-rotation=5 --guid=c80b8165-eb2e-4654-8b64-6d223fa2b771 --dump-specification=backup_xyz.it_info_1404142335.xml --dump-storage=/var/lib/psa/dumps --storage-structured --session-path=/usr/local/psa/PMM/sessions/2014-04-14-233526.515 --verbose
[2014-04-14 23:49:25.235|16046] INFO: Repository '/var/lib/psa/dumps': Initializing...
[2014-04-14 23:49:25.235|16046] INFO: Repository '/var/lib/psa/dumps': Initialized
[2014-04-14 23:49:25.235|16046] INFO: Repository '/var/lib/psa/dumps': Rotate structured backups is started for owner c80b8165-eb2e-4654-8b64-6d223fa2b771
[2014-04-14 23:49:25.236|16046] INFO: Repository '/var/lib/psa/dumps': The backup list is empty. Nothing to rotate.
[2014-04-14 23:49:25.236|16046] INFO: pmm-ras finished. Exit code: 0

but backups are 8

bye
 
it's looks like patch not applied properly

in your log:
--dump-specification=backup_xyz.it_info_1404142335.xml

but there should be path to xml file:
--dump-specification=domains/domain.tld/backup_domain.tld_info_1404151214.xml
 
it's looks like patch not applied properly

in your log:
--dump-specification=backup_xyz.it_info_1404142335.xml

but there should be path to xml file:
--dump-specification=domains/domain.tld/backup_domain.tld_info_1404151214.xml


In my logfiles i see the same problem.
OS: Ubuntu 12.04.4 LTS
Plesk: 11.5.30 Update #39

UPDATE: Plesk: 11.5.30 Update #41 still the same
 
Last edited:
Status
Not open for further replies.
Back
Top