<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN"
 "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">

<channel>
<title>ExchangeRecovery.org</title>
<link>http://www.exchangerecovery.org</link>
<description>Exchange Data Recovery</description>
<language>en-us</language>

<item>
<title>Exchange Disaster Recovery after Hurricane</title>
<link>http://www.exchangerecovery.org/modules.php?name=News&amp;file=article&amp;sid=4</link>
<description>Hurricane Disaster Recovery Case Study &lt;br&gt;&lt;br&gt;
Scenario: &lt;br&gt;&lt;br&gt;
New Orleans accounting firm (requested anonymity) running Exchange 2000 Enterprise on a Dell Power Edge 4400 Server. EDB size 23GB aprox. 250 users. &lt;br&gt;&lt;br&gt;

The failure was at the RAID 5 level. The server shutdown and 2 out of 5 hard drives (78GB Seagate SCSI) failed. The Exchange server was backed up using Veritas and a Quantum tape library. The tapes were damaged by water. &lt;br&gt;&lt;br&gt;

The company is being temporarily housed by Regus in Houston. &lt;br&gt;&lt;br&gt;

&lt;a href=&quot;http://www.exchangerecovery.org/modules.php?name=News&amp;file=article&amp;sid=4&amp;mode=&amp;order=0&amp;thold=0&quot;&gt;Read The Resolutions&lt;/a&gt;</description>
</item>

<item>
<title>Transaction Logs as Backup</title>
<link>http://www.exchangerecovery.org/modules.php?name=News&amp;file=article&amp;sid=2</link>
<description>Microsoft&Acirc;&reg; Exchange Server transaction logging is a robust disaster recovery mechanism that is designed to reliably restore an Exchange database to a consistent state after any sudden stop of the database. The logging mechanism is also used when restoring online backups. &lt;br&gt;&lt;br&gt;
Before changes are actually made to an Exchange database file, Exchange writes the changes to a transaction log file. After a change has been safely logged, it can then be written to the database file.&lt;br&gt;It is common for changes to become available to end users just after the changes have been secured to the transaction log, but before they have been written to the database file. Exchange employs a sophisticated internal memory management system that is tuned for high performance. Physically writing out changes to the database file is a low-priority task during normal operation. Exchange can efficiently manage caching of more than a gigabyte of database pages. This cache includes pages read from the database to fulfill client requests, as well as changed pages that will eventually be written back to the database file.
&lt;br&gt;&lt;br&gt;&lt;b&gt;&lt;a href=&quot;modules.php?name=News&amp;file=article&amp;sid=2&amp;mode=&amp;order=0&amp;thold=0&quot;&gt;Read More....&lt;/a&gt;&lt;/b&gt;</description>
</item>

<item>
<title>Hard Drive Recovery Tips</title>
<link>http://www.exchangerecovery.org/modules.php?name=News&amp;file=article&amp;sid=1</link>
<description>What is data recovery? &lt;br&gt;&lt;br&gt;



Well there are 3 types of recovery:&lt;br&gt;





Logical Data Recovery - This type of recovery involves using software to
recover deleted files, virus damage or damage to the operating system. &lt;br&gt;

Non-Invasive Recovery - When the electronics on a drive fry for some reason
or another and the hard drive doesn't have to go into the clean room, its
non-invasive.&lt;br&gt;

Invasive Data Recovery - If any of the interior parts fail, usually the
heads, the drive has to be opened. Hard drives have to be opened in a clean
room, if even the smallest speck of dust gets into the heads the platters
can be damaged.&lt;br&gt;&lt;br&gt;&lt;b&gt;&lt;a href=&quot;modules.php?name=News&amp;file=article&amp;sid=1&amp;mode=&amp;order=0&amp;thold=0&quot;&gt;Read More...&lt;/a&gt;&lt;/b&gt;

</description>
</item>

</channel>
</rss>