Using Barcode recognizer for Software Control to read, scan read, scan image in Software applications.

The comprehensiveness of your plan will depend on your ability to be prepared for some or all of these events In the event that your backup strategy fails to provide you with the ability to restore your data, you should become familiar with the additional tools available to assist you in restoring service and repairing databases

Using Barcode generator for VS .NET Control to generate, create QR-Code image in VS .NET applications.

Earlier in the chapter, we reviewed procedures for recovering databases and mailboxes The tool that makes that process easier to accomplish is the Database Recovery Management (DRM) tool DRM is collection of tools you can use when you have to recover data DRM is a subset of a larger collection of tools called the Microsoft Exchange Server Performance Troubleshooting Assistant (ExTRA) tool as shown in Figure 18-7

Using Barcode generation for Java Control to generate, create barcode image in Java applications.

E-mail Continuity

DRM Task Analyze log drive space Repair database Show database related event logs Verify database and transaction log files Create a recovery storage group Merge or copy mailbox contents Mount or dismount the databases in the recovery storage group Remove the recovery storage group Set up Database can be overwritten by restore flag Swap databases for dial-tone scenario TABLE 18-2

Description Determines drive space issues for databases and log files Repairs corrupted databases Generates a report on database errors in the Application Event log Determines the reason why databases fail Also used to verify file availability for restore procedures Creates a recovery storage group for restoring mailbox data The RSG task that restores mailbox content This RSG task is necessary as the the RSG databases are not visible in the EMC You can use this tool to mount and dismount the recovered databases as well This RSG task removes the existing recovery storage group after restores are complete This is a mandatory step for production databases prior to a restore Empty databases added to the RSG will automatically have this value set Used to swap the temporary database with the recovered database The paths are changed, and the configuration information in AD is updated

DRM Task Descriptions

Database Troubleshooting Tool

The Database Troubleshooting Tool will analyze events generated by Exchange in the Application log related to the Mailbox and Public Folders databases It will attempt to do the following: Troubleshoot why the database will not mount Troubleshoot why the log files are inconsistent Troubleshoot why the log file generation has run out of numbers to name the log files Identify events that indicate low disk space on volumes containing Exchange databases and transaction logs

Extensible Storage Engine Utility

The Extensible Storage Engine Utility (Eseutilexe) is a low-level command-line tool used to maintain and in some cases repair Exchange database files (see Figure 18-8) When a database cannot be repaired by a restore from backup, it may be possible to repair it

18:

Backup, Restore, and Disaster Recovery

FIGURE 18-8

Eseutil

using Eseutil Eseutil is located in the Microsoft Exchange BIN directory (C:\ProgramFiles\ Microsoft\Exchange Server\BIN) Although this tool has traditionally been used to administer Mailbox and Public Folders databases, its scope of administration now includes the Hub Transport and Edge Transport server roles If multiple versions of Exchange coexist in your organization, you need to be cautious about which version of Eseutil you are using The Exchange 2007 version is not compatible with previous versions of Exchange Use the Exchange 2003 Eseutil to manage and repair 2000/2003 Exchange database files Offline defragmentation (Eseutil /D) is a common task that administrator use to optimize Exchange database performance Offline defragmentation and other optimization tasks are covered further in 20 Eseutil /D is also used as part of the database repair procedure to create a stable database after the repair procedure is complete A repaired database will be considered consistent However, due to the nature of the repair process, it could be unreliable Eseutil scans the logical structure of the database tables and records If the logical structure is inconsistent with the physical data on the disk, Eseutil will attempt to repair the data If the repair fails, the logical reference to the data is removed from the database tree structure In other words, it makes the database consistent by removing the reference to the missing data A defragmentation will move all the consistent data to a new database and delete the original database, leaving a single consistent and reliable database Table 18-3 lists the various modes that Eseutil can run in and gives a brief description of each mode