Intro To Exchange Chapter 11- Backup and Recovery

  • Published on

  • View

  • Download


Intro To Exchange Chapter 11- Backup and Recovery. Preventing Disasters. Chapter 11 covers the processes to take to prevent a disaster. The most prudent actions include Implement redundant hardware Implement redundant services Using Clustering Redundant Hardware - PowerPoint PPT Presentation


<ul><li><p>*</p></li><li><p>Preventing DisastersChapter 11 covers the processes to take to prevent a disaster. The most prudent actions includeImplement redundant hardwareImplement redundant servicesUsing ClusteringRedundant HardwareTo prevent data loss from disk failure you can implement RAIDRAID is a system in which multiple disks are combined into a single logical unit in which the failure of a single disk does not result in data lossRAID 1 and RAID 5 are the most common RAID configurationsRAID 1 is mirroringRAID 5 is true RAID striping with parity</p><p>*</p></li><li><p>Preventing Disasters (2)Redundant ServicesExchange Server 2003 relies on network services to function properlyDNSWith no DNS Exchange is unavailable to deliver mail to external sitesDNS fault tolerance is achieved by having at least two DNS servers available on the network and configuring Exchange to use both DNS serversDNS is used to find Domain Controllers for authenticationActive DirectoryUsers cannot authenticate with Active DirectoryAt least two Domain Controllers should be configured to ensure fault tolerance</p><p>*</p></li><li><p>Preventing Disasters (3)ClusteringActive/Active Clustering -Exchange 2003 is configured and running on at least two serversEach node actively responds to user requests and manages messagesWhen one server fails the other takes over its tasksCost effective because all hardware is being utilizedActive/Passive ClusteringExchange is installed on up to eight serversRuns on only up to seven serversWhen an active server fails one of the inactive servers takes its placeMore scalable More expensive</p><p>*</p></li><li><p>Planning for Disaster RecoveryOverviewProperly planning for disaster recovery is essential to successful disaster recoveryWithout the right information even a complete backup of the Exchange Server 2003 databases is not enough to bring Exchange back onlineThere are several key tasks involved in disaster recovery planningDocumentationDocument system version and service packsDocument server network configuration, including IP address and DNS serversExchange Server 2003 Service PacksName of the Exchange organizationName of the administrative group in which the server is located Names of the storage grops on the serverNames of the logical databases in the storage groups on the server</p><p>*</p></li><li><p>Planning for Disaster Recovery (2)LoggingA set of log files is maintained for each storage group on an Exchange 2003All databases changes for a storage group are written to a log file(s) before the database is updatedLog files are used by Exchange 2003 to keep track of partially completed transaction if a problem occursCircular Logging removes information from the log files after it is committed to the databaseIf circular logging is used the system can only be restored to the point of the last backup</p><p>*</p></li><li><p>Planning for Disaster Recovery (3)Log File LocationLog files should be stored on physically different drives from database to aid recoveryIf stored on the same drive Exchange is only recoverable to the most recent backupIf kept on separate drives Exchange can be restored to the point just before the failure occurredBackup SchedulingIdeally a full backup should be performed every nightAdministrators should confirm backups ran successfully and logging where successful backups are keptMonitoring and logging backups ensures that they are available when required</p><p>*</p></li><li><p>Planning for Disaster Recovery (4)Available Disk SpaceRepairing databases requires free disk space equivalent to the database plus about 10 extra percent for working space on the driveAnother suggestion is to keep free disk space on each Exchange 2003 server equivalent to the largest storage group on the serverWritten InstructionsEnsure that there are written instructions on how to perform restores on ServersStorage GroupsDatabasesMailboxesWritten instructions limit the amount of thinking required to perform a recoveryBe sure to test the instructions before publishing them</p><p>*</p></li><li><p>Backing up Exchange Server 2003OverviewBackup is an essential step in disaster recoveryImportant conceptsDatabase backupsBackup softwareWhat to BackupOffline backupsFull-Text IndexesDatabase BackupsFull BackupTakes a copy of the database files and transaction logsClears the transaction logs off of the hard driveIf transaction logs are not clear they become too big and will eventually force Exchange to shut downFull backups can restore storage groupsNo other backups are necessary with a full backupDifferential BackupDoes not take a copy of the database filesDoes not remove transaction logs from the hard driveSmaller and Faster than a full backupOnly the most recent differential backup and full backup are required to restore Exchange successfullyIncremental BackupDoes not take a copy of the database filesTakes a copy of the transaction logs and removes the transaction logs from the hard driveCan be used partway through the day to supplement a daily full backupIncremental backups must be used in conjunction with a full backupThe full backup and incremental backups performed since the full back are required to restore it</p><p>*</p></li><li><p>Backing up Exchange Server 2003 (2)Backup SoftwareStandard version of NT Backup and most third party cannot backup Exchange while it is runningAn updated version of NT Backup is installed when Exchange databases and transaction logs while Exchange is runningUpdated version of NT Backup uses the Exchange backup APIThird party apps that can back up and restore individual messages perform what is called a brick-level backup and restore. Some third party apps use the new Volume Shadow Copy service to perform backupsDoes not slow down performanceTakes a snapshot and backup is performed on the backup</p><p>*</p></li><li><p>Backing up Exchange Server 2003 (3)What to BackupOS directoriesSystem stateSystem state is a set of data residing within several important but disparate components that are required for recoveryExchange Server 2003 folders (except the databases and log files)Exchange database and log filesCluster quorum(if in a cluster)Cluster disk signatures (if in a cluster)Offline BackupsOffline backups are performed by taking a copy of the Exchange database and transaction logs when the Exchange services are stoppedServices must be stoppedUsers cannot access services while they are stoppedOffline backup does not remove transaction logsCan be used if third party backup solution does not support Exchange backup APINT backup is always preferred for online backups</p><p>*</p></li><li><p>Backing up Exchange Server 2003 (4)Full-Text IndexesIt is not necessary to back up indexes because they contain redundant information that is already contained in the databases</p><p>*</p></li><li><p>Restoring a Failed Exchange 2003 ServerOverviewOnly necessary when server has experienced a catastrophic failureIdentical hardware is not necessary for restore of full backupRequires same drive lettersRequires identical OS patching to original serverRestore ProcessInstall the same version of Windows on new or repaired hardware with a temporary nameServer should not be joined to domainInstall all Windows service packs to match the failed serverRestore the last operating system backup from the old server, including the system stateRestores computer name to the same name as the failed serverInstall Exchange 2003 in disaster recovery mode.Accomplished by using /disasterrecovery switchPrevents Information Stores from being mounted after installationN.B.During installation, ensure that select only components that were installed on the failed serverPlace the databases and log files in the same location as they were located on the failed serverUsing disaster recovery mode, install all service packs for Exchange Server 2003 to match the failed serverRestore the latest version of database files that are available</p><p>*</p></li><li><p>Restoring a Corrupted Exchange 2003 StoreOverviewInvolves restoring current transaction logsCurrent transaction logs are replayed after the databases are restored, no information is lostThe store that is being restored must be dismounted firstRestore ProcessDatabase files from backup are copied back to diskThe log files are copied to a temporary directoryA restore.env file is created in the same temporary directory as log files. Restore.env is used to control the restore process and applies to a single storeExchange stores must be restored one at a time or they may be overwrittenHard recovery is performedHard recovery plays the transaction logs that were restoredTriggered by checking Last Restore Set check boxOption should not be checked if additional incremental or differential restores of transaction logs are requiredSoft recovery is performedReplays the current transaction logs and makes the store information current to the point of failureThe temporary directory with transaction log files is removed</p><p>*</p></li><li><p>Restoring an Exchange Mailbox or MessageOverviewReasons to recover a mailbox or messageReviewing deleted message as part of a legal actionRetrieving accidentally deleted messagesAllowing a manager to review the mail of a terminated employeeMethodsRecovering Deleted Items in Outlook Web AccessMessage deleted from Inbox or other folder in Outlook is placed in the Deleted Items folderMessages deleted from the Deleted Items folder it is no longer visible to the user but still available to be restoredThe length of time deleted items are retained is configurable by the Exchange AdministratorReattaching MailboxesMailboxes that are deleted accidentally or belong to a terminated employee can be restoredUser Id should be recreatedDeleted mailboxes are retained for 30 daysDeleted mailboxes can be attached to a new or recreated user accountMailboxes can be attached to a different account if a manager/administrator needs to review the contents after a user is dismissedUsing an Alternate Recovery ForestAn alternate recovery forest is at least a single server that contains a copy of your entire Exchange organizationAlternate recovery forests are completely separate from the production environment and is used for testing and recovery purposesAdvantagesProvides the ability to perform restores of public foldersAllows testing of backup integrity without affecting the production environmentAllows mailbox recovery even after retention period has expiredCan act as a test environment for service packs and third party add-onsDisadvantagesCost and time related to maintaining separate hardwareUsing the Recovery Storage Group</p><p>*</p></li><li><p>Restoring Clustered Exchange ServersOverviewRestoring clustered Exchange 2003 severs varies depending on the errorProcess to restore clustered Exchange is the same as non-clustered serverRestoring failed sever is a faster process to fix because services on failed server start up on the other servers in the clusterNo need to restore server in exactly the same state before failure because the cluster operates the same without it. </p><p>*</p></li><li><p>Restoring Clustered Exchange Servers (2)Recovery StepsUse Cluster Administrator to remove the failed server from the clusterBuild a new server to replace the old serverJoin the new server to the clusterInstall Exchange 2003 on the new serverMove resources back to the new server or leave it as a passive node in the cluster.</p><p>*</p></li><li><p>SummaryDisasters with Exchange Server 2003 can be prevented using:Redundant HardwareRAID 1RAID 5Power SuppliesNetwork CardsRedundant ServicesDNSActive DirectoryClusteringHelps limit service outages to a few minutesCan be configured as Active/Active or Active/Passive</p><p>*</p></li><li><p>Summary (2)It is important to plan properly for disaster recoveryConfiguration DocumentationChoosing a logging methodSeparating Log Files and DatabasesHaving a consistent backup scheduleEnsuring enough free space for disaster recoveryPreparing detail written instructions for disaster recoveryExchange keeps transaction logs until a full backup is performedCircular logging deleted transaction logs after their contents have been committed to the database.</p><p>*</p></li><li><p>Summary (3)Full, Differential and Incremental BackupsFull backup of Exchange Server 2003 takes a copy of the database and the transaction logs, and then deletes the transaction logs from disk. A Differential backup takes a copy of only transaction logs and does not delete the transaction logs from disk.An incremental backup takes a copy of only the transaction logs and deletes the transaction lgos from disks</p><p>*</p></li><li><p>Summary (4)Backup SolutionsExchange Server 2003 includes an updated version of NT Backup that is able to back up Exchange stores while Exchange services are running by using the Exchange backup APIThird party solutions can perform brick level backups and Volume Shadow CopiesBackups of Exchange should include the followingOS directoriesSystem stateExchange 2003 folderswith Database and logsExchange storesCluster quorum and cluster disk signatures</p><p>*</p></li><li><p>Summary (5)An offline backup is a copy of the Exchange databases taken when the Exchange Services are stoppedUsed if a third party backup software does not support the Exchange APIA failed exchange server can be restored by reinstalling Windows and Exchange Server 2003Use Disaster/Recovery switchA corrupted Exchange Server 2003 store can be restored with windows NT backupHard Recovery replays the stored transaction logs performed automatically unless Last Recovery Set box is uncheckedSoft Recovery replays the current transaction logs, runs automatically after hard recovery</p><p>*</p></li><li><p>Summary (6)Messages and mailboxes can be restored byRecovering deleted items in OutlookReattaching a mailbox to a user account,Using an alternate recovery forestUsing the recovery storage groupAn alternate recovery forest is a copy of the Exchange organization that is completely separate from the production environmentAllows restores of public of public foldersAllows testing of backup integrityAllows mailbox recovery after retention period has expiredCan act as a test environment for service packs</p><p>*</p></li><li><p>Summary (7)The Recovery storage group is a new feature in Exchange Server 2003Recovers storage group is a stoage group that can be added any existing Exchange ServerThe only utility that can retrieve messages from the recovery storage group is ExMergeClustered Exchange servers are restored by rebuilding them as a new cluster server.</p><p>*</p></li></ul>


View more >