Backing Up the Windows Server 2003 and Exchange Server 2003

 <  Day Day Up  >  

The Windows Server 2003 operating system and the Exchange Server 2003 messaging system contain several features to enhance operating system stability, provide data and service redundancy, and deliver feature-rich client services. To provide the most disaster recovery options, many services have their own backup tools and might require additional attention. This section discusses ways to back up a Windows Server 2003 system, including key components needed to make an Exchange 2003 server operate . By preparing for a complete server failure, an organization is more likely to be able to recover to a previous state. This section also outlines specific Windows Server 2003 services that have tools to aid in the backup recovery process.

Backing Up Boot and System Volumes

A backup strategy for every Exchange 2003 system should always include the boot and system disk volumes. On many installations, the boot and system volume are the same, but sometimes they are located on completely separate volumes ”usually on dual-boot computers. For the rest of this section, assume that they are both on the same partition, referred to as the system volume. This volume contains all the files necessary to start the core operating system. It should be backed up before and after a change is made to the operating system and once every 24 hours if possible.

When Exchange is installed on a Windows 2003 server, the installation will, by default, install on the system partition unless a different partition is specified during installation. On average, the amount of information stored on the system volume, with applications and services installed, is typically less than 1GB.

NOTE

When system volumes are backed up, the system state should be backed up at the same time to simplify recovery if a server needs to be rebuilt from scratch.


Backing Up Exchange Data Volumes

Having the Exchange databases written to a completely separate data drive from the operating system is typically recommended; this improves overall system and user data access performance. When systems are built with this recommendation in mind, backing up just the system volume does not back up the Exchange databases. Backing up the Exchange databases that are stored on a separate drive set frequently requires the backup administrator to specifically back up both the boot drive and the data drive. In far too many instances, organizations find out the hard way that they have been diligently backing up the Exchange server's C: drive, but have failed to back up the server's E: drive, which hosted the Exchange databases. Without a database backup, there is no data to be restored and recovered.

It is also important to note that the database volume usually has the most data needed for backup and recovery. This creates longer backup intervals and might require more than one tape depending on the size of the Exchange databases. For many organizations, a full backup of data volumes can be run only once a week, but to capture all new and modified data, incremental or differential backups can be run every day.

Backing Up Windows Server 2003 Services

Many Windows Server 2003 services store configuration and status data in separate files or databases located in various locations on the system volume. If the service is native to Windows Server 2003, performing a complete server backup on all drives and the system state, the critical data is almost certainly being backed up. A few services provide alternative backup and restore options. The procedures for backing up these services are outlined in the section titled "Backing Up Specific Windows Services," later in this chapter.

Backing Up the System State

The system state of a Windows Server 2003 system contains, at a minimum, the System Registry, boot files, and the COM+ class registration database. Backing up the system state creates a point-in-time backup that can be used to restore a server to a previous working state. Having a copy of the system state is essential if a server restore is necessary.

How the server is configured determines what will be contained in the system state, other than the three items listed previously. On a domain controller, the system state also contains the Active Directory database and the SYSVOL share. On a cluster, it contains the cluster quorum data. When services such as Certificate Server and Internet Information Services, which contain their own service-specific data, are installed, these databases are not listed separately but are backed up with the system state.

Even though the system state contains many subcomponents, using the programs included with Windows Server 2003, the entire system state can be backed up only as a whole. When recovery is necessary, however, there are several different options. Recovering data using a system state backup is covered in Chapter 32.

The system state should be backed up every night to prepare for several server- related failures. A restore of a system state is very powerful and can return a system to a previous working state if a change needs to be rolled back or if the operating system needs to be restored from scratch after a complete server failure.

Using the Active Directory Restore Mode Password

When a Windows Server 2003 system is promoted to a domain controller, one of the configurations is to create an Active Directory Restore mode password. This password is used only when booting into Active Directory Restore mode. Restore mode is used when the Active Directory database is in need of maintenance or needs to be restored from backup. Many administrators have found themselves without the ability to log in to Restore mode when necessary and have been forced to rebuild systems from scratch to restore the system state data. Many hours can be saved if this password is stored in a safe place, where it can be accessed by the correct administrators.

The Restore mode password is server-specific and created on each domain controller. If the password is forgotten, and the domain controller is still functional, it can be changed using the command-line tool ntdsutil.exe , as shown in Figure 31.1. The example in Figure 31.1 changes the password on the remote domain controller named adserver.companyabc.com .

Figure 31.1. Changing the Active Directory Restore mode password (using ntdsutil.exe ).

graphics/31fig01.gif

 <  Day Day Up  >  


Microsoft Exchange Server 2003 Unleashed
Microsoft Exchange Server 2003 Unleashed (2nd Edition)
ISBN: 0672328070
EAN: 2147483647
Year: 2003
Pages: 393
Authors: Rand Morimoto

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net