It would be nice to have a WITH option for the BACKUP command that allows us to suppress informational messages. If the backup works fine, there is no reason.
The problem I'm specifically having is that I have a job which backs up 40 databases in one step, and when there are failures, because the SQL Agent log only keeps about 1024 characters per step, this means that unless an error happens on the very first database, I do not see the reason the step failed, since it is pushed down the stack by all the "10 percent complete" nonsense, which is pretty useless when not called directly from Management Studio, since I am not actively monitoring the output when Backup Database is called from my job or a maintenance plan.
The problem varies slightly with the database name, e.g. if you named your databases "x" and "y" you might see some details for the second database, but I doubt it.
This will also help performance as the system can prevent all that I/O at each intreval, success messages, etc.