<?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"
	>
<channel>
	<title>Comments on: Using NTBACKUP  to recover from system failure in Exchange 2003</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/using-ntbackup-to-recover-from-system-failure-in-exchange-2003/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/using-ntbackup-to-recover-from-system-failure-in-exchange-2003/</link>
	<description></description>
	<pubDate>Sun, 29 Nov 2009 09:41:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Shestopalov</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/using-ntbackup-to-recover-from-system-failure-in-exchange-2003/#comment-59567</link>
		<dc:creator>Shestopalov</dc:creator>
		<pubDate>Sat, 31 Jan 2009 00:05:56 +0000</pubDate>
		<guid isPermaLink="false">#comment-59567</guid>
		<description>What I remember from running a backup of the Exchange Server and database you cant do it unless the database is not running, or run a shadow copy, otherwise when you restore from backup your database will be corrupt. Am I correct? We currently use Symantec Auto Exec and it seems to work, but we havent tested the actual back ups yet.</description>
		<content:encoded><![CDATA[<p>What I remember from running a backup of the Exchange Server and database you cant do it unless the database is not running, or run a shadow copy, otherwise when you restore from backup your database will be corrupt. Am I correct? We currently use Symantec Auto Exec and it seems to work, but we havent tested the actual back ups yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wrobinson</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/using-ntbackup-to-recover-from-system-failure-in-exchange-2003/#comment-56235</link>
		<dc:creator>Wrobinson</dc:creator>
		<pubDate>Mon, 08 Sep 2008 16:23:57 +0000</pubDate>
		<guid isPermaLink="false">#comment-56235</guid>
		<description>The answer above contains a lot of useful information but I think that we can get to a much quicker answer based on the problem as described.

There is more to restoring a server from backup in a disaster recovery scenario, than simply restoring the system state. You also need to backup all of the files and folders on the server. This can be accomplished by performing a full or copy backup.

To restore the Exchange Server, you need to backup the Exchange inforamtion store. This allows you to take an online backup, as opposed to having to stop and start the services to take an offline backup. This can be accomplished using NTBACKUP.

Alternatively, it is possible to restore an Exchange Server only. This requires that Exchange Server be installed and the default database and log files removed. Then restore the Exchange information store to the new server; make sure it is at the same service pack and patch level and you should be off and running. You may need to perform some light maintenance and troubleshooting of the database but it can be done.</description>
		<content:encoded><![CDATA[<p>The answer above contains a lot of useful information but I think that we can get to a much quicker answer based on the problem as described.</p>
<p>There is more to restoring a server from backup in a disaster recovery scenario, than simply restoring the system state. You also need to backup all of the files and folders on the server. This can be accomplished by performing a full or copy backup.</p>
<p>To restore the Exchange Server, you need to backup the Exchange inforamtion store. This allows you to take an online backup, as opposed to having to stop and start the services to take an offline backup. This can be accomplished using NTBACKUP.</p>
<p>Alternatively, it is possible to restore an Exchange Server only. This requires that Exchange Server be installed and the default database and log files removed. Then restore the Exchange information store to the new server; make sure it is at the same service pack and patch level and you should be off and running. You may need to perform some light maintenance and troubleshooting of the database but it can be done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->