• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Backup error, how to know the problem ?

N

nima

Guest
Hi,
I configured some domains to backup automatically but some works and other don't. I have the followin message, sent by mail, about the backup :

****************************************************************************
* *
* ATTENTION: DUMP PROCEDURE HAS BEEN ABORTED, BECAUSE AN ERROR OCCURED! *
* *
* Using the dump file for restoration is dangerous !!! *
* *
****************************************************************************

How can I have more informations about this error ? any log somewhere ?

Thanks,
Nicolas.
 
See if you have a log file at:

/var/lib/psa/dumps/yourdomain.com/backup_restore.err_log

or do a search for the file.
 
Hi,

I have the same problem with some domain names.

I post the content of the backup logs:

backup_restore.log

START LOGGING: Tue Nov 08 04:30:22

Postgres is not configured: all postgres databases will not be dumped.

===============================================================================

Making backup to STDOUT ...
===============================================================================



****************************************************************************
* *
* ATTENTION: DUMP PROCEDURE HAS BEEN ABORTED, BECAUSE AN ERROR OCCURED! *
* *
* Using the dump file for restoration is dangerous !!! *
* *
****************************************************************************


Single domain backup is successfully completed


backup_restore.err_log

[EMPTY]

It seems the error log has not logged any error.

What can I do?

Many thanks! :)
 
I solved the problem, but I don't know what really caused it.
I scheduled the backup cron one hour later in order that it begin after other backup crons were finished and now it works fine...
 
Back
Top