Remarkably, Brian forgets to mention that this feature is available only in the Enterprise Edition SKU. I have to wonder why it's only available in EE; does it make sense that user have to pay for a substantially more expensive license to keep their data safe?
Why does the feature fail to write all backups if only one of the destinations fails? Doesn't that make the feature far less useful? Are there strategies for creating robust backups with SQL Server? That is, how does Brian recommend working around the limitation he identifies?