Description of problem: When running a script in cron mode, it's normally expected that the script is silent, unless something unusual or noteworthy happens along the way. Some scripts behave like this by default; some scripts need a "--quiet" or "--silent" argument for this behavior. The "engine-backup" tool does not currently seem to have a cron-friendly mode of operation. I request that a "--quiet" argument be added to the tool, making it work quietly, unless something unusual happens.
Makes sense, does not seem high priority. Patches are welcome :-) A workaround: Run it with > /dev/null. If there is an error, it will be written to stderr, so you should get mail, at least by most sane cronds, and the log ('--log=') should usually be enough to debug the error. Or run it with > /some/place/engine-backup-stdout.log, and have the same behavior, plus the extra theoretical info written to stdout and not to the log (if you find such, please open a bug), and plus the need to rotate the generated log.
Yes, it's a minor thing. By the way: Now that oVirt warns about lack of recent backups, maybe it should have a standard directory for backups and a default scheduled (nightly) backup-dump. That would leave one less task for the end-user to remember.
Closing old RFEs, please reopen if still needed. Patches are always welcome.