<?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>Running UNIX &#187; patching</title>
	<atom:link href="http://www.runningunix.com/tag/patching/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.runningunix.com</link>
	<description>UNIX/Solaris tips, tricks, and advice</description>
	<lastBuildDate>Sun, 25 Apr 2010 17:33:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sparse vs. Whole-root Zones patching times</title>
		<link>http://www.runningunix.com/2008/12/sparse-vs-whole-root-zones-patching-times/</link>
		<comments>http://www.runningunix.com/2008/12/sparse-vs-whole-root-zones-patching-times/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 21:23:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[patching]]></category>
		<category><![CDATA[sparse]]></category>
		<category><![CDATA[zones]]></category>

		<guid isPermaLink="false">http://www.cybersand.com/blog/?p=22</guid>
		<description><![CDATA[Someone had a question for me &#8211; does patching a sparse zone take less time than patching a whole-root zone? My first instinct was &#8220;yes&#8221;, because there would be much less data to copy into each zone, as some file systems like /usr are shared with the global zone. I decided to test both scenarios.
Here [...]]]></description>
			<content:encoded><![CDATA[<p>Someone had a question for me &#8211; does patching a sparse zone take less time than patching a whole-root zone? My first instinct was &#8220;yes&#8221;, because there would be much less data to copy into each zone, as some file systems like /usr are shared with the global zone. I decided to test both scenarios.</p>
<p>Here is the procedure I used:</p>
<p>Rebooted server to clear inode cache, memory pages, etc. With 3 whole-root zones installed, used PCA (http://www.par.univie.ac.at/solaris/pca/), and patched, adding 106 patches to the system. Rebooted, removed the zones and backed out the 106 patches. Rebooted and installed 3 sparse zones and performed the same patching again.</p>
<p>Patching whole-root zones: <strong>88 minutes to install 106 patches</strong></p>
<p>Patching sparse zones: <strong>72 minutes to install 106 patches</strong></p>
<p>Hmm not all that different. Not quite what I expected, but good to know.</p>
<p>Setup : SunFire V440, using all local disk/ SVM mirrored, 4GB RAM, Solaris 10 update 4, patching to the EIS May 2008 level.</p>
<p><strong>UPDATE:</strong> I patched the server without any zones also, and it took only <strong>30 minutes</strong>. My sub-par math tells me each sparse zone took 14 minutes to patch, and each whole root took 19 minutes.</p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.runningunix.com%2F2008%2F12%2Fsparse-vs-whole-root-zones-patching-times%2F&amp;linkname=Sparse%20vs.%20Whole-root%20Zones%20patching%20times"><img src="http://www.runningunix.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.runningunix.com/2008/12/sparse-vs-whole-root-zones-patching-times/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
