When we backup an availability group e.g. two servers one active one in standby in the same Veeam job the active member SQL databases are backed up correctly but we always get VSS unfreeze errors on the standby member. Technically this is a Microsoft issue but Veeam seems to try and do a 'copy only' of the standby member and so initiates a VSS snapshot/freeze. I understood from this post in the forums:veeam-backup-replication-f2/backup-sql-always-on-2016-basic-availiblity-group-t40892.html
that there was a 'fix' for this in v10. All I'm asking is, given that a lot of stuff is being released in 9.5 U3 is this included?
I am assuming that all it does is avoid requesting VSS snapshots on the standby member once it has determined which one that is.