|

Exchange
Server down? Problems
mounting store? Information
store corrupt? Click
here.....
|
Disaster recovery is
an important part of the core services offered by any
IT consultancy. There will be times when a server
stops working and the client needs expert help to get
the system quickly up and running again.
We have been called upon many times
to recover Small Business Server, Windows Server and
Exchange Server. Whether the system requires a full
rebuild, bare metal restore, a partial restore, patches,
configuration changes etc. we can help.
We have engineers available 24x7.
So if disaster strikes, affecting Active Directory,
Windows
Server, Small Business Server or
Exchange Server, give us a call - 0845 838 5505 24x7
If your server can still browse the
Internet, we can give instant remote help using our
secure remote support client here.
|
1
|
Be prepared for a server
disaster.....
Regularly look
at the server event logs to check for any software
or hardware problems. Try to fix a problem
before it becomes a disaster! Use
server hardware management agents to check
for platform specific hardware errors. These
should warn of hardware problems or impending
hardware failure.
|
| 2 |
Take
regular (daily if possible) full backups of
Exchange and the key operating system files
(for example the System State in Win2K). Much
of the Exchange 2000 Server and the Exchange
Server 2003 configuration information (specifically
related to Internet protocols and routing)
is stored in the metabase on the local computer.
For Exchange server recovery to work successfully,
you should back up the metabase as well.
Define a backup policy for how long to archive
the
data. Verify
your backups by doing occasional restores.
Use the opportunity to train staff. |
| 3 |
Build
as much redundancy and fault tolerance as possible
into the hardware platform. Minimize single
points of failure, for example use two teamed
network
cards. Consider clustering or data replication
software if service availability is considered
crucial. |
| 4 |
Have
a documented and tested disaster recovery plan
and have all necessary software, service packs
and patches available on CD. Know your strategy
- server restore, server rebuild or standby
server? Know exactly what level
of service pack and patches you are using for Exchange
and the OS. Keep all patches, service packs and
server firmware fully up to date. Test the
patches in a separate environment
if possible prior to deployment on production systems.
|
| 5 |
Fully
document your infrastructure. Make sure you
properly document your Windows and Exchange
server's name, the names of the folders in
which the
Exchange
files are installed, the folder tree of the
drives where the database files are stored,
the complete specifications for all hardware
components, backups of the driver disks for
hardware and installation disks for any critical
software, and the logical drive specifications
|
 .gif)
|