<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Email archiving software features &#8211; technical considerations</title>
	<atom:link href="http://4sysops.com/archives/email-archiving-software-features-technical-considerations/feed/" rel="self" type="application/rss+xml" />
	<link>http://4sysops.com/archives/email-archiving-software-features-technical-considerations/</link>
	<description>For Windows Administrators</description>
	<lastBuildDate>Fri, 19 Mar 2010 19:02:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Walter</title>
		<link>http://4sysops.com/archives/email-archiving-software-features-technical-considerations/comment-page-1/#comment-137160</link>
		<dc:creator>Walter</dc:creator>
		<pubDate>Thu, 08 Oct 2009 20:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=1686#comment-137160</guid>
		<description>I recently had an conversation with a few of my Agency&#039;s Microsoft Knowledge Exports and Technical Account Managers.  They advised that we should consider requiring a solution that utilizes Exchange backup and recovery APIs as opposed to custom database injections that enable a third party EAS solution to backup/recover Exchange data because it increases the liklihood of corrupt Exchange database.  Does anyone have any insight to this and why or why not this should be something we require?</description>
		<content:encoded><![CDATA[<p>I recently had an conversation with a few of my Agency&#8217;s Microsoft Knowledge Exports and Technical Account Managers.  They advised that we should consider requiring a solution that utilizes Exchange backup and recovery APIs as opposed to custom database injections that enable a third party EAS solution to backup/recover Exchange data because it increases the liklihood of corrupt Exchange database.  Does anyone have any insight to this and why or why not this should be something we require?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
