Wednesday, June 01, 2011
Dave Keys is a piece of crap pirate. He blatantly stole my company name, and the worst thing is Dave Keys is a photographer, he doesn't know crap about SEO, yet he is a minion of a total loser so-called blog coach. The blog coach who doesn't have a blog and doesn't know anything relative to how search engines work.
Stay away from posers such as Dave Keys, he is dangerous to people that want to succeed on the Internet. Nobody needs so called insight from a loser and a pirate that steals ideas from others. Hire this idiot to take pictures, but don't put your online presence with somebody who is coached to steal content and names. dave Keys is a total user scumbag.
Tuesday, December 18, 2007
Hard Drive Recovery Programming
It is vital that when looking at data recovery companies, that you choose a real lab with a clean room and engineers. In the US there are only a handful of data recovery companies that actually operate a class 100 clean room. More importantly is the fact that even less have qualified technicians that are capable of programming and rebuilding file systems. The software side of hard drive recovery is actually harder than the repair of the disk. Since hard drive usually fail from the inside out, the operating system is almost always damaged. That is why DTI Data is your best choice for hard drive recovery. All the software that we sell on our site was created by our own in house programmers. We have the capabilities to rebuild file systems from the hex level. Don't take a chance on losing your data choose DTI for your hard drive recovery.
Monday, July 09, 2007
Hard Drive Recovery For Exchange
If the Exchange Server has had a physical failure, that the first step is hard drive recovery. DTI has a class 100 clean room where they perform the repairs to the hard disk to extract the data and the databases. DTI is one of only a few data recovery companies in the world that specialize in both Exchange restoration and hard drive recovery.
The ideal set up for Exchange is that the operating system and programs are on one partition or hard drive that is set up in a RAID 1. The MDBDATA folder that houses the PRIV1 EDB and STM as well as the PUB1 EDB and STM should be on a secondary partition that is on a RAID 1 for a smaller Exchange install, or a RAID 5 for larger or Enterprise storage groups.
If your server has crashed call our Exchange emergency line at 727-251-2058 or the numbers below during normal business hours. If you have had a physical crash visit our site about hard drive recovery.
24 Hour Hard Drive Recovery & Server/RAID Recovery Hotline:
Toll Free 1-866-438-6932 or direct 1-727-345-9665.
Extended Software Support:
8 AM to 11 PM EST 7days a week!
Friday, February 23, 2007
Exchange Server Backup Part II: Restoring Exchange Using Windows Backup
This is a continuation of my previous article entitled “Exchange Server Backup: Using Windows Native Backup”. It assumes a backup was performed using the steps described in that article. It also assumes the server running Exchange is still functioning. Restoring an entire Exchange server, operating system and all will be a topic for another article.
Prior to running a restore, it is extremely important that you first perform an offline backup of your database. If for any reason the restore process fails, having an offline backup will give you the option of repairing your database files and at least getting some of your data back.
Make sure you are logged into an administrative account to perform the functions in this article.
To perform an offline backup:
- Shut down the information store
Right-click My Computer > click Manage > go to Services and Applications > Services > right-click Microsoft Exchange Information Store and choose “Stop”
- Verify the location of your private and public database files, and transaction log files. On Exchange 2000 these are located by default in C:\Program Files\Exchsrvr\MDBDATA, however it is common practice to place the database files on a separate drive from the transaction log files.
- Copy the database files (.edb), the streaming database files (.stm), checkpoint file (.chk) and the log files (E0*.log) to another location. If the files are all in one directory, then you could just copy the entire MDBDATA folder to a backup location.
To restore Exchange:
Make sure the Information store is started
From Exchange System Manager, navigate to Administrative GroupsàFirst Administrative GroupàServersàServernameàFirst Storage Group
Right-click the store you are going to restore and choose “Dismount Store”
After the store has dismounted, right-click again and choose “Properties”
Click the database tab and select “This database can be overwritten by a restore”
6. Click Start > Programs > Accessories > System Tools > and click Backup
7. If backup starts in wizard mode, select advanced.
Click on the Tools tab and select “Restore Wizard”
On the Welcome screen, click Next
On the What to Restore screen, if your backup file is not listed:
Browse to the location of your backup file (.bkf)
Click OK to catalog the backup file
On the What to Restore screen, choose the mailbox store you want to restore and log files
Verify that your server name is listed under Restore To, choose a temporary path for log and patch files, and select Last Restore Set (unless you will be restoring incremental backup files after this)
Click Next to start the restore process
When the restore is complete, click close or you could view the report
Return to Exchange System Manager and mount your restored mail store
If the restore process was successful, the store should mount without error
At this point you will want to connect to your exchange server with a client to test functionality and make sure everything is OK. This guide describes a very basic restore scenario, as mentioned earlier you may run into a situation where your whole server needs to be restored, you may need to only restore a particular mailbox, or you may want to set up an identical server to periodically test the restore process. Some of these scenarios will be discussed in future articles.
Tuesday, November 28, 2006
What is a reverse NDR attack?
Spammers have a new means to avoid filters built into many systems. They take advantage of a mail systems sending of a non-delivery report (NDR) when a message cannot be delivered as addressed and returns the original contents.
How do I know that my server is suffering from a Reverse NDR attack?
There are several symptoms that you may see within the Microsoft Exchange Server Admin:- Outbound email is not being delivered (To view your outbound queue go to the properties of your Internet Mail Service connection, then click on the Queues tab and switch to outbound messages awaiting delivery)- Take note of the originator in the outbound queue, if you see <> under originator 99% of the time it will be a spam mail that has generated an NDR. If you see hundreds/thousands of these then you are most likely suffering a RNDR attack on your exchange server.
How do I clear the outbound queue?
I will explain how you can clear the outbound queue, but this will by no means resolve your issue as soon as the Internet Mail Service is started you will continue to resolve spam emails that generate NDRs on your system
(1) Stop the Internet Mail Service
(2) Go to the following directory path: (ie c:\exchsrvr\imcdata\out)
(3) Delete all files in this directory (each file is an email to be sent out, if you have users that are trying to send out there emails are in here also. You may need to advise them to resend emails that they just recently tried to send out, since they will most likely be deleted.)
(4) Delete the queue.dat file in the imcdata directory.
(5) Restart the Internet Mail Service
Here is Microsoft's KB article on how to resolve this issue:
Update available in Exchange Server 5.5 to control whether the Internet Mail Service suppresses or delivers NDRs
October 26, 2006
This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986
Description of the Microsoft Windows registry
var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'";
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;
An update to Microsoft Exchange Server 5.5 is available that introduces a new feature that you can use to control how non-delivery reports (NDR) are processed by the Internet Mail Service. After you apply the hotfix that is described in this article, add the SuppressNDROptions registry entry to the following registry subkey. Then, set the SuppressNDROptions registry entry to the appropriate value, depending on whether you want the Internet Mail Service to suppress or deliver NDRs:
A supported feature that modifies the default behavior of the product is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if you are not severely affected by the lack of this feature, we recommend that you wait for the next update that contains this feature.
This hotfix requires Microsoft Exchange Server 5.5 Service Pack 4 (SP4).
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name
After you apply the hotfix that is described in this article, add the SuppressNDROptions registry entry to the following registry subkey and then set the registry entry to the appropriate value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIMC\Parameters To configure the way that the Internet Mail Service processes NDRs: Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
1.Click Start, and then click Run.
2.In the Open box, type regedit, and then click OK.
3.Locate and then click the following registry subkey:
4.On the Edit menu, point to New, and then click DWORD Value.
5.Type SuppressNDROptions, and then press ENTER.
6.On the Edit menu, click Modify, and then follow these steps:
ÂSet the Base type to hexadecimal.
ÂTo enable this feature so that the Internet Mail Service does not deliver NDRs, type 1 in the
Value data box.
ÂTo enable this feature so that the Internet Mail Service does not generate NDRs, type 10 in the Value data box.
ÂTo enable this feature so that the Internet Mail Service does not deliver any NDRs if an SMTP address is missing in the return address field, type 100 in the Value data box.Note If the SuppressNDROptions registry entry is either not present or if the registry entry is set to 0 (zero), the feature is not used.
7.Quit Registry Editor.
8.Restart the Internet Mail Service.For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
For Exchange 5.5 Server Support Click Here.
Monday, November 20, 2006
This first post is on how to use Native Windows backup to backup your Exchange Server.
This article describes how to back up your Microsoft Exchange 2000 or later database using Microsoft Windows Backup Utility. In my line of work, I see far too many exchange servers that have absolutely no back up strategy in place. Out of all the corrupt databases I recover, virtually every recovery could have been avoided if the administrator would have set up an automated backup that ran nightly
Windows 2000 and 2003 Server include a backup utility that becomes updated and capable of performing an online exchange backup after Exchange 2000 has been installed. Backing up your exchange database also flushes transaction logs that have been committed to the database, freeing up disk space. Each transaction log is 5 megabytes and exchange can generate a lot of them depending on how many transactions are taking place. I have seen exchange servers with thousands of unneeded log files. It is extremely important that these log files are not deleted manually. Allow the backup program to flush them.
To backup your exchange server:
1. Click Start > Programs > Accessories > System Tools > and click Backup
2. If backup starts in wizard mode, select advanced.
3. Click on the Tools tab and select “Backup Wizard”
4. On the Welcome screen, click Next
5. Choose Back up selected files, drives, or network data
6. On the Items to Back Up screen, click the plus sign next to Microsoft Exchange Server, then on the name of your server, and then click your storage group (which is named First Storage Group by default).
7. Here you should see the Mailbox store and Public Folder Store are both selected.
8. After clicking next, you will see the Backup Type, Destination, and Name screen. Here you can choose to backup to a device such as a tape drive or to a file as I have chosen here:
9. Click Next.
10. On the Competing the Backup Wizard window, you could click finish to start the job right away. But for this guide we will choose the Advanced button.
11. Be sure the type of backup is set to Normal. Click Next.
12. On the next window you will choose to either append or replace. Keep in mind that if you choose append, the file may grow very large on an automated schedule. If you choose replace, the file will be completely overwritten. I normally choose replace and then setup two alternating backup jobs. This way, I always have a backup file if the server crashes during a backup.
13. Click Next.
14. On the next screen we can choose to run the backup now or schedule it for later. Choose Later.
15. Give the backup job a name. Then click the Set Schedule button. The schedule job settings window appears. You could set your backup to run every weekday at night or whenever works best for you.
16. Click OK.
17. We should be back to the When to Back Up window. Verify the correct start date and click Next.
18. It will then ask you for the proper credentials that this job will run under. Be sure to use an account that has administrative permissions.
19. Click OK.
20. On the Completing the Backup Wizard screen, click Finish to schedule the backup job.
21. Verify the job has been set to run by clicking Start > Programs > Accessories > System Tools > and Scheduled Tasks.
22. You should see your task scheduled with the dates and time to run.
23. You can check on your backup jobs by opening the Backup Utility and going to Tools > Report to view the details of each job. Also check your backup directory to make sure the backup file has been created and the modified date is set to the last backup day.
It is not enough to just create the backup job and trust it will run forever. You need to constantly check that your backup is running. You should also check your event viewer logs to make sure there are no problems occurring during the backup.
This guide is a very simple backup strategy intended for administrators that currently have NO backup strategy in place. Any backup is better than NO backup. I highly recommend that in a mission critical environment, better backup software be purchased and a better backup strategy using both tapes as well as backup files be put into place.
Thursday, September 21, 2006
The Microsoft MVP Guide
to Exchange Availability
10 Essential Rules that Will Save Your Job
Paul Robichaux, Microsoft Exchange MVP
Chris Scharff, Microsoft Exchange MVP
Ben Winzenz, Microsoft Exchange MVP
MessageOne’s Emergency Mail System™(EMS™) provides
guaranteed email continuity. When your Exchange servers
become unavailable, EMS allows users to continue to send
and receive email through a web browser or via a BlackBerry®
wireless device without interruption. Today, more than 700 CIOs at
companies including DaimlerChrysler, Time Warner, and Marriott
depend on MessageOne to ensure that email is always available
– no matter what. Learn more at www.messageone.com/mvp.
Brought to you by MessageOne™
© Copyright 2005 MessageOne, Inc. All Rights Reserved.
It’s a very bad day when Microsoft Exchange goes down.
Unfortunately, achieving high availability with Exchange can be
a daunting task: a wide variety of software, hardware, directory,
storage, network, and datacenter problems are always lurking.
Each one has the potential to bring email down.
MessageOne has seen many causes of downtime: an idiot with
a backhoe cutting the fi ber line, an executive emailing his
7 GB ripped video of a Grateful Dead DVD, termites in the data
center, a night visitor accidentally shutting down power – not to
mention the mundane failures caused by human error, technical
problems, and natural disasters.
This pocket guide provides 10 essential rules that will help
you ensure that email is always available, no matter what. It
was written by three Microsoft Exchange MVP’s to help Exchange
Administrators avoid many of the pitfalls that can lead to
Highly complex availability solutions create new risks that
increase their cost and value. Aircraft engineers have known this
rule for a long time: extra bells and whistles add weight and cost
and sap agility, performance, and maneuverability.
The same is true for your availability solution design.
Instead of larding up your infrastructure with complexity, search
for solutions that reduce the number of failure points by removing
unnecessary components, consolidating functions where it
makes sense to do so, eliminating processes that you don’t
need, and streamlining whatever you keep.
The Zen masters teach that you can only reach Nirvana by letting
go of your possessions; to reach high availability nirvana, you
must simplify in exactly the same way.
01 Simplify, Simplify, Simplify.
02 Know Thy
GI Joe’s motto is "Knowing is half the battle."
That’s as true for Exchange availability as it is for plastic
action fi gures.
Your efforts to build a highly available Exchange system depend
on knowing what failure points exist in your design and what you
can do about them. Some of these failure points will be outside
your control, like security fl aws in the software you run or the
quality of your local utility company’s electrical service. Most of
these lurking enemies, though, are yours to command –
First, you have to know where your infrastructure is vulnerable;
then you have to have the training and knowledge to know how
to best fi x those vulnerabilities without violating Rule #1. For
example, understand the history of your failures and what caused
them – were they SAN-related, related to a specifi c upgrade
process, or something else?
02 Know Thy Enemies
03 Is that a Tool
or a Weapon?
George Washington said that government, "like fi re, is a
dangerous servant and a terrible master."
So it is with the Exchange maintenance tools we depend on to fi x
things when they go wrong. Eseutil and isinteg (and lesser-known
tools available from Microsoft support that you may have heard
of) are wonderfully useful in the right circumstances – but in
untrained hands, or when used for the wrong reasons, they can
irreparably damage your data.
Know what these tools are for, how to use them, and when not to
use them. Don’t experiment with these tools on your production
servers (that’s what Virtual PC is for), and don’t plan on running
them as part of your normal maintenance routines. If you get into
a situation where running these tools seems like a good idea,
stop and think – and consider calling Microsoft’s PSS if you’re
not 100% sure that you’re choosing the right tool for the job.
03 Is that a Tool or a Weapon?
04 Clusters, Not
Clusters are like nuclear weapons: they’re expensive, they
require lots of maintenance, and they don’t solve the problems
most people think that they do. They’re both devastating if
improperly used or secured. Despite this, they are much
If you’re considering using clusters, or if you’ve already got them
deployed, ask yourself whether your cluster implementation
actually delivers the benefi ts you want. Clusters are great at
protecting against single points of hardware failure, and they
make rolling upgrades of the operating system easy. They can
also be used to provide higher availability than standalone
systems when properly designed and used with appropriate
To get the most out of your clusters, carefully study Microsoft’s
recommendations for cluster design and sizing; buy only
hardware that appears as "cluster-certifi ed" on Microsoft’s
hardware compatibility list, and gain experience with cluster
management and setup by using Virtual PC or VMware before
you take the big plunge.
04 Clusters, Not Cluster Bombs
05 Take Care of
Your Spare to
Avoid a Scare
You probably wouldn’t drive your car across the country
without a spare tire.
Likewise, you probably shouldn’t operate your Exchange servers
without a good backup and recovery plan. Backups are your
last-ditch safety net; they can save your data when the protective
mechanisms built into Exchange and your server hardware
have failed you. However, it pays to be sure that your safety net
doesn’t have any holes in it. You, and everyone else on your
messaging team, should be intimately familiar with how your
backup procedures work. Everyone on the team should be able
to do a restore, on demand, of anything from a single mailbox
up to an entire server (including the operating system). The best
way to develop this level of skill is to practice—a lot. Doing so will
build your confi dence level and your skill.
Apart from the question of whether your backups and restores
work is the question of whether they meet your business needs.
Be sure that your restore processes—including media retrieval,
the actual restore, and any post-restore operations—can be
completed during the amount of time you’ve specifi ed as your
recovery time objective (RTO). Also, you need to ensure that
your backup captures all the data you need for a complete
restoration—don’t forget Active Directory, the Windows Certifi cate
Services certifi cate authority, your anti-spam fi lters, and any
other data that you’d need to completely reconstitute your
05 Take Care of Your Spare
to Avoid a Scare
06 Know the
DR and BC
Modern messaging operations impose two requirements: protect
your data (and be able to recover it) and minimize downtime.
They’re related, but not identical, and they have different
requirements that you must know and meet:
• Disaster Recovery (DR) is being able to come back from
a failure, whether large or small. DR may involve restoring
from conventional backups, moving work to another node in
a cluster, or shifting operations to an alternate location. For
example, if your server explodes because someone spilled a
diet Coke in it, and you restore it, that’s DR.
• High availability (HA) is being able to avoid failures in the
fi rst place. RAID, clustering, and redundant power supplies
all provide elements of HA capability. If your server explodes,
and no one notices because its work automatically moves to
another cluster node, that’s HA.
• Business continuity (BC) is being able to keep with some
(possibly degraded) degree of functionality while a disaster
recovery is taking place. If your server explodes and you
switch messaging operations over to your remote data center
or a hosted service while you’re repairing it, that’s BC.
DR is something basic that every organization must implement
to some degree, even if it’s only the "spare tire" level. HA is
something that most organizations choose to implement at some
level; BC is usually what those organizations are trying
06 Know the Difference
between HA, DR and BC
If a tree falls in the forest, does anyone hear it? I don’t know.
I do know that if your server falls over, you’re going to hear
about it when users start calling your help desk—or you—to
complain. Before that happens, you should take advantage of the
monitoring tools built into Windows and Exchange to keep tabs
on your servers’ performance, health, and behavior.
Windows’ basic performance monitoring tools will tell you
when resource usage goes outside of preset limits, and these
indications can give you valuable advance warning of problems.
If you can’t measure your systems’ performance or availability,
you can’t manage to improve it. Watch message fl ow, resource
usage, and uptime to fi gure out where potential weak spots are.
If you depend on non-Exchange servers for message hygiene
or fi ltering, keep an eye on them, too, to make sure that you
get early warning of problems with inbound or outbound
message fl ow.
For large or complex networks, the money you spend on a solid
monitoring package like Microsoft Operations Manager or HP
OpenView will be money well-spent because you’ll be able to
get timely notifi cations of queue buildups, unexpected changes
in disk space usage, and other conditions that can lead to
Exchange problems if not corrected in a timely manner.
07 Monitor, Monitor, Monitor.
Writer and explorer Antoine de Saint-Exupery nailed this rule:
"You know you’ve achieved perfection in design, not when you
have nothing more to add, but when you have nothing more to
As you design your Exchange system, you should ruthlessly
identify and remove every individual single point of failure
(SPOF) that you can fi nd. You may fi nd SPOFs in your physical
infrastructure, your Exchange design, your DNS or Active
Directory confi guration, your processes, or even your people.
(after all, if you have even one irreplaceable person on your team,
what happens when they’re not available?)
The fi rst step to implementing this rule is to identify any area
where you have potential SPOFs (which we defi ne loosely as any
single service, server, or component whose failure can interrupt
your messaging operations). Next, rank the SPOFs twice: once
according to their potential for failure and once according to
the cost of fi xing them. Use these rankings to decide what to
fi x fi rst according to your operational requirements and budget
requirements. Finally, fi x things (at all times being sure to
remember Rule #1!).
08 Ruthlessly Drive Out SPOFs
09 D2D N-O-W
It’s cheap and easy. No, not vending-machine dinners—
The fastest way to back up Exchange data is to use a disk as the
target medium; this gives you much faster backups—and thus
quicker recoveries—than using tapes, at a per-gigabyte cost that
compares favorably with many tape-based solutions. You can
take one (or more, space permitting) disk-to-disk backups, then
selectively write them to tape when it’s convenient. This hybrid
approach gives you fast backups, low overhead, and quick
recoverability, plus long-term archival and storage.
You don’t need any additional software to do this, because
Windows’ built-in ntbackup utility can make disk-to-disk backups
of Exchange right out of the box. Third-party backup utilities
add more fl exible scheduling and a wider range of backup
options, but because the bundled tools give you a cheap way
to get started, you should start investigating how disk-to-disk
technology can improve your backup and recovery processes.
09 D2D N-O-W
Life is all about tradeoffs; the more successful you are at
making the right tradeoffs, the better off you’re likely to be.
This is true for your Exchange design too—picking the right
combination of hardware, software, and design elements makes
it possible for you to have your cake and eat it too.
The type of RAID system you use, the number of physical disks
you use, and the number and size of your database and storage
groups—these factors have a huge infl uence on the balance
between performance and availability in your system. For the
best mix, choose a RAID level that’s appropriate for your recovery
needs (RAID-1+0 is generally best, but RAID-5 is workable in
many environments) and back it with the right number of physical
disks to give you an adequate number of I/O operations per
When you combine the right design principles with good
monitoring and solid backup, you’ll fi nd that your performance
and availability both rise to meet your expectations.
10 Don’t Trade
Performance for Availability
MessageOne’s Emergency Mail System provides guaranteed
email continuity. When your Exchange servers become
unavailable, EMS allows users to continue to send and receive
email through a web browser or via a Blackberry wireless device
No matter what may happen to your physical facilities, data
centers, servers, software, network connectivity, or IT staff,
MessageOne’s Emergency Mail System (EMS) guarantees that
email will always be up and running.
EMS is a Linux-based standby email system that is automatically
synchronized with your primary email environment. In the
event of an emergency or planned outage, EMS can quickly
be activated over the Web or by phone. In less than minute,
selected email users will have direct access to a fully functional
Web-based email account that allows users to send and receive
email from their standard email address. The standby account
includes all of the key features of the primary email system
including contact lists, calendar appointments, distribution lists,
and important historical email.
Today, millions of users depend on EMS at more than 700
companies to ensure that email is always available. EMS is the
only affordable solution to address the shortfalls of tape backup
and traditional mirroring and replication solutions. It is easy to
use, inexpensive, and can be installed in a few hours.
The bottom line: EMS provides guaranteed email continuity – no
EMS includes the following features:
• Guaranteed 60-Second Email Continuity – Activate in less
than 60 seconds to provide any employee with full email &
BlackBerry access during an email outage. EMS ensures that
email never bounces and that email system outages are never
evident to the outside world.
Guaranteed Exchange Availability
• Emergency Access to Historical Email – EMS intelligently
synchronizes historical email to your standby email system
based on your organization’s needs. For example, you can
provide executives with a full email history, managers with
the last fi ve days of email, and other employees with no email
history at all in their EMS inbox.
• Automated Synchronization – Automatically synchronizes
corporate directories, user accounts, contacts, calendars, and
distribution lists to secure SunGard & IBM data centers.
• Designed for Immunity – Linux-based system provides
immunity from viruses and database corruption that may cause
downtime in the primary Exchange environment.
• Quick Recovery – After an outage, EMS automatically moves
all sent and received email back to the primary system in one
step, with all forensic information intact.
Learn why leading companies depend on MessageOne’s
Emergency Mail System to ensure that email is always available.
Visit www.messageone.com/mvp or call 888-367-0777 for white
papers, product information, or to request a web-based demo.
Paul Robichaux is a principal engineer for 3sharp. A well-known
corporate messaging expert, Paul is an MCSE and a Microsoft
Exchange MVP. He is the author of several books, including
The Exchange Server Cookbook (O’Reilly and Associates), and
creator of the http://www.exchangefaq.org Web site.
Chris Scharff is a Senior Systems and Sales Engineer at
MessageOne. Chris, a MCSE and a Microsoft Exchange MVP,
serves as the technical/reviews Editor and Columnist at Microsoft
Exchange & Outlook Magazine and has contributed to a number
of best-selling reference titles on Microsoft Exchange including
the ever popular Nutshell and Pocket Consultant Guides. Chris
holds a Bachelor’s degree from Iowa State University.
Ben Winzenz is a Senior Systems and Sales Engineer at
MessageOne and a Microsoft Exchange MVP. Ben holds a
Bachelor’s degree from Brigham Young University.
About the Authors
Visit www.messageone.com/mvp for direct access to our
Microsoft MVP product resources including:
• "Avoid Exchange Availability Pitfalls" – A whitepaper
by WindowsITPro author Ed Roth that describes the most
common Exchange problems and pitfalls.
• "Why Email Fails" – A whitepaper analyzing real world
Microsoft Exchange failure data.
• "Building the Business Case for High Availability Email" – A
thorough analysis of the economic and business drivers for
high availability exchange architectures.
• "The Paradox of High Availability" – A webinar featuring
Gartner, Inc. analyst Donna Scott discussing the pros and cons
of various approaches to high availability for Exchange and
other Windows applications.
• Direct access to EMS product information.
Visit www.messageone.com/mvp today!
For Further Reading...
11044 Research Blvd.
Building C, Fifth Floor,
Austin, TX 78759