Alt to getting email ...
IF you can, redirect to a log file which is not part of logging system and will be over-written each run of cron.
Rather than:
/usr/local/bin/ea-php73 /domain_path/admin/cli/automated_backups.php >/dev/null 2>&1
in domain path ... touch moodle-cron.log
Then
/usr/local/bin/ea-php73 /domain_path/admin/cli/automated_backups.php > /path/to/moodle-cron.log
Can than watch that log in realtime using:
tail -f /path/to/moodle-cron.log
Auto might be failing ... so check contents of moodledata/temp/backup/ ... successful backups leave only a 0 byte log file. Any .log file larger than 0 bytes failed for some reason - looking at the .log file not really helpful.
Depending upon the size of the backups, could be the very last step ... that of copying the auto .mbz file to destination. Evidence of that ... in moodledata/temp/backup/ you see long directory names ... bunch of letters/numbers. Inside there you do find a backup.mbz file. That's a valid/good backup, just couldn't be copied to destination.
'SoS', Ken