• 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!
  • 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.

Resolved Plesk scheduled backups disappear on a renamed subscription

Franco

Regular Pleskian
Hello,
this is quite a weird one and not easy to describe.
I run daily plesk full backups on each of my subscriptions (at different times in order not to create resource usage peaks) and they all run fine except for one. Maybe that has nothing to do but that particular subscription was renamed at some point from abc.com to abc.be.

i checked in the logs the both backup.log and pmmcli.log exist and say all is ok, including the creation of files of the kind domains/abc.be/backup_info_1711100610.xml etc. No error, exit code: 0.
I do not use ftp transfer, but they are stored locally on /var/lib/psa/dumps and I keep 10 of them.

One hint: manual backups are regularly created, but they disappear the day after (or a few hours later, not sure).

I am on CentOs 7.4 latest and Onyx 17.5.3 latest MU 27.
Any idea, please?

Regards
Franco
 
Well, I think I found the reason: the initial domain backups are not removed over time and they consitute the quota (which is fine). However, the new domain backups get added and if the quota is reached they get removed as soon as added instead of removing the older backups on the original domain. I think this is a bug or at least not a correct behaviour. I mark it solved because getting rid (manually) of those olrder backups has restarted the normal behavior; however, i think this should be analyzed by the Plesk developers, in my opinion. Relying on your backup setup and finding our later - when in need - that your backups are obsolete can be a dramatic scenario.

Regards

Franco
 
Back
Top