t cht lk
Choosing between ‘ 2 evils ’
Users of the new class of cloud-based Microsoft SQL Server need optimal remote data protection , which requires figuring out how to leverage the full power of SQL ’ s DR functionality and HA for local HA . But there ’ s been something preventing this until recently , a major obstacle with a serious impact on SQL Server . In order to use SQL Server on Linux for HA and DR together , IT needed to select between two ‘ evils ’, so to speak :
• Using a Pacemaker-based solution . For DR , this meant relying on virtual private networks ( VPNs ), with separate clusters for availability groups and HA instances .
• Using VPNs for DR and combining HA SQL Server instances with another solution for data replication . This would be needed whether replicating the full virtual machine , storage , blocklevel , etc .
As you might guess , the resulting implementationcobbling together SQL Server clustering for SQL Server AGs , Pacemaker and VPNs – is more like a suboptimal ‘ Frankenstein ’ effort . It lacks scalability , fails recovery time objective ( RTO ) and recovery point objective ( RPO ) requirements , and thanks to VPNs , has insufficient data security . This type of ‘ science project ’ is also quite expensive , making it unrealistic for many organizations .
A smarter use case
Rather than relying on the ‘ Frankenstein ’ method , a more effective solution is Smart Availability software , which runs on top of SQL Server . Here ’ s an example of what this might look like for a large fintech company , which initially considered using a SQL Server AG , Pacemaker clusters and direct network connections . This firm found the proposed architecture suffered from several problems :
• Complex , unreliable local HA and DR architecture
• Clunky cluster management because of the panoply of incompatible clustering technologies
• Challenges with RTO from long system outages due to manual failover management between clusters and data centers
• A costly infrastructure requiring continuous maintenance
Understandably disappointed with these results , the financial services company sought a superior solution and next implemented multi-platform Smart Availability SQL Server clustering software . The fintech company immediately enjoyed better uptime and quicker transaction processing . By leveraging Smart Availability SQL Server clustering software , the firm solved several pain points that made it the clear winner over the earlier use case : it increased the performance of SQL Server AGs , simplified SQL Server workload management , and responded to channel partners ’ and end customers ’ requirements for better database resilience from SQL Server .
This second use case also had the benefit of offering Zero Trust security and providing scalability across public and private clouds , and between remote and on-premises locations .
Last but not least , multi-platform Smart Availability SQL Server clustering software can help an organization that needs to combine remote data protection with local HA potentially chop its SQL Server costs in half .
In short , Smart Availability SQL Server clustering software eliminates the performance problems of traditional solutions , emerging as the clear winner when compared with VPN technologies .
There are many clear advantages to the software , from smart and simple HA and DR , to almost no downtime , workload portability , infrastructure freedom and cost savings . This single cluster setup creates the cyber-resiliency that enterprises need by offering simple system management , evergreen infrastructure compatibility , and standardized local HA and DR architecture . p
Don Boxley Jr , Co-founder and CEO of DH2i
www . intelligentcio . com INTELLIGENTCIO NORTH AMERICA 77