<?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>Blog O' Matty &#187; Veritas Volume Manager</title>
	<atom:link href="http://prefetch.net/blog/index.php/category/veritas-volume-manager/feed/" rel="self" type="application/rss+xml" />
	<link>http://prefetch.net/blog</link>
	<description>Blog O' Matty</description>
	<lastBuildDate>Wed, 16 May 2012 00:16:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Resizing Veritas volumes with vxresize</title>
		<link>http://prefetch.net/blog/index.php/2007/04/14/resizing-veritas-volumes-with-vxresize/</link>
		<comments>http://prefetch.net/blog/index.php/2007/04/14/resizing-veritas-volumes-with-vxresize/#comments</comments>
		<pubDate>Sat, 14 Apr 2007 18:56:21 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas File System]]></category>
		<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/04/14/resizing-veritas-volumes-with-vxresize/</guid>
		<description><![CDATA[We were getting close to running out of space on one of our database volumes last week, and I needed to add some additional storage to ensure that things kept running smoothly. The admin who originally created the VxVM database volume only used half of each of the five disks that were associated with the [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/04/14/resizing-veritas-volumes-with-vxresize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Removing duplicate devices from vxdisk list</title>
		<link>http://prefetch.net/blog/index.php/2007/03/17/removing-duplicate-devices-from-the-vxdisk-output/</link>
		<comments>http://prefetch.net/blog/index.php/2007/03/17/removing-duplicate-devices-from-the-vxdisk-output/#comments</comments>
		<pubDate>Sat, 17 Mar 2007 14:33:26 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/03/17/removing-duplicate-devices-from-the-vxdisk-output/</guid>
		<description><![CDATA[I replaced a disk in one of our A5200s last week, and noticed that vxdisk was displaying two entries for the device once I replaced it with vxdiskadm: $ vxdisk list DEVICE TYPE DISK GROUP STATUS c7t21d0s2 sliced disk01 oradg online c7t22d0s2 sliced disk02 oradg error c7t22d0s2 sliced - - error c7t23d0s2 sliced disk03 oradg [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/03/17/removing-duplicate-devices-from-the-vxdisk-output/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Recreating Veritas configurations with vxmake</title>
		<link>http://prefetch.net/blog/index.php/2006/11/19/recreating-veritas-configurations-with-vxmake/</link>
		<comments>http://prefetch.net/blog/index.php/2006/11/19/recreating-veritas-configurations-with-vxmake/#comments</comments>
		<pubDate>Sun, 19 Nov 2006 18:42:17 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/11/19/recreating-veritas-configurations-with-vxmake/</guid>
		<description><![CDATA[Last year I wrote an article titled Veritas Volume Manager Recovery Features for SysAdmin magazine. In the article I described how to backup a Veritas configuration to a file with vxconfigbackup, and how to restore it with vxconfigrestore. One thing I didn&#8217;t touch on was selectively restoring individual volume configurations. This is easy to do, [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/11/19/recreating-veritas-configurations-with-vxmake/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tracing vxassist activity</title>
		<link>http://prefetch.net/blog/index.php/2006/11/08/tracing-vxassist-activity/</link>
		<comments>http://prefetch.net/blog/index.php/2006/11/08/tracing-vxassist-activity/#comments</comments>
		<pubDate>Wed, 08 Nov 2006 13:22:48 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/11/08/tracing-vxassist-activity/</guid>
		<description><![CDATA[While creating a few Veritas volumes last week, I wanted to see the commands that vxassist was executing under the covers. This was easily accomplished by adding the &#8220;-v&#8221; (trace commands executed by vxassist) option to the vxassist command line: $ vxassist -b -v make datavol02 1g layout=mirror mirror=3 /usr/sbin/vxvol -g datadg -o bg -o [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/11/08/tracing-vxassist-activity/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Using Veritas Volume Manager with RHAS 4.0</title>
		<link>http://prefetch.net/blog/index.php/2006/08/30/using-veritas-volume-manager-with-rhas-40/</link>
		<comments>http://prefetch.net/blog/index.php/2006/08/30/using-veritas-volume-manager-with-rhas-40/#comments</comments>
		<pubDate>Wed, 30 Aug 2006 04:00:32 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/08/30/using-veritas-volume-manager-with-rhas-40/</guid>
		<description><![CDATA[I have used Veritas Volume Manager (VxVM) and Veritas File system (VxFS) for as long as I can remember. All of my VxVM and VxFS experience has been on Solaris, so I thought I would install both products on a Linux host to see if anything was different. The Linux installation turned out to be [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/08/30/using-veritas-volume-manager-with-rhas-40/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Creating a Veritas Volume Manager volume from a plex</title>
		<link>http://prefetch.net/blog/index.php/2006/05/17/building-volumes-from-plexes/</link>
		<comments>http://prefetch.net/blog/index.php/2006/05/17/building-volumes-from-plexes/#comments</comments>
		<pubDate>Wed, 17 May 2006 14:35:36 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=239</guid>
		<description><![CDATA[While cleaning up my Veritas VxVM notes this week, I came across one of my cheat sheets for creating volumes from plexes. This can be useful when you want to perform an offline backup of the data on an alternate server, or when you want to grab a spare copy of data prior to performing [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/05/17/building-volumes-from-plexes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adding mirrors to Veritas Volume Manager volumes</title>
		<link>http://prefetch.net/blog/index.php/2005/11/03/adding-a-mirror-to-a-volume-with-veritas-volume-manager/</link>
		<comments>http://prefetch.net/blog/index.php/2005/11/03/adding-a-mirror-to-a-volume-with-veritas-volume-manager/#comments</comments>
		<pubDate>Thu, 03 Nov 2005 23:11:24 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=251</guid>
		<description><![CDATA[One of the cool features of Veritas Volume Manager (VxVM) is it&#8217;s ability to change the layout of a volume on the fly with vxasssist(1m). This option has helped me numerous times, especially when I needed to mirror volumes that weren&#8217;t mirrored. Given the following unmirrored striped volume: $ vxprint -hft Disk group: oradg DG [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2005/11/03/adding-a-mirror-to-a-volume-with-veritas-volume-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting failure notifications with Veritas Volume Manager</title>
		<link>http://prefetch.net/blog/index.php/2005/10/29/getting-failure-notifications-with-veritas-volume-manager/</link>
		<comments>http://prefetch.net/blog/index.php/2005/10/29/getting-failure-notifications-with-veritas-volume-manager/#comments</comments>
		<pubDate>Sat, 29 Oct 2005 15:42:17 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=237</guid>
		<description><![CDATA[One of the cool and often overlooked features in Veritas Volume Manager is the failure notification mechanism. This facility provides automated notifications when problems are detected with Veritas managed disks, plexes, subdisks and volumes. These notifications are active by default, and will generate an e-mail to the user root each time a failure is detected. [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2005/10/29/getting-failure-notifications-with-veritas-volume-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Veritas Volume Manager (VxVM) Hot Spares</title>
		<link>http://prefetch.net/blog/index.php/2005/09/28/veritas-volume-manager-vxvm-hot-spares/</link>
		<comments>http://prefetch.net/blog/index.php/2005/09/28/veritas-volume-manager-vxvm-hot-spares/#comments</comments>
		<pubDate>Thu, 29 Sep 2005 03:54:30 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=164</guid>
		<description><![CDATA[When a disk fails that is part of a redundant volume (e.g., RAID 1, RAID 5), the volume is able to continue handling I/O requests, but becomes susceptible to data loss if additional devices fail ( and in the case of RAID5 volumes, the volume will operate in a degraded state, since parity calculations are [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2005/09/28/veritas-volume-manager-vxvm-hot-spares/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Reattaching to failed devices with Veritas Volume Manager</title>
		<link>http://prefetch.net/blog/index.php/2005/09/21/reattaching-failed-devices-with-veritas/</link>
		<comments>http://prefetch.net/blog/index.php/2005/09/21/reattaching-failed-devices-with-veritas/#comments</comments>
		<pubDate>Wed, 21 Sep 2005 19:21:09 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Veritas Volume Manager]]></category>

		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=137</guid>
		<description><![CDATA[When Veritas loses contact (e.g., if a fiber cable is removed between a server and a storage array) with an active device, Veritas will place the device in the failed state, which will be reported as &#8220;failed was: cXtXdX&#8221; in the vxdisk(1m) output: $ vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2005/09/21/reattaching-failed-devices-with-veritas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

