A
adam_jjz
I've seen everybody's using third party solutions to control the failover process, but I can't find anybody tried this setup:
- 2 nodes Exchange 2010 (all Exchange components run on single box)
- DAG with static ip, and fqdn (192.168.2.10/cluster.home.local)
- CAS array named cluster.home.local
- Outlook points to cluster.home.local
I have successfully tested it in my lab, and it seems it is flawless. It takes about 30s to mount databases to the secondary box, and about 5s for the DAG ip to fail over. I couldn't find any flaws in it, and it is seamless. Am I missing something, or is it cheapest solution for small shops?
All comments are appreciated.
Thanks
- 2 nodes Exchange 2010 (all Exchange components run on single box)
- DAG with static ip, and fqdn (192.168.2.10/cluster.home.local)
- CAS array named cluster.home.local
- Outlook points to cluster.home.local
I have successfully tested it in my lab, and it seems it is flawless. It takes about 30s to mount databases to the secondary box, and about 5s for the DAG ip to fail over. I couldn't find any flaws in it, and it is seamless. Am I missing something, or is it cheapest solution for small shops?
All comments are appreciated.
Thanks