Using clustering, a single logical database can fail over to multiple servers in the case of hardware failure. Faster and more flexible backup scheduling is possible, as databases are typically smaller. Recovery time is greatly decreased in the event of hardware failure, since each physical database can be restored individually. The restore process proceeds while other databases continue to operate online. With an Exchange 2000 database split across separate servers, an administrator can stop a single instance of the database and restore it from the transaction logs associated with that database, even while the other databases continue running.
Administration is performed at the logical level, providing a unified view of all databases.
This feature is critical for repair situations and means that only those users whose data is stored on a particular server are affected during repair and restoration. This feature also enables more flexibility in strategies for backing up Exchange data, allowing shorter backup times. Multiple databases can be backed up simultaneously, reducing administration costs. The corrupted database can be dynamically dismounted and restored from backup while the working database continues to allow user access. Of course, Exchange 2000 can be used on a single computer with a single database, just as Exchange Server 5.5 could.