I just wrote couple of questions which I thing is good for a consultant to think about when architechting for a disaster recovery solution or high availability solution.

Do you realize that your messaging system poses a critical business resource?

What would happen to business processes in the event of a major disruption to their message system?

What are the High Availability options you would like to have?

Have you defined the boundaries between disaster recovery and high availability? (When the scope, type or number of failures exceeds then it is defined as a disaster recovery situation)

Have you;

1. Defined the business requirements?
2. Identified the options that can meet the requirements?
3. Determining the costs associated with each reasonable option?
4. Established “Service Level Agreements” (SLAs) with each dependency to validate the availability (Active Directory, Domain Name System, TCP/IP network, storage sub-system, Backup services, Monitoring services, Datacenter infrastructure (power and air conditioning))

Is the availability goals are aligned with the business goals?

Defined Recovery point objective

Defined Recovery time objective

The sample list of failure classes is:

1. Single mail item lost
2. Single mailbox lost
3. Database lost or corrupted
4. Disk failure
5. Disk volume failure or corruption
6. Storage unit failure
7. Server failure
8. Network connectivity lost
9. Datacenter failure

Is there a monitoring system in your solution?

I have tried to reduce the content but my mind was not obliged to it....

1. http://www.microsoft.com/exchange/evaluation/overview/default.mspx
2. http://www.microsoft.com/exchange/evaluation/features.mspx
3. http://www.microsoft.com/exchange/evaluation/sysreqs/default.mspx
4. http://www.microsoft.com/exchange/evaluation/clients.mspx
5. http://www.microsoft.com/exchange/evaluation/topquestions.mspx
6. http://www.microsoft.com/exchange/evaluation/editions.mspx
7. http://www.microsoft.com/exchange/partners/default.mspx
8. http://www.microsoft.com/exchange/evaluation/features/ex_compare.mspx
9. http://www.microsoft.com/exchange/evaluation/languages.mspx
10. http://www.microsoft.com/exchange/evaluation/featurecomparison.mspx
11. http://www.microsoft.com/technet/prodtechnol/exchange/2003/topten.mspx
12. http://www.microsoft.com/exchange/evaluation/news/default.mspx
13. http://www.microsoft.com/exchange/evaluation/compare/default.mspx
14. http://www.microsoft.com/exchange/howtobuy/licensingfaq.mspx
15. http://www.microsoft.com/exchange/howtobuy/default.mspx
16. http://www.microsoft.com/exchange/evaluation/upgrade/upgradingto2007.mspx
17. http://www.microsoft.com/exchange/evaluation/features/admin.mspx
18. http://www.microsoft.com/exchange/evaluation/features/businesscontinuity.mspx
19. http://www.microsoft.com/exchange/evaluation/features/mobileaccesswp.mspx
20. http://www.microsoft.com/exchange/evaluation/features/unifiedmessaging.mspx
21. http://www.microsoft.com/exchange/evaluation/features/calendarconcierge.mspx
22. http://www.microsoft.com/exchange/evaluation/features/anywhereaccess.mspx
23. http://www.microsoft.com/exchange/evaluation/features/serverroles.mspx
24. http://www.microsoft.com/exchange/evaluation/outlooktogether.mspx
25. http://www.microsoft.com/exchange/evaluation/compliance/compliance-tour.mspx
26. http://www.microsoft.com/exchange/evaluation/security/security-tour.mspx
27. http://download.microsoft.com/download/f/c/c/fccf22eb-30df-4471-92ce-452abfd4e565/Exchange_Server_2007_Data_Sheet.pdf
28. http://download.microsoft.com/download/9/9/c/99c1fe21-9156-4ef6-bc41-

More than dozan way to learn on Exchange Server 2007

Though it was released to manufacture and the launch in the local sector is nearby door step, I was wondering how we can bring the message to the people who are just about to break their "virginity" in messaging.

As we all agree the local sector is not fully "technology(est)" like Singaporean people. So, we needed a better way to spread the word -

"see guys if you use this way of messaging, you can reduce the total cost of ownership and reduce the IT managers burden.....etc;"

But, before teaching or launching the product and the technology we need to learn and demonstrate to the in-house mates.

While I was reading and installing and troubleshooting (which I never expected in my new VISTA tabletPC), it was really really cool to see how Exchange 2007 actually works, in a disastrous situation.

This product was developed to "ERASE"(not ease) the IT management burdens. It's so simple and works to perfection, you can simply install, correctly configure and even the monitoring can be automated.

Thanks Microsoft - Exchange Team and PowerShell - You guys will be in my heart always.