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

FTP Backup Failure

NevilleM

New Pleskian
After I uploaded to Update #15, I started getting this error in the Backup Manager

Error:
Unable to rotate dump: The dump rotation is failed with code '151' at /usr/local/psa/admin/bin/plesk_agent_manager line 1224.
Error:
Unable to upload dump to FTP, it remains in server repository and you can manually download and upload it to FTP. Upload diagnostic message: Repository error: Destination directory 'ftp://111.111.111.111//pleskbackup/' does not exist

Any ideas on how to resolve this please?
 
When I posted this message I was on #16 and was still having the same problem.

However it seems to be ok now- it looks like the #16 did the trick!

Thanks
 
Upgraded, still ran into problems. Rebooted the server, reset up the backup and it ran under a manual start. I'll know by tomorrow if it did it's job. Been having issues with backup file rotation, and also it's having problems with files on a certain domain account where it can't stat some cache files.
 
Moved to "multi volume" setting and it seems to be working better instead of trying to move over a 20GB file every night. I'm using 2GB files now. Backup is not 100%, it needs some serious work by Plesk Team.
 
@SpyderZ

It seems to be the case that you are running out of disk space, when making the backup of that specific domain.

Just increase the disk space by using a proper mount OR change the DUMP_D variable in /etc/psa/psa.conf to point to a directory with enough space (restart sw-cp-server afterwards).

Regards....

PS In order to check whether a proper mount is present for the default backup directory (i.e. /var/lib/psa/dumps), just run the "df -h" command from a command line and verify that enough disk space is available.
 
Thanks, I have five times disk space to 100GB to the 20GB backup tgz that is produced.


@SpyderZ

It seems to be the case that you are running out of disk space, when making the backup of that specific domain.

Just increase the disk space by using a proper mount OR change the DUMP_D variable in /etc/psa/psa.conf to point to a directory with enough space (restart sw-cp-server afterwards).

Regards....

PS In order to check whether a proper mount is present for the default backup directory (i.e. /var/lib/psa/dumps), just run the "df -h" command from a command line and verify that enough disk space is available.
 
@SpyderZ

Given your response, it is not likely that a backup would fill up disk space, but it can be the case that disk mounts are not proper (i.e. mostly, but not only tmpfs related issues).

What are the settings on the FTP side (since we can exclude safely that server-side issues are present)?
 
Back
Top