Disaster Recovery exchange server

8/7/2019 Disaster Recovery exchange server

1/51

Disaster Recovery , Exchange Server(EXCH)

The Exchange Server (Domain Controller) can be recovered usingone of the two methods.

1 Restore the Server MethodFrom a Full computer Backup Set ( System State dataand most for the data on your hard disk ) and thenrestoring your exchange database.

2 Re-Build the Server Method a. This involves performing a new installation of windows

b. Restoring your windows backup setc. Running exchange 2000 in disaster recovery mode &d. Restoring your exchange 2000 databases.

PART I

Using Restore the Server Method for

Disaster Recovery

1.1 Repairing Windows 2000There are many troubleshooting techniques you can use toresolve problems with a Windows 2000 installation. However, if aproblem arises, consider the following possibilities before usingmore complex troubleshooting techniques:Recent changes to your Windows 2000 installation, such as the

installation of new software, new drivers, or configurationchanges, might be causing or contributing to the problem.Use this section to familiarize yourself with the following basictroubleshooting techniques: Running the Windows 2000 Chkdsk utilityRunning Windows 2000 System File CheckerUsing the Safe Mode boot options


2/51

Using the Last Known Good Configuration boot optionUsing Windows 2000 Recovery ConsoleUsing the Emergency Repair ProcessReinstalling Windows 2000

Note This section does not provide every possibletroubleshooting technique for Windows 2000. For moreinformation about repairing Windows 2000, see the Microsoft Windows 2000 Server Operations Guide of Microsoft Windows2000 Server Resource Kit .

1.2 Running the Windows 2000 Chkdsk UtilityIf your Windows 2000 installation experiences a problem, youcan use the Chkdsk disk repair utility included in Windows 2000to ensure that the file system integrity and the hard diskintegrity are sound. The Chkdsk utility creates and displays astatus report for a disk based on the file system used. Chkdskalso lists and corrects errors on the disk. You can run Chkdskfrom within Windows 2000. If you are unable to start Windows2000 as a result of the problem, you can run Chkdsk fromWindows 2000 Recovery Console in Windows 2000 Setup.For more information about how to run Chkdsk to repair adamaged file, folder, or file system, see Microsoft KnowledgeBase article Q176646, "Error Message: The File or Directory IsCorrupt..." ( http://go.microsoft.com/fwlink/?LinkId=3052&ID=176646 ).For more information about how to run Chkdsk from Windows2000 Recovery Console, see Microsoft Knowledge Base articleQ229716, "Description of the Windows 2000 Recovery Console"(http://go.microsoft.com/fwlink/?LinkId=3052&ID=229716 ).

Note If the Chkdsk utility cannot lock the drive, it will offer tocheck the drive the next time the computer restarts. Also, if you run Chkdsk on a fixed disk, you must be a member of theAdministrators group.

1.3 Running Windows 2000 System File CheckerIf your Windows 2000 installation experiences a problem, but youcan still start Windows 2000, you can use the System File


3/51

Checker tool (Sfc.exe) to ensure that all the Windows 2000operating system files are the correct version and are still intact.System File Checker is a command line tool that scans andverifies the versions of all protected system files. If System FileChecker discovers that a protected file was overwritten, it

retrieves the correct version of the file from the %systemroot%\system32\dllcache folder, and then replaces the incorrect file.To run Windows 2000 System File Checker, click Start , clickRun , type sfc /scannow , and then click OK .For more information about the System File Checker tool, seeMicrosoft Knowledge Base article Q222193, "Description of theWindows 2000 Windows File Protection Feature"(http://go.microsoft.com/fwlink/?LinkId=3052&ID=222193 ).

1.4 Using the Safe Mode Boot OptionsIf your Windows 2000 installation experiences a problem, andyou are unable to boot normally into Windows 2000, try usingthe following Safe Mode advanced startup options for Windows2000: Safe ModeSafe Mode with NetworkingSafe Mode with Command PromptThe Safe Mode boot options are troubleshooting modes that loadWindows 2000 with a minimal set of device drivers and services.After you start Windows 2000 in Safe Mode, you can usetroubleshooting techniques such as running System File Checkeror restoring backups to resolve the problem.For more information about the Safe Mode boot options andother advanced startup options, see Microsoft Knowledge Basearticle Q202485, "Description of Safe Boot Mode in Windows2000" ( http://go.microsoft.com/fwlink/?LinkId=3052&ID=202485 ).

1.5 Using the Last Known Good Configuration BootOptionIf you experience difficulty starting Windows 2000 after youinstall a new driver or change a driver configuration, you can usethe Last Known Good Configuration advanced startup options for


4/51

Windows 2000. If you use this boot option, the registryconfiguration reverts to the condition it was in before you madethe changes that prevented Windows 2000 from startingnormally. Furthermore, if you use this option, you will lose allconfiguration changes that were made since you last successfully

logged on to your system.For more information about the Last Known Good Configurationand other advanced startup options, see Microsoft KnowledgeBase article Q202485, "Description of Safe Boot Mode inWindows 2000" ( http://go.microsoft.com/fwlink/?LinkId=3052&ID=202485 ).

1.6 Using Windows 2000 Recovery ConsoleWith Windows 2000 Recovery Console, you can obtain limitedaccess to NTFS, FAT, and FAT32 volumes without starting theWindows graphical interface. In Recovery Console, you can: Use, copy, rename, or replace operating system files and folders.Enable or disable services or devices from starting when younext start your computer.Repair the file system boot sector or the master boot record

(MBR).Create and format partitions on drives.You can install Windows 2000 Recovery Console as a Windows2000 Boot Menu option, or you can run Recovery Console fromWindows 2000 Setup. For more information about how to useWindows 2000 Recovery Console, see Microsoft Knowledge Basearticle Q229716, "Description of the Windows 2000 RecoveryConsole" ( http://go.microsoft.com/fwlink/?LinkId=3052&ID=229716 ).

1.7 Using the Emergency Repair ProcessYou can use the Windows 2000 Emergency Repair Process to fixproblems that prevent you from starting your computer,including problems with your registry, system files, partition bootsector, and startup environment. You start the Emergency RepairProcess after using either the Windows 2000 Setup CD or the


5/51

Windows 2000 Setup floppy disks to restart the computer.However, the Emergency Repair Process is more successful if you create an emergency repair disk (ERD) after you installWindows 2000. If you have an ERD, the Emergency RepairProcess attempts to replace damaged files on your computer.

1.8 Windows 2000 Emergency Repair Disk CreationAlways maintain a current Windows 2000 emergency repair disk(ERD) for each server in your company.

1.8.1 To create an ERDIn the Windows 2000 Backup utility (Backup), on theWelcome tab, click Emergency Repair Disk .

1.9 To run the Emergency Repair Process

1. Restart your computer using either the Windows 2000 CDor the Windows 2000

Setup floppy disks.

2. Run Windows 2000 Setup.3. In Setup Notification , click Enter to continue the

Setup process.

4. On the Welcome to Setup page, press R to repair aWindows 2000 installation.

5. On the Windows 2000 Repair Options page, press Rto repair a Windows 2000 installation using theEmergency Repair Process.

6. Select one of the following repair options:

Press M if you want to perform a manual repair. Themanual repair option, which requires user interaction,allows you to select whether you want to repair systemfiles, partition boot sector problems, or startupenvironment problems. However, this option does notallow you to repair problems with your registry. If you


6/51

want to manually repair individual registry files or replaceyour entire registry, use Recovery Console.

Important The manual repair option should only beused by advanced users or administrators.

Press F if you want to perform a fast repair. The fastrepair option is the easiest and does not require anyuser interaction. This option attempts to repairproblems related to the registry, system files, thepartition boot sector on your boot volume, and yourstartup environment (if you have a dual-boot ormultiple-boot system).

NOTE:

The fast repair option uses a backup copy of theregistry that was created when Windows 2000 Setupwas first run on your computer. If you select thisoption, you may lose settings or preferences youcreated since Setup was first run.

7. If you have an ERD, press ENTER. The repairprocess starts, prompting you to insert your ERD disk.It also prompts you to insert your Windows 2000 SetupCD.

8. If you do not have an ERD, press L. The repairprocess starts, attempting to locate your Windows2000 installation. It also prompts you to insert yourWindows 2000 Setup CD.

Note If the Emergency Repair Process cannot fix yoursystem, try using Recovery Console, or try reinstallingWindows 2000.

9. Follow the prompts as the Emergency Repair Processattempts to repair your computer.

10. When prompted, restart your computer. If theEmergency Repair Process was successful, your computerautomatically restarts.

Important The Emergency Repair Process relies oninformation that is saved in the Systemroot\Repair folder.You must not change or delete this folder.


7/51

1.10 Reinstalling Windows 2000If the computer still does not operate normally after you performthe Emergency Repair Process, use the Windows 2000 Setup CDto perform an in-place upgrade over the existing installation. Thelength of time it takes to perform this in-place upgrade is equalto the amount of time it took to perform your original Windows2000 installation.

Important After you perform an in-place upgrade, changes that weremade to your system after the original Windows 2000 installation (suchas service pack upgrades and system customizations) may be lost.

To reinstall windows 2000 server go to the section Using Rebuild theServer Method for Disaster Recovery in part II of this document.


8/51

2.1 Repairing Exchange 2000You may experience problems with your server runningExchange 2000. However, these problems may not necessarilyrequire you to perform a database restore or a completerecovery of the server. For example, you can repair Exchange2000 by repairing your Exchange databases, or by reinstallingExchange 2000.

Note Before attempting to perform any of the followingprocedures, restart your Exchange server. Restarting theserver may resolve the problem.

This section contains the following topicsregarding Exchange 2000 repair processes:Reinstalling Exchange 2000 over a damaged installationRepairing Exchange 2000 databases

2.2 Reinstalling Exchange 2000 Over a DamagedInstallationReinstalling Exchange 2000 and any relevant service packs andhotfixes helps ensure that all Exchange 2000 files are intact andare the correct version. Reinstalling Exchange 2000 and anyservice packs stops Exchange services from running on theExchange server during the install processes; therefore, userscannot access the Exchange server until after the installationsare complete.

To reinstall Exchange 20001. Insert the Exchange 2000 Installation CD, and then click

Exchange Server Setup .

2. In Microsoft Exchange 2000 Installation Wizard , on theWelcome page, click Next .

3. On the Component Selection page, under Action , selectthe Reinstall option next to each component name that is


9/51

installed on your server running Exchange, and then clickNext Components that are not installed are not available.

Figure 2.2 The Component Selection page of Microsoft Exchange2000 Installation Wizard

4. On the Component Summary page, click Next to begin thereinstall process).

Figure 2.3 The Component Summary page

5. As the reinstall process is in progress, view theComponent Progress ). Exchange 2000 stops all Exchangeservices and performs all the necessary steps to reinstallExchange 2000 over the damaged installation, includingrecopying all files.


10/51

Figure 2.4 The Component Progress page

6. As Setup attempts to copy installation files to your computer,the Confirm File Replace dialog box may appear, asking if you want to overwrite certain files on your computer that arenewer than the files being copied from the Exchange 2000Setup CD (Figure 1.4). Because you are attempting to repairfiles that are either damaged or the wrong version, you shouldclick Yes to overwrite these files. You can restore the newerversions of these overwritten files in the repair process whenyou install the Exchange 2000 service packs or hotfixes thatwere installed on the server prior to the repair process.

Figure 1.4 The Confirm File Replace dialog box

7. After Exchange 2000 Setup is complete, Setup notifies youif there are errors and whether your installation of Exchange2000 is successful.

8. Click Finish to exit Setup.

9. Install any Exchange 2000 service packs and hotfixes thatwere installed to the server prior to the repair process.

2.3 Repairing Exchange 2000 DatabasesYou can repair Exchange 2000 database files (.edb files) usingthese Exchange 2000 utilities: Eseutil.exe and Isinteg.exe


11/51

(Eseutil replaces the Edbutil utility that was used with previousversions of Exchange).Consider the following information when repairingExchange 2000 databases: Repairing Exchange databases with Eseutil and Isinteg can resultin losing data in the Exchange databases you repair. For thisreason, you should copy the database files you are repairingprior to attempting the repair process. (For information abouthow to copy your database files, see "Copying or Moving theExisting Versions of the Database Files That You are Restoring"later in this chapter.) Because you cannot undo changes thatwere made to a database during the repair process, only useEseutil and Isinteg as a last resort .It is recommended that you recover a damaged database byrestoring a backup set rather than repairing a database.

If you use Eseutil to repair an Exchange 2000 database, youmust have enough free disk space for Eseutil to make a copy of the database being repaired. Before you begin the repairprocess, ensure that the amount of disk space on the hard drivecontaining your database files is greater than the size of thedatabase being repaired. Using the Eseutil and Isinteg utilities torepair a database file takes a substantial amount of time.Typically, it takes much longer to repair a database than it doesto restore a database from backup. If both utilities runsuccessfully (for example, if there are not any errors at the end

of the last Isinteg run), the database is generally considered tobe repaired and ready to replace the damaged database. If Eseutil and Isinteg are unable to fix every error in the database,you should not discard a repaired database. You should onlydiscard a repaired database if you experience specific problemswith it; for example, if a database does not mount aftercompleting the repair process, you should discard that databaseFor more information about the Eseutil and Isinteg utilities, seeMicrosoft Knowledge Base article Q259851, "XADM:Ramifications of Running the ESEUTIL /P or EDBUTIL /D /RCommand" ( http://go.microsoft.com/fwlink/?LinkId=3052&ID=259851 ).For information about the various command-line switches andusages of Eseutil and Isinteg, see Microsoft Knowledge Basearticles Q182903, "XADM: ESEUTIL Command Line Parameters"(http://go.microsoft.com/fwlink/?LinkId=3052&ID=182903 ) andQ182081, "XADM: Description of Isinteg Utility"(http://go.microsoft.com/fwlink/?LinkId=3052&ID=182081


12/51

2.4 Backup Requirements for Restoring a ServerFull computer backup setA full computer backup set includes a backup of System Statedata and most of the data on your hard disks, excluding theExchange installable file system [IFS] drive and the drives orfolders that contain your Exchange 2000 database files andtransaction log files. At a minimum, a full computer backup setmust include the Windows boot and system partitions, theExchange installation folder, and the computer's System Statedata.

Exchange 2000 database backupsTo back up Exchange 2000 databases, use the MicrosoftInformation Store backup options in Windows 2000 Backup.Perform these backups daily to keep them current.

2.5 Advantages and Disadvantages to Restoring aServerRestoring the server has the following advantages anddisadvantages in comparison to rebuilding the server or keepinga stand-by recovery server:

Advantages You can usually restore a server faster than you canrebuild an entire server. To rebuild a server, you must manuallyinstall Windows 2000 Server, Exchange 2000 Server, and otherapplications or files.

You can restore all configuration information for yourapplications such as Active Server Pages (ASP), mailbox agents,

and workflow software instead of re-creating it.Disadvantages

Because you are backing up most files on your computer, youneed more disk space or tapes for your backup sets, and yourbackup jobs take longer to complete.


13/51

You spend more time managing your backups compared to othermethods. You can minimize this time if you automate yourbackups.

Your computer operating environment is not as clean as whenyou rebuild a server. Full computer backups back up every file ona disk drive, including any damaged files or mismatched DLLs.

NOTE : You may experience severe problems if any of thereplacement hardware (for example, disk drives) on the server being restored is different than the hardware on the originalserver. These problems may occur because the files backed upduring the full computer backup contain driver information and files specific to the hardware on the original server. Furthermore,if you restore a full computer backup set to a computer that hasa different CPU, chip set, processor, or other operating systemcomponents than the original server, you may not be able tostart Windows 2000 properly. To avoid this problem, ensure that you have replacement hardware that is identical to the hardwareyou are currently using.

To resolve these issues if they occur, start Windows 2000in Safe Mode after restoring the full computer backup set,remove the drivers for the different hardware, restart thecomputer, and then allow the computer to detect thedifferent hardware. You may still, however, experienceproblems integrating or installing the new drivers into

your server. These problems are similar to those manyusers experience when installing new hardware.

2.6Creating Windows 2000 Backup SetsTo completely back up the operating system of a server runningWindows 2000, you must back up both its System State data andits operating system files. A backup of Windows 2000,including both the System State data and the boot andsystem partitions, is called a Windows backup set . AWindows backup set must contain the following data and mustbe backed up as part of the same backup job:The System State data


14/51

The boot partition (the disk partition from which your computerstarts. This partition contains files in the root directory such asNTLDR and BOOT.INI)The system partition (the disk partition to where Windows isinstalled)

Note If you installed Windows 2000 to the hard disk partitionthat is used to start your computer (known as the activepartition), your boot partition and system partition will be thesame.You back up a computer's System State data using the SystemState data option in Backup. When performing a System Statebackup, Backup automatically backs up all of the relevantSystem State data for your computer. Because of thedependencies among System State components, you cannotback up or restore individual components of System State data

using BackupNote: When backing up the System State data, a copy of yourregistry files is also saved in the systemroot/repair/regbackfolder. If your registry files become damaged or areaccidentally erased, use these copied files to repair yourregistry without performing a full restore of the System Statedata. Repairing the registry in this way is only recommendedfor advanced users.To back up your computer's Windows operating system files,back up the boot partition (the partition that contains the files

that start Windows 2000) and the system partition (the partitionwhere the Windows 2000 folders reside, such as the WINNTfolder, Documents and Settings, and Program Files folders).

Important In preparing to restore the Windows 2000 operatingsystem configuration information, you must restore theserver's System State data and its operating system files;these data and files must be part of the same backup set.Create Windows backup sets frequently. In general, the lesscurrent your Windows backup sets are, the more likely you are toexperience problems that you must resolve before you canrestore Exchange 2000.

2.7 To create a Windows backup set :


15/51

1. Click Start , point to Programs , point to Accessories , pointto System Tools ,and then click Backup .

2. In Backup , click the Backup tab. In the console tree, clickthe boxes next to the drive letters for your boot partition and

system partition, and then select the check box next toSystem State (Figure 1.5).

Figure 1.5 Selecting a System State backup

3. In the Backup destination list, perform one of the followingsteps:

Select File if you want to back up files and folders to a file.

If you do not have a tape device installed on your computer,this option is selected by default and cannot be changed.Select a tape device if you want to back up files and foldersto a tape.

4. Next to the Backup media or file name box, click Browseto select a location and file name for your backup.

5. Click Start Backup .

6. In Backup Job Information , in the Backup descriptiontext box, type a backup description, set the appropriateoptions, and then click Start Backup.


16/51

7. After the backup completes, verify the backup wassuccessful.

2.8Backing Up Exchange 2000 DataThe Exchange 2000 data you need to back up depends on whatcomponents are installed on your server running Exchange 2000.This section provides detailed descriptions and proceduralinformation about the following types of backupsBacking upExchange 2000 databasesBacking up Exchange 2000 Site Replication ServiceBacking up Exchange 2000 Key Management ServiceBacking up connector-specific information

Note To locate the Microsoft Information Store options that arereferred to in this section, in Backup, in the console tree,expand Microsoft Exchange Server, expand the server youwant, and then expand Microsoft Information Store.

2.9 Backing Up Exchange 2000 DatabasesThe mailbox store and public folder store data contained withinyour Exchange 2000 databases and transaction log files are themost important data to back up in your Exchange 2000organization. You can use an Exchange 2000 database backup torestore damaged mailbox or public folder stores to a functioningserver running Exchange 2000. Exchange 2000 uses theMicrosoft Information Store options in Backup to back upExchange 2000 databases and their associated transaction logfiles. To manage this process, Backup makes API calls to theExchange 2000 Extensible Storage Engine (ESE). Exchange 2000informs ESE that it is entering a backup mode, and then,assuming you are running a Normal backup, a patch file isgenerated for each database. If you are running a Differential orIncremental backup, a patch file is not generated becauseDifferential and Incremental backups only back up transactionlogs. When ESE enters a backup mode, a new log file opens. Forexample, if Edb.log is the current open log file, Edb.log is closedand renamed to the latest generation, and a new Edb.log isopened. After the backup completes, the new Edb.log filedesignates the point when the ESE can truncate the logs.


17/51

2.10 To back up Exchange 2000 databases

1. On any computer in the Windows 2000 domain forest runningExchange 2000, click Start , point to Programs , point toAccessories , point to System Tools , and then click Backup

Figure 2.0 Welcome to windows backup Screen

2. In Backup , click the Backup tab.


18/51

2. On the Backup tab, in the console tree, expand MicrosoftExchange Server , and then expand the server that containsthe Exchange 2000 databases that you want to back up.

Note In the console tree, you use the Microsoft Exchangeoption only to back up databases on previous versions of Exchange.

4. To back up the Exchange 2000 databases, perform one of thefollowing procedures:


19/51

If you want to back up all storage groups on that server,select the check box next to Microsoft Information Store

If you want to back up specific storage groups in theirentirety, expand Microsoft Information Store , and then

select the check boxes next to the storage groups you want toback up.

If you want to back up specific mailbox stores and public storesin a storage group, expand Microsoft Information Store , clickthe storage group that contains the databases you want to backup. Then, in the details pane, select the check boxes next to thedatabases you want to back up.

5. Next to the Backup media or file name box, click Browseto select the media for your backup

6. The next screen is the backup Job information. Give it anappropriate name and click on the replace the date on themedia radio button.


20/51

7. Click on the Advanced button and choose verify data afterbackup. Also in the backup type select Normal and click O.K.

8. Click Start Backup .


21/51

9. Warning message to overwrite the data on the media. Clickon Yes

9. Backup Progress screen shown


22/51

10. Backup complete Screen.


23/51

11. After the backup completes, verify the backup wassuccessful.

HOW TO: Schedule a Daily Backup in Windows2000

SUMMARYThis step-by-step article describes how to schedule a backup job onyour Windows 2000-based computer.

When you schedule a backup job, you can have an unattended backupjob occur at a later time when users are not working and files areclosed. You can also schedule backup jobs to occur at regular intervals.Windows 2000 integrates the Backup Wizard with the Task Schedulerservice to help you to schedule backup jobs.

How to Schedule a Backup JobNOTE : You must have the Task Scheduler service running before youcan schedule a backup. If the Task Scheduler service is alreadyrunning, skip to step 1. If the Task Scheduler service is not alreadyrunning, type net start schedule at a command prompt, and then


24/51

press ENTER. After you receive a message that indicates the TaskScheduler service was started successfully, continue to step 1.

1. Log on as an administrator. Click Start , point to Programs ,point to Accessories , point to System Tools , and then click

Backup .

2. On the Welcome tab, click Backup Wizard .


25/51

3. Click Next to begin to create the backup job. You are thenprompted to choose what you want to back up by selecting one of the following options:

Backup Up Everything On My Computer Backs up all fileson the computer on which you are running Backup Wizard,


26/51

except those files that Backup Wizard excludes by default (suchas certain power management files). Back Up Selected Files, Drives, Or Network Data Backsup selected files and folders. This includes files and folders on

the computer where you run Backup Wizard and any sharedfiles or folders on the network. When you click this option, theBackup Wizard provides a hierarchical view of the computerand the network (through the My Network Places tool). Only Back Up The System State Data Backs up importantsystem components, such as the registry and the boot files forthe computer on which you are running Backup Wizard.

4. Click Back Up Selected Files, Drives, Or Network Data , andthen click Next to continue.


27/51

5. When you are prompted to select the local and network drive,folder, or file you want to back up, expand the My Computerbranch, and then select the drive, folder or file that you want to backup.


28/51

6. Click Next to continue. When you are prompted to select thedestination for the data you will back up, type c:\backup.bkf orWhere ever you want to store the file in the Backup Media Or FileName box, and then click Next. Note that if you do not have a tapedrive that is connected to your computer, File is the only backupmedia type that is available in the Backup Media Or File Namebox.


29/51

7. Click Advanced to specify additional backup options.


30/51

8. When you are prompted to select a backup type for this backupjob, click Normal in the Select The Type Of Backup OperationTo Perform box, and then click Next .


31/51

9. When you are prompted to specify whether or not to verify thebacked up data after the backup job finishes, click to select theVerify Data After Backup check box, and then click Next .

10. When you are prompted to specify whether to append thisbackup job to existing media or overwrite existing backup data onthe destination media, click the Replace The Data On The MediaWith This Backup option. Make sure that the Allow Only The

Owner And The Administrator Access To The Backup DataAnd To Any Backups Appended To This Media check box is notselected, and then click Next .


32/51

11. When you are prompted to provide a label for the backup joband a label for the backup media, type Backup file for computer name in the Media Label box, and then click Next .

12. When you are prompted to choose whether to run the backupjob now or schedule this backup job, click Later . The Set AccountInformation dialog box appears, and prompts you to provide thepassword for the administrator account. Note that if the TaskScheduler service is not set to start automatically, you may first be


33/51

asked whether you want to start Task Scheduler. If this occurs, clickYes , and then the Set Account Information dialog box appears.

Because the Task Scheduler service automatically runsprograms within the security context of a valid user for thecomputer or domain, you are prompted for the name andpassword with which the scheduled backup job will run.For scheduled backup jobs, you should supply a useraccount that is a member of the Backup Operators groupwith permission to gain access to all of the folders andfiles to be backed up. The instructions in this article usethe administrator account to run the scheduled backupjob.

13. Make sure that computer name \Administrator appears in theRun As box, and then type the correct password in the Passwordbox and the Confirm Password box. Click OK .


34/51

14. In the Job Name box, type computer name Backup , and thenclick Set Schedule .


35/51


36/51

16. In the Schedule Task box, click Daily , type 12:00 a.m. (or atime that is more convenient for your environment) in the StartTime box, and then click OK .


37/51

17. Click Next to continue. The Backup Wizard displays theCompleting The Backup Wizard page that displays the options andsettings that you selected for the backup job. Click Finish to startthe backup job. The Backup window remains displayed with theWelcome tab active. Close the Backup window.


38/51

After you schedule the backup job and complete the BackupWizard, Windows Backup places the backup job on the calendaron the Schedule Job tab in Windows Backup. The backup jobautomatically starts at the time that you specified.


39/51


40/51

2.11 To Restore Exchange 2000 databases1. On the computer in the Windows 2000 domain forest running

Exchange 2000, click Start , point to Programs , point toAccessories , point to System Tools , and then click Backup

figure 2.0 Welcome to windows backup

2. If the backup set is not displayed then you need to run amanual catalogue process. This applies only if the backup setexists on files and not on the tape backup.


41/51

3. Right click on the file icon and enter the name of the backupand where it can be found

4. The backup set is now available for restoring


42/51


43/51

7. The actual data are now visible to restored. Click on the checkboxes next to the data to be restored and click on the restorebutton

8. The next option is the Restore database store. In the

temporary location for log and patch files, type in a temporaryfile name as in the figure


44/51

9. The option enter the path and the file name of the backup youwant to restore. This option is only displayed if the backed updata is on a file.

10. Click on the restore button. The progress screen appears


45/51

11. The restore complete screen appears. Click on the report

button to verify the restore operation

12. Confirm the restore operation for success


46/51

PART -II

Using Rebuild the Server Method for DisasterRecovery

3.1Rebuilding the ServerTo rebuild a server, install as much of the static data on yourcomputer as possible (including performing a new installation of Windows, installing applications that existed on the server, andso on), and then use Backup to restore any dynamic data(Windows System State data, Windows partitions, applications,and so on). After installing the static data and restoring thedynamic data, you must run Exchange 2000 Setup in DisasterRecovery mode to match your new Exchange serverconfiguration with that of the original server. Finally, you mustrestore any Exchange service packs and Exchange databases.When rebuilding a server, you must have all of the software toinstall your static data (Windows 2000 Server disks, Exchange2000 Server disks, and so on), as well as the necessary backupsto restore any dynamic data (a Windows backup set, MyDocuments folder backups, Exchange 2000 database backups,and so on). It is not necessary to back up all of the contents of your drives. You just need to back up the information that cannotfeasibly be re-created without a backup; at a minimum, thisincludes a Windows backup set and a backup of your Exchangedatabases.

3.2 Backup Requirements for Rebuilding a ServerWindows backup set :A Windows backup set includes three parts: System State data, theWindows boot partition, and the Windows system partition.Dynamic data backups :A back up of any mission-critical data or other data that isimpossible or difficult to re-create manually, such as Web pages,Web applications, custom scripts, and databases of non-Exchange applications.


47/51

Note: Although having a separate backup of the Exchsrvr folder(Exchange installation folder) is useful in some recovery scenarios,this folder is typically not backed up as part of the "rebuild theserver" method.

Exchange 2000 database backupsTo back up Exchange 2000 databases, use the MicrosoftInformation Store backup options in Windows 2000 Backup.Perform these backups daily to keep them current.

3.3 Backup Rotations and Schedules

To ensure that you are able to recover the maximum amount of data after a disaster, maintain regular backup rotations andschedules.

For your Exchange 2000 databases, it is recommended that youperform a Normal backup daily

3.4 Advantages and Disadvantages to Rebuilding aServerRebuilding the server has the following advantages and

disadvantages in comparison to restoring the server.Advantages

Because you are not backing up almost every file on all the harddisks, you need less disk space or tapes for the backup sets.

You usually end up with a cleaner, more stable operating systemenvironment with better performance than if you restored aserver from full computer backups. When you restore a server,all or most of the folders and drives from your full computerbackup set are restored. As a result, that backup set may includefiles that are damaged or incorrect versions, which may havecontributed to the disaster. For this reason, when you restore aserver from full computer backups, you may be copying thoseinstabilities to your replacement server. However, when yourebuild a server, the installation of the operating system andother applications, including Exchange, is clean, therebyreducing the risk of introducing errors that could affect theperformance of your server running Exchange 2000.


48/51

Disadvantages

Rebuilding a server running Exchange 2000 generally takeslonger than restoring a server from full computer backups.

You may experience severe problems if any of the replacement

hardware (for example, disk drives) on the server being rebuilt isdifferent than the hardware on the original server. Theseproblems may occur because the replacement hardware may notbe compatible with the configuration information contained inthe Windows 2000 System State data that you restored with theWindows backup set. Furthermore, if you rebuild a computer thathas a different CPU, chip set, processor, or other operatingsystem components than the original server, you may not beable to start Windows 2000 properly. To avoid this problem,ensure that you have replacement hardware that isidentical to the hardware you are currently using

Note: To resolve these issues if they occur, start Windows2000 in Safe Mode after you restore the Windows backupset, remove the drivers for the different hardware, restartthe computer, and then allow the computer to detect thedifferent hardware. Keep in mind that you may stillexperience problems integrating or installing the newdrivers into your server . These problems are similar to those thatmany users experience when installing new hardware.

3.5 Steps for Rebuilding a ServerTo rebuild a server

1. Replace damaged hardware if any

2. Rebuild the server. Perform a new installation of Windows2000, ensuring that you use a random computer name and makethe computer a member of a workgroup instead of joining thedomain. Next, install any other applications (other thanExchange 2000) that run on the server. Be sure to reconfigure

the applications as they were previously configured, such asinstalling them to the same drives and directories to which theywere originally installed. Finally, install any service packs,patches, or updates for Windows 2000 and your serverapplications.

3. Restore your Windows backup set. Restoring your SystemState data and Windows operating system files restores the


49/51

Windows 2000 registry database files that provide the rebuiltcomputer with its original NetBIOS name, returns the server to itsoriginal domain, and restores many other important files (such asthe IIS metabase).

4. Restore your dynamic data from backup.

5. Run Exchange 2000 Setup in Disaster Recovery mode. Thisreclaims the Active Directory configuration information for therebuilt Exchange 2000 server and returns the Exchange 2000files to the computer.

6. Install any Exchange 2000 service packs in Disaster Recoverymode. When you install Exchange 2000 service packs, use thedisaster recovery setup switch. This switch prevents theExchange 2000 databases from being mounted at the end of thesetup, so that you can proceed directly to restoring thedatabases from backup.

7. Restore Exchange 2000 database using Backup.

3.6 Summary of Disaster RecoveryStrategies

Table 2.1 summarizes the three strategies for recovering an Exchange2000 server from a disaster, including the advantages anddisadvantages for each method.

Table 2.1 Backup and recovery methods

Restoring theServer

Rebuilding theServer

BackupRequirements

Full computerbackup setBackup of Exchange 2000

databases

Windowsbackup setBackups of dynamic data

(data that isimpossible tore-create)Backup of Exchange 2000databases


50/51

RestoreProcedures

1. Replacedamagedhardware.2. Perform a

full computerrestore.3. Restore the

Windows 2000System State.4. Restore

Exchange 2000databases.

1. Replacedamagedhardware.2. Rebuild the

server.3. Restore the

Windowsbackup set.4. Restore the

dynamic data.5. Run

Exchange 2000Setup inDisasterRecoverymode.6. Reinstall

Exchange 2000service packsin DisasterRecoverymode.7. Restore

Exchange 2000databases.

Restoring theServer

Rebuilding theServer

Advantages

Faster thanrebuilding aserverEasier torestore data,and

applications,andconfiguration

Uses less diskspace or tapesfor the backupsthan restoringthe serverResulting

operatingenvironment isusually morestable andprovides betterperformance


51/51

Disadvantages

Requires moredisk space ortapes for thebackup.Backup jobstake longer tokeep yourbackupscurrent.Backups maybeincompatible if yourreplacementhardware is notidentical.Operating

systemenvironment,etc, may notbe installed ascleanly as withotherstrategies.

Takes longer torecover aserver than itdoes usingeither of theother twostrategies.Backups maybeincompatible if you replace thedamagedhardware withhardware thathas differentspecifications.