• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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