<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MS SQL 2008 failover between sites in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/MS-SQL-2008-failover-between-sites/m-p/57778#M8234</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am still very keen to hear other people's thoughts, yet in the particular case I am working on, this method was selected:&lt;/P&gt;&lt;P&gt;- Virtualising SQL &amp;amp; utilising SMSQL + SnapMirror + VMware SRM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reasons:&lt;/P&gt;&lt;P&gt;- can be fully automated (only the actual fail-over decision requires human intervention)&lt;/P&gt;&lt;P&gt;- easy testing&lt;/P&gt;&lt;P&gt;- can cover multiple (virtualised) applications&lt;/P&gt;&lt;P&gt;- well documented&lt;/P&gt;&lt;P&gt;- fairly popular, people with required skills available&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Sep 2011 09:50:05 GMT</pubDate>
    <dc:creator>radek_kubka</dc:creator>
    <dc:date>2011-09-06T09:50:05Z</dc:date>
    <item>
      <title>MS SQL 2008 failover between sites</title>
      <link>https://community.netapp.com/t5/Data-Protection/MS-SQL-2008-failover-between-sites/m-p/57774#M8233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering what your experience / recommendations are re protecting MS SQL 2008 against site-level outages? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the particular case I am looking at, the links between sites are decent (low latency, high bandwidth), yet not good enough for MetroCluster. The fail-over process itself not necessarily has to be fully automated, yet it should be easy to accomplish, ideally without custom scripting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So this is my list of different technologies, both NetApp-specific &amp;amp; storage agnostic:&lt;/P&gt;&lt;P&gt;- Native SQL database mirroring in High Availability mode - although sports an automated fail-over, I was always under impression the client application has to be written with the fail-over 'awareness' in mind, or it plainly won't be automated&lt;/P&gt;&lt;P&gt;- SMSQL + SnapMirror - fail-over requires either multiple steps, or scripting (unless I am missing something)&lt;/P&gt;&lt;P&gt;- SMSQL + SnapMirror + Veritas Cluster - as per TR-3713; looks like exactly what I am looking for, yet it's not tremendously popular, is it? Does anyone knows whether it works / is docummented for SQL 2008?&lt;/P&gt;&lt;P&gt;- Virtualising SQL &amp;amp; utilising SMSQL + SnapMirror + VMware SRM - probably my preferred one, due to e.g. having one methodology for protecting multiple systems&lt;/P&gt;&lt;P&gt;- Neverfail - I am somewhat skeptical about reliability of this product, but happy to listen to others whose experience is different&lt;/P&gt;&lt;P&gt;- SnapProtect - can the fail-over be any simpler than in the case of SMSQL?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Opinions? Any other approaches not listed above?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:50:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/MS-SQL-2008-failover-between-sites/m-p/57774#M8233</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2025-06-05T06:50:22Z</dc:date>
    </item>
    <item>
      <title>MS SQL 2008 failover between sites</title>
      <link>https://community.netapp.com/t5/Data-Protection/MS-SQL-2008-failover-between-sites/m-p/57778#M8234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am still very keen to hear other people's thoughts, yet in the particular case I am working on, this method was selected:&lt;/P&gt;&lt;P&gt;- Virtualising SQL &amp;amp; utilising SMSQL + SnapMirror + VMware SRM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reasons:&lt;/P&gt;&lt;P&gt;- can be fully automated (only the actual fail-over decision requires human intervention)&lt;/P&gt;&lt;P&gt;- easy testing&lt;/P&gt;&lt;P&gt;- can cover multiple (virtualised) applications&lt;/P&gt;&lt;P&gt;- well documented&lt;/P&gt;&lt;P&gt;- fairly popular, people with required skills available&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 09:50:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/MS-SQL-2008-failover-between-sites/m-p/57778#M8234</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2011-09-06T09:50:05Z</dc:date>
    </item>
  </channel>
</rss>

