You are here: Services » Emergency Services Overview » Exchange server
Print this page

 
Exchange servers fail at the worst possible time - they are in use 24/7 and they are critical to your organization.

  • It takes about 5 minutes to improve the chances of recovery for any Exchange server.
  • Exchange servers must always run on a system with equipped with RAID.
  • Microsoft Exchange 2003 and 2007 introduced several important features to make backups and restores easier.
  • You can recover deleted mailboxes instantly within 7 days of deletion, by default, in Microsoft Exchange 2000 and any subsequent version.
  • You can recover deleted items after the deleted items folder was emptied by mistake or with intent to conceal nefarious activity within 30 days of deletion, by default, in Microsoft Exchange 2000 and any subsequent version.
  • As of Microsoft Exchange 2003, we no longer require a separate server for routine mailbox restoration and can restore historical data while the server remains online.
  • There is a very inexpensive way to prevent inbound e-mail outage in the event your Exchange organization goes offline due to a failure or for maintenance.
  • There is a free anti-spam solution built into Exchange 2003 if you update it to SP2.
  • Exchange 5.5 can be migrated to Exchange 2003 with no downtime and is no longer supported by Microsoft in any way.
  • Just as is the case with SQL database servers, Exchange at its core is a database server. There are some very specific things we can do to bring the data back up to the point of failure even if your backups are more than a few days old.
  • In some instances, we've been able to bring an Exchange organization back online in 10 minutes. We have tools that enable us to diagnose your entire Exchange organization in a matter of minutes, not hours.

If your Exchange server is currently dead, regardless of its version, call us now at 510-282-1008 24 hours a day and we'll tell you how to start the process of bringing it back to life immediately.

We have more information on how to turn a typically catastrophical Exchange server failure into a non-event in Disaster Recovery.


^ Top

Previous page: Emergency Response computer services - how to address a typical SQL, or Active Directory domain controller server failure. Tips and hints how to setup a server for higher resiliency to failures. RAID arrays are essential for high availability solutions.
Next page: Emergency Response computer services - Active Directory recovery and repair. Running dcdiag, netdiag, and repadmin. FSMO failure and how to prevent FSMO crash. Removing a dead domain controller.