<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Replica disk threshold exceeded, or Recovery Point Volume threshold exceeded</title>
	<atom:link href="http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded//feed" rel="self" type="application/rss+xml" />
	<link>http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded/</link>
	<description>My place to speak about things</description>
	<lastBuildDate>Tue, 03 Jan 2012 21:30:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michael</title>
		<link>http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded//comment-page-1#comment-668</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 16 Sep 2011 12:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded/#comment-668</guid>
		<description>Essentially, all DPM is doing is looking at the used space for the Recovery Point Volume.  The only problem I have seen with this is when DPM 2007 had the issue where it wouldn&#039;t remove expired recovery points.  I posted about that here: http://nukeitmike.com/blog/2009/04/12/dpm-does-not-remove-expired-recovery-points/ and a follow up to that here: http://nukeitmike.com/blog/2009/08/07/follow-up-to-the-dpm-recovery-point-expiration-issues/

Hope this helps.</description>
		<content:encoded><![CDATA[<p>Essentially, all DPM is doing is looking at the used space for the Recovery Point Volume.  The only problem I have seen with this is when DPM 2007 had the issue where it wouldn&#8217;t remove expired recovery points.  I posted about that here: <a href="http://nukeitmike.com/blog/2009/04/12/dpm-does-not-remove-expired-recovery-points/" rel="nofollow">http://nukeitmike.com/blog/2009/04/12/dpm-does-not-remove-expired-recovery-points/</a> and a follow up to that here: <a href="http://nukeitmike.com/blog/2009/08/07/follow-up-to-the-dpm-recovery-point-expiration-issues/" rel="nofollow">http://nukeitmike.com/blog/2009/08/07/follow-up-to-the-dpm-recovery-point-expiration-issues/</a></p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Jordan</title>
		<link>http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded//comment-page-1#comment-667</link>
		<dc:creator>Dan Jordan</dc:creator>
		<pubDate>Thu, 15 Sep 2011 17:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded/#comment-667</guid>
		<description>Michael, Thanks for your response.  The part about the RPV having the potential to be many time the size of the replica volume is particularly helpful.  

Is the bottom line that the system internally calculates the 90% threshold and that DPM admins won&#039;t always have access to the figures the system used in that calculation?</description>
		<content:encoded><![CDATA[<p>Michael, Thanks for your response.  The part about the RPV having the potential to be many time the size of the replica volume is particularly helpful.  </p>
<p>Is the bottom line that the system internally calculates the 90% threshold and that DPM admins won&#8217;t always have access to the figures the system used in that calculation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded//comment-page-1#comment-666</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 15 Sep 2011 17:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded/#comment-666</guid>
		<description>Dan,

DPM creates two volumes for each protected item (database, VM, file share, etc).  The first volume is the Replca Volume.  This is where DPM stores the most recent recovery point view of the protected member.  The other volume is the Recovery Point Volume.  This is where the historical changes are saved.  Depending on what you are protecting, how long you are protecting it, how often you create recovery points, and how much data change there is between recovery points, the Recovery Point Volume can be many times the size of the Replica Volume.  In my experience, active Databases and System State are the most space consuming.  Large file servers tend to have much less churn.
Hope this helps.

Michael</description>
		<content:encoded><![CDATA[<p>Dan,</p>
<p>DPM creates two volumes for each protected item (database, VM, file share, etc).  The first volume is the Replca Volume.  This is where DPM stores the most recent recovery point view of the protected member.  The other volume is the Recovery Point Volume.  This is where the historical changes are saved.  Depending on what you are protecting, how long you are protecting it, how often you create recovery points, and how much data change there is between recovery points, the Recovery Point Volume can be many times the size of the Replica Volume.  In my experience, active Databases and System State are the most space consuming.  Large file servers tend to have much less churn.<br />
Hope this helps.</p>
<p>Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Jordan</title>
		<link>http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded//comment-page-1#comment-665</link>
		<dc:creator>Dan Jordan</dc:creator>
		<pubDate>Tue, 13 Sep 2011 17:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://nukeitmike.com/blog/2009/03/31/replica-disk-threshold-exceeded-or-recovery-point-volume-threshold-exceeded/#comment-665</guid>
		<description>I&#039;m familiar with the process of making the recovery point volume a little bigger, but sometimes I can&#039;t make sense of *what* has exceeded the 90% threshold.  For instance, right now my &quot;data size&quot; is 1.47GB, my &quot;Replica Volume&quot; is 1.85GB, and my &quot;Recovery Point Volume&quot; is 11.52GB, and yet it tells me to allocate more disk space for the *recovery point volume*.  Why?  What has &quot;exceeded the 90% threshold&quot;?  I want to understand how it is making this calculation.</description>
		<content:encoded><![CDATA[<p>I&#8217;m familiar with the process of making the recovery point volume a little bigger, but sometimes I can&#8217;t make sense of *what* has exceeded the 90% threshold.  For instance, right now my &#8220;data size&#8221; is 1.47GB, my &#8220;Replica Volume&#8221; is 1.85GB, and my &#8220;Recovery Point Volume&#8221; is 11.52GB, and yet it tells me to allocate more disk space for the *recovery point volume*.  Why?  What has &#8220;exceeded the 90% threshold&#8221;?  I want to understand how it is making this calculation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

