I'd also like to add our voice to this feature. We're using one of the more common architectures with multiple fast primary backup repositories holding 3 restore points and backup copy jobs sending data to onsite and offsite dedupe appliances. If the log backups aren't copied over, it means we have only ~3 days where we can do a point in time recovery. It also means if we lose the primary copy (host or datacenter failure), we have up to 24hrs of missing data.
Proposed methods of using File Copy jobs aren't practical with Per-VM chains and Scale-Out repos in v9. They also don't give us a solution to change compression levels so terrible with dedupe secondaries.
We're hoping this feature will make it into v9.5 (for MSSQL at least, Oracle would also be nice) as it will finally allow us to stop using TSM on top of Veeam. The only mention of this missing feature in the docs is under the Backup-to-tape section (https://helpcenter.veeam.com/backup/vsp ... begin.html
) so it's possible many don't know their logs aren't moving over (I'll admit, we just assumed they did).