I would like to know why clusterless AG in sql 2017 not a DR solution? Is there a reason that i am missing?
I am ok with async & no auto failover - It's like one type of mirroring option of old.
Pretty much if it came after db mirroring it would be a hit. mirroring + read_only secondaries is what I am seeing it as with no requirement of clustering. So if mirroring was a viable DR solution for so long than why isn't clusterless AG a DR solution.
I want to know as I would like to set it up & use for DR+read_only reporting copies.
I know all about AG etc, but it needs clustering and that is not a option on one of my apps so lets not get into AG & its advantages (ha, dr, grp failovers, listener, read-only routing etc etc.. i know) but my question pertains to one of my apps where i have a mixture of a clustered env & non windows clustering enabled server which needs to be used for reporting and i have tested that I am able to use clusterless ag there where i can add both env as replicas.
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-read-scale-availability-groups?view=sql-server-2017
we are good with:
- Forced manual failover with data loss
- Manual failover without data loss
Please don't reply about adv of AG, keep your answers to why read-scale AG is not a DR option, thanks.
D