<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Edwin M Sarmientoclustering &#8211; Edwin M Sarmiento</title>
	<atom:link href="https://www.edwinmsarmiento.com/category/clustering/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.edwinmsarmiento.com</link>
	<description>Intentional Excellence</description>
	<lastBuildDate>Mon, 13 Apr 2026 21:00:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">84283043</site>		<item>
		<title>Installing, Configuring and Managing Windows Server Failover Cluster using PowerShell Series</title>
		<link>https://www.edwinmsarmiento.com/installing-configuring-and-managing-windows-server-failover-cluster-using-powershell-series/</link>
		<comments>https://www.edwinmsarmiento.com/installing-configuring-and-managing-windows-server-failover-cluster-using-powershell-series/#respond</comments>
		<pubDate>Tue, 23 Sep 2014 14:18:47 +0000</pubDate>
		<dc:creator>Edwin M Sarmiento</dc:creator>
				<category><![CDATA[clustering]]></category>
		<category><![CDATA[High Availability]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Windows Cluster]]></category>
		<category><![CDATA[Windows PowerShell]]></category>
		<category><![CDATA[Windows Server Failover Clustering]]></category>
		<category><![CDATA[WSFC]]></category>
		<guid isPermaLink="false">http://bassplayerdoc.wordpress.com/?p=909</guid>

				<description><![CDATA[Last year, I started writing an article that was supposed to be a series for Installing, Configuring and Managing Windows Server Failover Cluster using Windows PowerShell. The first of the series came out on July 2013 (which ended up being the last article I wrote for the year 2013 on MSSQLTips.com.) Since then, I&#8217;ve been involved [&#8230;]]]></description>
					<content:encoded><![CDATA[<p>Last year, I started writing an article that was supposed to be a series for Installing, Configuring and Managing Windows Server Failover Cluster using Windows PowerShell. The <a href="http://www.mssqltips.com/sqlservertip/3001/installing-configuring-and-managing-windows-server-failover-clusters-using-powershell-part-1/" target="_blank">first</a> of the series came out on July 2013 (which ended up being the last article I wrote for the year 2013 on MSSQLTips.com.) Since then, I&#8217;ve been involved with more projects on SharePoint and business intelligence (BI) integration that I barely had a chance to work with the SQL Server database engine on a regular basis. But since part 1 of the series is already out there, I figured it&#8217;s worth the time and effort to finish it up. So, here it is &#8211; the complete series on Installing, Configuring and Managing Windows Server Failover Cluster using Windows PowerShell.</p>
<ul>
<li><a href="http://www.mssqltips.com/sqlservertip/3001/installing-configuring-and-managing-windows-server-failover-clusters-using-powershell-part-1/" target="_blank">Part 1</a> &#8211; from installing the feature to creating the Windows Server Failover Cluster</li>
<li><a href="http://www.mssqltips.com/sqlservertip/3325/installing,-configuring-and-managing-windows-server-failover-cluster-using-powershell-part-2/" target="_blank">Part 2</a> &#8211; retrieving and changing cluster object properties and adding clustered disks</li>
<li><a href="http://www.mssqltips.com/sqlservertip/3326/install-configure-and-manage-windows-server-failover-cluster-with-powershell--part-3/" target="_blank">Part 3</a> &#8211; managing permissions, changing parameter values, moving clustered resources and dependencies</li>
<li><a href="http://www.mssqltips.com/sqlservertip/3343/installing-configuring-and-managing-windows-server-failover-cluster-using-powershell-part-4/" target="_blank">Part 4</a> &#8211; common cluster troubleshooting tasks</li>
</ul>
<p>Enjoy!</p>
<h1></h1>
]]></content:encoded>
			

		<wfw:commentRss>https://www.edwinmsarmiento.com/installing-configuring-and-managing-windows-server-failover-cluster-using-powershell-series/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
				<post-id xmlns="com-wordpress:feed-additions:1">909</post-id>	</item>
		<item>
		<title>Reconfiguring your SQL Server disks &#8211; 2008 edition</title>
		<link>https://www.edwinmsarmiento.com/reconfiguring-your-sql-server-disks-2008-edition/</link>
		<comments>https://www.edwinmsarmiento.com/reconfiguring-your-sql-server-disks-2008-edition/#respond</comments>
		<pubDate>Sat, 07 Feb 2009 04:52:00 +0000</pubDate>
		<dc:creator>Edwin M Sarmiento</dc:creator>
				<category><![CDATA[clustering]]></category>
		<category><![CDATA[SQL Server 2008]]></category>
		<guid isPermaLink="false">http://bassplayerdoc.wordpress.com/2009/02/07/reconfiguring-your-sql-server-disks-2008-edition</guid>

				<description><![CDATA[This was from my old blog entry from way back November 2006 and remembered how easy it was to fool SQL Server when trying to replace disks. I was configuring a clustered SQL Server 2008 on a Windows Server 2008 and testing the disk resources for failover. I tried failing over one of the disks [&#8230;]]]></description>
					<content:encoded><![CDATA[<p><span style="font-family:arial;">This was from my old <a href="http://bassplayerdoc.spaces.live.com/blog/cns%21CED2A18FB2A30E11%21335.entry">blog entry</a> from way back November 2006 and remembered how easy it was to fool SQL Server when trying to replace disks. I was configuring a clustered SQL Server 2008 on a Windows Server 2008 and testing the disk resources for failover. I tried failing over one of the disks and it went out pretty well. The next disk resource that I failed over happened to be the one containing the system databases. To my surprise, it did not failover to the other node causing the SQL Server resource to fail as well. It took me quite a while figuring out that the disk subsystem is somehow corrupted (good thing it was just a test environment) so what I ended up doing was recreating a new disk subsystem and redefining it on my cluster using Failover Cluster Management. I made it available on my SQL Server 2008 resource. I knew I would definitely have downtime as I need to bring down the SQL Server cluster resource. Here&#8217;s what I did &#8211; I brought the SQL Server resource offline, copied the contents of the original disks that contain my system databases to the new disk resource, changed the drive letter of the original disk to something else and rebooted the node that originally hosted the disk resource that is failing. Once it is up, I can reuse the same drive letter to the new disk resource which now has the original system databases. When I brought te SQL Server resource back online, it&#8217;s as if nothing had happened (except, of course, for some errors in the Clustering error log).</span></p>
<p>Note that this is definitely not a substitute to a valid backup and restore process for your SQL Server databases. All I&#8217;m saying is it just works</p>
<div class="blogger-post-footer"><img decoding="async" src="" alt="" width="1" height="1" /></div>
]]></content:encoded>
			

		<wfw:commentRss>https://www.edwinmsarmiento.com/reconfiguring-your-sql-server-disks-2008-edition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
				<post-id xmlns="com-wordpress:feed-additions:1">153</post-id>	</item>
	</channel>
</rss>