Cron Output Says Backups Completed But They Didn't (Low Priority)

[dgerman]

No backup have been configured, however output from cronjob reports they have been successful.X-Powered-By: PHP/5.3.26Content-type: text/htmlAttempting to run all tasks for Auto Dealer Verification Services, LLC.

...

 

Attempting to backup the database to AmazonS3.The backup completed successfully.The AmazonS3 database backup task has completed.Attempting to backup the database via SFTP.The backup completed successfully.The SFTP database backup task has completed.

 

I wonder if no one ever sees that because they pipe crontab's output to /dev/null to avoid getting very frequent email. Perhaps something more sophisticated (like using sed to remove anything other than failure messages) than just discarding all the output is needed.

How do I know if the backup, after running previously, really fails?

[Tyson]

If you have no backups configured, then it did nothing, and success is the default response. If a backup was configured, and had failed, then you would have seen a message regarding the failure as opposed to "The backup completed successfully."

 

Perhaps the default response shouldn't be a success message, but rather more along the lines of "Nothing to do".

[Cody]

Moved to support forum as doesn't appear to be a bug.