<?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>Thrive Technology Solutions</title>
	<atom:link href="http://www.thrivetechnologysolutions.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thrivetechnologysolutions.com</link>
	<description>The trusted technical advisor your business needs to thrive.</description>
	<lastBuildDate>Sat, 11 Feb 2012 07:10:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>DR Planning: Risk Analysis</title>
		<link>http://www.thrivetechnologysolutions.com/2010/06/dr-planning-risk-analysis/</link>
		<comments>http://www.thrivetechnologysolutions.com/2010/06/dr-planning-risk-analysis/#comments</comments>
		<pubDate>Sat, 05 Jun 2010 14:35:59 +0000</pubDate>
		<dc:creator>Thrive</dc:creator>
				<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[DR]]></category>
		<category><![CDATA[DR Planning]]></category>

		<guid isPermaLink="false">http://www.thrivetechnologysolutions.com/?p=144</guid>
		<description><![CDATA[The first step in drafting a disaster recovery plan is conducting a thorough risk analysis of your computer systems. List all the possible risks that threaten system uptime and evaluate how imminent they are in your particular IT shop. Anything that can cause a system outage is a threat, from relatively common manmade threats like [...]]]></description>
			<content:encoded><![CDATA[<p>The first step in drafting a disaster recovery plan is conducting a  thorough risk analysis of your computer systems. List all the possible  risks that threaten system uptime and evaluate how imminent they are in  your particular IT shop. Anything that can cause a system outage is a  threat, from relatively common manmade threats like virus attacks and  accidental data deletions to more rare natural threats like floods and  fires. Determine which of your threats are the most likely to occur and  prioritize them using a simple system: rank each threat in two important  categories, probability and impact. In each category, rate the risks as  low, medium, or high.</p>
<p>For example, a small Internet company (less than 50 employees)  located in California could rate an earthquake threat as medium  probability and high impact, while the threat of utility failure due to a  power outage could rate high probability and high impact. So in this  company&#8217;s risk analysis, a power outage would be a higher risk than an  earthquake and would therefore be a higher priority in the disaster recovery plan.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thrivetechnologysolutions.com/2010/06/dr-planning-risk-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Patch management for virtualized servers</title>
		<link>http://www.thrivetechnologysolutions.com/2010/06/patch-management-for-virtualized-servers/</link>
		<comments>http://www.thrivetechnologysolutions.com/2010/06/patch-management-for-virtualized-servers/#comments</comments>
		<pubDate>Fri, 04 Jun 2010 05:35:17 +0000</pubDate>
		<dc:creator>Thrive</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[virtual]]></category>

		<guid isPermaLink="false">http://www.thrivetechnologysolutions.com/?p=141</guid>
		<description><![CDATA[Patch management of virtualized servers isn&#8217;t all that different with regular servers because each virtual operating system is its own independent virtual hard drive.  You still need a patch management system that patches all of your servers, but there may be interesting developments in the future where you may be able to patch multiple operating [...]]]></description>
			<content:encoded><![CDATA[<p>Patch management of virtualized servers isn&#8217;t all that different with  regular  servers because each virtual operating system is its own independent  virtual  hard drive.  You still need a patch management system that patches all  of  your servers, but there may be interesting developments in the future  where you  may be able to patch multiple operating systems at the same time if they  share  some common operating system or application binaries.  Ideally, you  would be  able to assign a patch level to an individual or a group of similar  servers.   For now, you will need to patch virtual operating systems as you would  any other  system, but there will be some innovations in the virtualization sector  that you  won&#8217;t be able to do with physical servers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thrivetechnologysolutions.com/2010/06/patch-management-for-virtualized-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

