Automated backups stopped working

V

ViAdCk

Verified User
Joined
Feb 14, 2005
Messages
247
Hello,

I just found out that since about a month ago, on 2 of our servers the automated weekly backups configured in directadmin have stopped working. This also affects resellers that have automated backups configured. If the backups are executed manually they work just fine. Crond is working just fine on both these servers.

As it has happened around the same time on both servers I suspect this is a directadmin issue. I have checked the directadmin logs but couldn't find any relevant information.

Does anyone know what could be wrong and what to look for?

Thanks in advance!
 
Do you see any message in /var/log/directadmin/system.log about backup being run?
 
Hello. We also had this problem after updating to version 1.648. In the logs, backups were launched, but they were not created, and manual creation went without errors. We were helped by changing the task for backups. We just went into the task change and saved it without changes. After that, the task began to work. On some servers it was necessary to delete all jobs and set them up again, copying the jobs did not help.
 
I have installed a new server with directadmin and the same issue happens. Automated backups just stop working without any reason. When I save the backups again in directadmin it works for some time until it stops again.

Does anyone have any idea on where to look?
Regards
 
The backups are stored remotely on a backup server but the backup folder is configured as a local folder through nfs.

The issue is that the backup doesn't even start, there is no sign of it whatsoever in the system.log.
 
it works if you run this cron task from DA panel manually by "run now" ?
 
Zhenyapan said:
it works if you run this cron task from DA panel manually by "run now" ?
Click to expand...
Yes, it works fine if I run it manually and it also works during some days when I save the automated backup again. But mysteriously it stops working after some days.
 
what you see in cron logs and in directadmin logs - was it started failed days?
 
When backup runs correctly, the following shows in the directadmin system.log:

2025:04:24-02:00:12: Running Backup: type=admin owner=admin id=8
2025:04:24-02:25:54: Running Backup: type=admin owner=admin id=4

When the backup doesn't execute, nothing appears in the log.

I don't see any relevant information in /var/log/cron, both when the backup works and doesn't.
 
cron works before and after failed backup? i mean another cron tasks logged as successful? like 15min 1h before or after your planned backups?
 
You must log in or register to reply here.
Back
Top