sql - Log Shipping from Synchronous Automatic Failover AlwaysOn Availability Group AAG -


i have alwayson availability group running synchronous commit & automatic failover. example, connected sql01 nodes sql01a or sql01b.

i want make data available warehousing on server sql02, due high numbers of changes , high numbers of reads cannot use aag asynchronous commit gets behind , causes high waits.

because of have decided logship sql02 once daily. aag failing on between nodes sql01a & sql01b not sure on best practices around this.

i had set lsbackup,copy,restores sql01a. failed on sql01b , set up. jobs error on copy , restore, can add additional step onto each job check if primary copy or restore job , exit out if not, seems messy , feel missing something?

any advice appreciated.

for starters, change backup preference secondary , configure logshipping secondary.


Comments

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -