SQL SERVER HIGH AVAILABILITY IDEA

Category: sql server multiservermgmt

Question

Jagdesh.dba on Fri, 09 Dec 2016 23:31:51


Hello guys,

I got a SQL Server setup in my company which is running on one Domain - I Need some high availability setup to make my database highly available on the SQL server running on the other domain , which Ideal Configuration is possible ?

Anyone can give me some sort of advise pls

Thanks 


Jay

Replies

Lin Leng on Mon, 12 Dec 2016 05:58:56


Hi Jagdesh.dba,

Your requirement is not quite clear to me, are you looking for a disaster recovery solution or something else? What’s the version of your SQL Server? What is your current SQL Server configuration? Here’s what I can think of at this moment:
1. Availability Group: It’s possible to create cross-domain availability group with SQL Server 2016/Windows Server 2016 as multi domain cluster/workgroup cluster was introduced in Windows Server 2016.
2. Log Shipping: Not exactly a high availability solution, but you could take this into consideration since you are in a cross-domain scenario.
3. Replication: You might need to use push subscription with SQL Authentication to make this work.
4. Database mirroring: I would probably go with database mirroring in this scenario. For more information, please review this thread.


If you have any other questions, please let me know.

Regards,
Lin

Jagdesh.dba on Thu, 15 Dec 2016 16:15:02


Hi,

How can i make a network share when you say the log-shipping is possible with cross domain?

Thanks 

Jay

Alex Bykovskyi on Mon, 19 Dec 2016 23:39:41


Hello Jagdess.dba,

I agree with Lin, it would be great to see a more information about your production. 

There are multiple options you can choose. 

As Lin mentioned you can go with Always On Availability Groups:
https://blogs.technet.microsoft.com/dataplatforminsider/2015/12/15/enhanced-always-on-availability-groups-in-sql-server-2016/ 

https://msdn.microsoft.com/en-us/library/ff878487.aspx?f=255&MSPPError=-2147217396

or Database Mirroring:

https://msdn.microsoft.com/en-us/library/ms189852.aspx

Lin Leng on Tue, 20 Dec 2016 02:00:21


Hi Jay,

>>How can I make a network share when you say the log-shipping is possible with cross domain?

Log shipping consists of three Jobs: LSBackup on the primary, LSCopy and LSRestore on the secondary. And there are two folders involved: backup destination and copy destination. The trick is, for cross-domain log shipping you just need to make sure the SQL Agent service account(or the account that LSCopy job is running under) have access on both folders and everything is fine.

And if you decide to use FTP to transfer backup files, here’s an example.


If you have any other questions, please let me know.

Regards,
Lin