<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">The way we do it is to create a VM that
runs Windows and hosts the DB, so the OS nor the DB have to have
any concept that there's replication behind the scenes.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Exactly how we do is specific to our
platform (The Anvil), but in short we've got a custom RA for
pacemaker and management tools to create LVs per VM, and those LVs
become backing devices for a DRBD resource with 1 or more volumes.
The resource runs in single-primary except when we want to live
migrate, (all this is handled in our Pacemaker RA) then we enable
dual-primary, promote the target to primary, migrate, demote the
old host to Secondary and disable dual-primary support. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Of course, protection is provided via
IPMI fencing as the primary method with switched PDU fencing as a
backup. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I'm happy to go into more detail, but
I'll stop here until/unless you have more questions. Otherwise I'd
write a book. :)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Madi<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2022-09-27 15:42, Eric Robinson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:MW4PR03MB6507AC054253D40A2400CF6EFA559@MW4PR03MB6507.namprd03.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi Madi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It sounds like you’ve had a lot of good
experience. I’m trying to decide between paying a premium
price for MSSQL Enterprise with Always-On Replication or just
setting up an Active/Standby scenario with the Standard
Edition of MSSQL running on DRBD. We have tons of experience
with MySQL on DRBD, but not with MSSQL. When running MSSQL on
DRBD, what’s the cluster stack? How does failover work? When
using MySQL, the service only runs on one server at a time. In
a failover, the writable data volume transitions to the
standby server and then the MySQL service is started on it.
Does it work the same way with MSQL? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Eric<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Madison Kelly
<a class="moz-txt-link-rfc2396E" href="mailto:mkelly@alteeve.com"><mkelly@alteeve.com></a> <br>
<b>Sent:</b> Monday, September 26, 2022 7:55 PM<br>
<b>To:</b> Cluster Labs - All topics related to
open-source clustering welcomed
<a class="moz-txt-link-rfc2396E" href="mailto:users@clusterlabs.org"><users@clusterlabs.org></a>; Eric Robinson
<a class="moz-txt-link-rfc2396E" href="mailto:eric.robinson@psmnv.com"><eric.robinson@psmnv.com></a><br>
<b>Subject:</b> Re: [ClusterLabs] DRBD and SQL Server<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2022-09-25 23:49, Eric Robinson
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hey list, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Anybody have experience running SQL
Server on DRBD? I’d ask this in the DRBD list but that one
is like a ghost town. This list is the next best option.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-Eric<o:p></o:p></p>
</blockquote>
<p>Extensively, yes. Albeit in VMs whose storage was backed by
DRBD, though for all practical purposes there's no real
difference. We've had clients running various DB servers for
over ten years spanning DRBD 8.3 through to the latest 9.1.<o:p></o:p></p>
<p>What's your question?<o:p></o:p></p>
<p>Madi<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Madison Kelly<o:p></o:p></pre>
<pre>Alteeve's Niche!<o:p></o:p></pre>
<pre>Chief Technical Officer<o:p></o:p></pre>
<pre>c: +1-647-471-0951<o:p></o:p></pre>
<pre><a href="https://alteeve.com/" moz-do-not-send="true" class="moz-txt-link-freetext">https://alteeve.com/</a><o:p></o:p></pre>
</div>
</div>
Disclaimer : This email and any files transmitted with it are
confidential and intended solely for intended recipients. If you
are not the named addressee you should not disseminate,
distribute, copy or alter this email. Any views or opinions
presented in this email are solely those of the author and might
not represent those of Physician Select Management. Warning:
Although Physician Select Management has taken reasonable
precautions to ensure no viruses are present in this email, the
company cannot accept responsibility for any loss or damage
arising from the use of this email or attachments.
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Madison Kelly
Alteeve's Niche!
Chief Technical Officer
c: +1-647-471-0951
<a class="moz-txt-link-freetext" href="https://alteeve.com/">https://alteeve.com/</a></pre>
</body>
</html>