<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Replication on sigtar.com</title>
		<link>https://sigtar.com/tags/replication/</link>
		<description>Recent content in Replication on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Tue, 09 Nov 2010 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/replication/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Celerra - Unable to create, refresh, or delete checkpoint of a replicated destination file system</title>
				<link>https://sigtar.com/2010/11/09/celerra-unable-to-create-refresh-or-delete-checkpoint-of-a-replicated-destination-file-system/</link>
				<pubDate>Tue, 09 Nov 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/11/09/celerra-unable-to-create-refresh-or-delete-checkpoint-of-a-replicated-destination-file-system/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been stuck with this error recently on a Celerra manager device : DpRequest_Max_VS_SuspendedCheckpointsReached&lt;/p&gt;&#xA;&lt;p&gt;This can sometimes happen when a filesystem is held during a replication task. To check what filesystems are currently being replcated run the following command;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;nas_replicate -info -all&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Either wait until the replication has completed - check status. Or temporary stop the replication task (stop it from the source side if possible).&lt;/p&gt;</description>
			</item>
			<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>
			<item>
				<title>vmware srm - replicating over a wan - optimizations</title>
				<link>https://sigtar.com/2010/08/17/vmware-srm-replicating-over-a-wan-optimizations/</link>
				<pubDate>Tue, 17 Aug 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/08/17/vmware-srm-replicating-over-a-wan-optimizations/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been working through a SRM setup and have been looking at ways to optimize the amount of traffic that is sent over the WAN. The first obvious move is to move your vmware swap files off the replicated LUNS.&lt;/p&gt;&#xA;&lt;p&gt;Another way is to reduce the sync window. i.e. how often is yoru replication technology trying to keep the source and destination in sync? &amp;ndash; Increasing this window can sometimes help you out. But that all depends on your delta&amp;rsquo;s.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
