Hey, did you ever get an answer to this? I am looking at rebuilding my whole SW environment with a FoE structure, and want to have two database servers that will be clustered alwayson. Can't seem to find much info on thwack or the kbase from SolarWinds on best practice settings or scenarios.
2 of 2 people found this helpful
Not on thwack but I did end up having to completely rebuild SW because of multiple crashes on the cluster which caused corruption. Giant pain!!
I did open a ticket with support and here is what they said. They do support always but highly recommend simple recovery mode opposed to full recovery mode. The problem is full recovery mode is required for always on so their support statement is contradictory.
I do have to say now that we are off always on our performance is way better.
Virtual SW server using NPM, NTA, NCM, UDT and IPAM
Virtual DB server with 12 GB of memory 4 V cpu
Virtual flow DB with 8 GB of ram
We manage about 120 interfaces and about 50 netflow sources
Wow! I am sorry to hear that you had such a @ssache with the AlwaysOn model. Thanks for the info! I will keep this in mind.
Is anyone out there using SQL AlwaysOn for HA successfully?
Is there a recommended migration path to move to SQL AlawaysOn from an existing single DB architecture? Or is it simply a matter of running the Config Wizard?