Minimum disk space check

[Nicholas West]

I've run into a client's cPanel server which runs automated backups in WHM, where the minimum disk space check is run after backups are made. What this causes is a backup failure email to be sent and no backup success message gets sent. This indicates to the client that their backups did not run successfully.

Is the minimum disk space check supposed to be done after the backups are made?

 

[cPanelLauren]

That check should be performed prior to the backups completing, doesn't make any sense for it to be completed after the backup process completes. What makes you believe this is occurring, any log entries/information you have would be helpful.

 

[Nicholas West]

This system is running cPanel version 86 ->

/usr/local/cpanel/cpanel -V
86.0 (build 18)

Here's the latest logs ( the actual cPanel username has been swapped ):

[2020-04-13 02:08:15 -0700] pkgacctfile is: /backup/2020-04-13/accounts/cpaneluser.tar.gz
[2020-04-13 02:08:15 -0700]
[2020-04-13 02:08:15 -0700] size is: 13867998977
[2020-04-13 02:08:15 -0700]
[2020-04-13 02:08:15 -0700] homesize is: 32587988992
[2020-04-13 02:08:15 -0700]
[2020-04-13 02:08:15 -0700] homefiles is: 299114
[2020-04-13 02:08:15 -0700] pkgacct completed
[2020-04-13 02:08:15 -0700] info [backup] Successfully backed up account “cpaneluser” to “/backup/2020-04-13/accounts”
[2020-04-13 02:08:15 -0700] info [backup] Adding metadata information for cpaneluser to backup at /backup/2020-04-13
[2020-04-13 02:08:15 -0700] warn [backup] Available disk space (9 percent) is too low. Backups will not run. at /usr/local/cpanel/bin/backup line 1286.
        bin::backup::enough_disk_space("/backup") called at /usr/local/cpanel/bin/backup line 1736
        bin::backup::backup_accounts("/backup/2020-04-13/accounts") called at /usr/local/cpanel/bin/backup line 920
        bin::backup::__ANON__() called at /usr/local/cpanel/bin/backup line 927
        bin::backup::__ANON__() called at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/cpanel_lib/Try/Tiny.pm line 97
        eval {...} called at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/cpanel_lib/Try/Tiny.pm line 88
        Try::Tiny::try(CODE(0x2d0eef0), Try::Tiny::Catch=REF(0x2d3a5a0)) called at /usr/local/cpanel/bin/backup line 937
        bin::backup::_process_backups(HASH(0x2bb0300)) called at /usr/local/cpanel/bin/backup line 381
        bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 120
[2020-04-13 02:08:15 -0700] info [backup] Pruning backup directory: /backup/2020-04-12
[2020-04-13 02:08:15 -0700] info [backup] Queuing prune operation for remote destination daily backups
[2020-04-13 02:08:15 -0700] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:97
[2020-04-13 02:08:19 -0700] info [backup] leaving queue_backup_transport_item
[2020-04-13 02:08:19 -0700] info [backup] Scheduling backup metadata vacuum
[2020-04-13 02:08:19 -0700] info [backup] Queuing transport reporter
[2020-04-13 02:08:19 -0700] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:98
[2020-04-13 02:08:19 -0700] info [backup] leaving queue_backup_transport_item
[2020-04-13 02:08:19 -0700] info [backup] Completed at Mon Apr 13 02:08:19 2020

The system has 71GB of space to use. When a backup is made, it consumes ~14GB. There is currently 20GB of free space, or about 28% disk free. There is also a copy of last night's backup on the server.

WHM backups are configured to make daily backups, retain just 1, and the minimum disk space check is set to 17%.

Backups are running just fine everyday, it's just that the backup success email notification is not getting sent because it seems the minimum disk space check is run after backups are made.

 

[cPanelLauren]

Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.


Thanks!

 

[Nicholas West]

Sounds good -> "Your Support Ticket ID is: 93476270"

 

[cPanelLauren]

Great! I'm following that ticket and I'll try and update here with the outcome as soon as it's available.