<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cbt on sigtar.com</title>
		<link>https://sigtar.com/tags/cbt/</link>
		<description>Recent content in Cbt on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Aug 2010 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/cbt/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>monitoring changed blocks (CBT) for replication of vmware virtual machines</title>
				<link>https://sigtar.com/2010/08/17/monitoring-changed-blocks-for-replication-of-vmware-virtual-machines/</link>
				<pubDate>Tue, 17 Aug 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/08/17/monitoring-changed-blocks-for-replication-of-vmware-virtual-machines/</guid>
				<description>&lt;p&gt;Check this link for a great script to monitor changes made to a virtual machine via the vmware CBT API. This is perfect for finding culprit machines that are generating a lot of replication traffic if you are replicating over a WAN.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/105-using-powershell-to-track-block-change-sizes-over-time&#34;&gt;http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/105-using-powershell-to-track-block-change-sizes-over-time&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you have some disks on a virtual machine you don&amp;rsquo;t want this script to capture then just set them as independent disks (so no snapshots can take place). This is handy if you have your windows page file on a separate disk that you don&amp;rsquo;t want to be measured as a part of the CBT changes.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
