"Veeam is not responsible for any problems encountered by making any of the suggested changes in these systems. Please refer to their respective support organizations for more detail on these settings."
These changes are not in accordance with best practice and if you have a customer in which it must be matched to the smallest detail perfectly , then that's not an option for this .
Fact is , the VSS snapshot to be backed up with the SQL nodes , causes a failover .
In Webinar Veeam to SQL Always On , you are advised to add all nodes to the backup and Veeam does the rest. This works so unfortunately not.
The Veeam colleague working on my Call #00916797, advised me to backup the secondary node . But in a failover scenario the customer had to switch the Node in the Job manualy again.
And that is really very impractical.
And to add, that the colleague has advised me to use Copy -only , but this is in contradiction statement to Alan Bolte .
I see here on this issue still many question marks. And it looks like they have not yet clarified internally at Veeam . It would therefore be very helpful, to have a official statement how best to proceed with SQL Always On .
@ anton gostev
you said that globaly there are no known issues, i can say that globaly there is no best practice to backup SQL Always On with Veeam ???