<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>DPM PowerShell Script -- invoking a Consistency Check</title><link>http://blogs.technet.com/b/dpm/archive/2008/04/10/dpm-powershell-script-invoking-a-consistency-check.aspx</link><description>By design, DPM 2007 should be &amp;#8216; fire and forget &amp;#8217; &amp;#8211; meaning that after initial replication, data changes will automatically and routinely replicate.&amp;#160; However, due to a variety of external factors, the data set may become inconsistent</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>DPM 2007 e il Consistency Check</title><link>http://blogs.technet.com/b/dpm/archive/2008/04/10/dpm-powershell-script-invoking-a-consistency-check.aspx#3065094</link><pubDate>Tue, 03 Jun 2008 03:13:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3065094</guid><dc:creator>$ClaudioG.Blog = $True</dc:creator><description>&lt;p&gt;Data Protection Manager 2007 prevede un meccanismo di verifica dell'integrit&amp;#224; di una Replica (un &amp;quot;backup&amp;quot;&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3065094" width="1" height="1"&gt;</description></item></channel></rss>