What to Do Before Performing Any Server-Recovery Process

If a full server recovery will be conducted , or if a number of different procedures will be taken to install service packs , patches, updates, or other server-recovery attempts as an attempt to recover the server, a full backup should be performed on the server.

It might seem silly backing up a server that isn't working properly, but during the problem-solving and debugging process, it is quite common for a server to end up being in even worse shape after a few updates and fixes have been applied. The initial problem might have been that a single mailbox couldn't be accessed, and after some problem-solving efforts, the entire server might be inaccessible. Having a full backup of the server in its current state provides a rollback to the point of the initial problem state. When the backup is complete, verify that the backup is valid, ensuring that no open files are skipped during the backup process or that, if the files are skipped , they are backed up in other open file backup processes.

CAUTION

When performing any recovery of an Exchange server or resource, be careful what you delete, modify, or change. As a rule of thumb, never delete objects that are known throughout the directory; otherwise , you will not be able to restore the object due to the uniqueness of each object. As an example, if you plan to restore an entire server from tape, you do not want to first delete the server and then add the server back during the restoration process. The restoration process requires the existence of the old server in the directory. Deleting the server object and then adding the object again later gives the object a completely different globally unique identifier (GUID). Even though you restore the entire Exchange server from tape, the ID of the server and all of the objects in the server will be different, making it more difficult to recover the server. Other replicable objects that should not be deleted include public folders, public folder trees, groups, and distribution lists.

Validating Backup Data and Procedures

Another very important task that should be done before doing any maintenance, service, or repairs on an Exchange server is to validate that a full backup exists on the server, test the condition of the backup, and then secure the backup so that it is safe. Far too many organizations proceed with risky recovery procedures, believing that they have a fallback position by restoring from tape, only to realize that the tape backup is corrupt or that a complete backup does not exist.

If the administrators of the network realize that there is no clean backup, the procedures taken to recover the system might be different than if a backup had existed. If a full backup exists and is verified to be in good condition, the organization has an opportunity to restore from tape if a full restore is necessary.