IBM DS8000, DS6000 manual Consistency Checks on Exchange Database and Log Files

Page 72

Consistency Checks on Exchange Database and Log Files

For an Exchange VSS backup, Microsoft requires that each database file (.edb, but not .stm) and each transaction log file required for the restore have a checksum consistency check run against the files. This consistency check is accomplished by running eseutil.exe with the proper options against the files which exist on the snapshot. For offhost backups, the consistency checks are run on the offhost server rather than on the Exchange Server. Off- loading the consistency check is recommended to further reduce the backup impact on production Exchange servers.

If any of the files fail the consistency check, the entire backup will fail, the backup image will be discarded, and the Exchange VSS Writer will be notified of the failure. When this occurs, Exchange will not truncate log files.

Failure of the consistency check may be an indication of either database corruption or a problem with the snapshot. The Exchange administrator should investigate the reason for the failure by dismounting the Exchange database which caused the failure, and running eseutil.exe against the database file to determine the cause of the corruption.

Best Practices for Exchange Storage and VSS Backups

The following are recommended configurations to prepare the Exchange environment for Backup Exec VSS operations.

•The volume(s) which contains the Exchange databases and log files should be dedicated to Exchange only. Other types of databases (e.g., SQL) should not reside on the volume(s). Only Exchange objects will be included in a snapshot backup.

•Disable circular logging for all Exchange Storage Groups.

•Transaction logs should reside on a different volume than where the Information Store resides.

•If you are running the integrity check, ESEUTIL throttling minimizes the impact on production LUNS during the VSS copy-on-write process. Although the current version of Backup Exec does not provide throttling, this is planned for a future release. It is also recommended to use the offhost feature to further minimize performance impacts.

•If you are planning on restoring individual mailbox messages or folders, you should ensure the backups are to disk, rather than tape. Granular restores from tape require staging of the data from tape to disk first, which impacts the restore times and the ability to meet SLA times.

Exchange 2003 VSS Backup Solution

Page 72

David West, David Hartman

For IBM Storage DS8000/DS6000

 

©Copyright IBM Corp. 2007

And Symantec Backup Exec 11d

 

 

Page 71 Page 73
Image 72
Page 71 Page 73
Contents Configuration and Best Practices Table of Contents Exchange Backup and Restore Disclaimer Importance of Exchange VSS Solutions Executive SummaryCost of Downtime Target EnvironmentIBM System Storage DS8000 Series IBM System Storage DS6000 Series Page Installing CIM Agent for Windows Installation Overview for Windows Installing the CIM Agent on Windows Launchpad Window Product Installation Check window IBM ESS CLI window Netstat -a Update Cimom Port window Verifying the CIM Agent Installation on Windows Close the Administrative Tools window Configuring the CIM Agent for Windows StepsProvider entry for IP 9.11.111.111 successfully added Page \Program Files\IBM\cimagent Configuring the CIM Agent to run in Unsecure Mode Verifying the CIM Agent Connection on Windows Esscli -uessuser -pesspass -s9.11.111.111 list serverESS CLI Service wbemhttp//tpc035/ 5989 Press any key to continue Error Messages Error Type 1. E CMMOM0002E CimerraccessdeniedCimom No CIM agent running or registered with SLP on current host Microsoft Volume Shadow Copy Service DS Open API Support for Microsoft VSS and VDS OverviewMicrosoft Virtual Disk Service Hardware Requirements Following minimum hardware is requiredSoftware Requirements License Agreement Edit Data window Password window Setup Type window Choose Destination Location window Ready to Install the Program window Creating Vssfree and Vssreserved Pools for Microsoft VSSWwname Result UsernameCimomHost server Error Codes Returned by Microsoft VSS and VDS WwpnErrarelunssupportedibmgetluninfo Erressservicefreecontroller Validate VSS Operations with Vshadow.exe Installing Symantec Backup Exec for Windows Servers Backup Exec OverviewBackup Exec Installation Overview Page Backup Exec Installation Requirements Operating systemAdditional application support Internet browserProcessor MemoryBackup Exec Service Account Storage hardwareInstalling Backup Exec for Windows Servers Page Page Before Starting Backup Exec Initial Backup Exec Server Configuration Installing the Remote Agent for Windows Systems Exchange Backup and Restore Overview of the Backup Exec Agent for ExchangeInformation for Microsoft Exchange Cluster Environments Granular Recovery Technology Benefits Performing Exchange VSS BackupsSet the Default VSS Options Select Microsoft Volume Shadow Copy Service Set Application Defaults windowConfigure the Backup Job Click New Backup JobExchange 2003 with Service Pack 1 or later ExchangeExchange Off-Host VSS Backups Media serverExchange Server Media server and the Exchange ServerConfiguring an Offhost backup Set Application Defaults window Restoring from an Exchange VSS Backup Best Practices for Using Offhost BackupClick New Restore Job Recovering Mailbox Data with Granular Restore Technology Restrictions when Restoring from Snapshot BackupsRecovering mailbox data Best Practices for Exchange Storage and VSS Backups Consistency Checks on Exchange Database and Log FilesConclusion Minimizing application impactHBA Configuration AppendixStorage Subsystem Configuration Logical ConfigurationsSwitch Configuration Software ConfigurationExchange 2003 Configuration Backup Client Software ConfigurationBackup Server Configuration VDS/VSS Provider ConfigurationDS8000 Dscli Configuration IBM DS CIM Icat Configuration
Related manuals
Manual 374 pages 22.96 Kb Manual 450 pages 61.48 Kb
Top Page Image Contents