<?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>Backdrift &#187; iSCSI</title>
	<atom:link href="http://backdrift.org/tag/iscsi/feed" rel="self" type="application/rss+xml" />
	<link>http://backdrift.org</link>
	<description></description>
	<lastBuildDate>Tue, 15 Nov 2011 03:01:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Automounting iSCSI with Autofs</title>
		<link>http://backdrift.org/automounting-iscsi-with-autofs</link>
		<comments>http://backdrift.org/automounting-iscsi-with-autofs#comments</comments>
		<pubDate>Thu, 06 May 2010 04:12:17 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[autofs]]></category>
		<category><![CDATA[automount]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[equallogic]]></category>
		<category><![CDATA[ext3]]></category>
		<category><![CDATA[iSCSI]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=498</guid>
		<description><![CDATA[I use SAN snapshots extensively to provide point-in-time recoverability for a number of different systems. This is a very reliable and efficient backup solution but it comes at the cost of additional complexity for individual file restoration. This is because the snapshot backups are of the entire volume and not each individual file. So when [...]]]></description>
		<wfw:commentRss>http://backdrift.org/automounting-iscsi-with-autofs/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Xen block iSCSI script with multipath support</title>
		<link>http://backdrift.org/xen-block-iscsi-script-with-multipath-support</link>
		<comments>http://backdrift.org/xen-block-iscsi-script-with-multipath-support#comments</comments>
		<pubDate>Tue, 27 Oct 2009 20:34:19 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iSCSI]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Multipath]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=232</guid>
		<description><![CDATA[When connecting a server to a storage area network (SAN) its important to make certain that you&#8217;re hosts are prepared for the occasional blip in SAN connectivity. Device mapper multipath to the rescue! Multipath is an abstraction layer between you and the raw block devices which allows for multiple I/O paths or networks (IO multipathing) [...]]]></description>
		<wfw:commentRss>http://backdrift.org/xen-block-iscsi-script-with-multipath-support/feed</wfw:commentRss>
		<slash:comments>40</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  backdrift.org/tag/iscsi/feed ) in 0.66803 seconds, on Feb 5th, 2012 at 1:57 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 5th, 2012 at 2:57 pm UTC -->
