I am looking to implement WSS 3.0 in a high availability enviroment. High utilization is not really an issue. I am more worried about uptime. My solution to this would be to have the following
1. Two internet providers
2. Two Cisco ASA Firewalls (Cisco1, Cisco2)
3. Two Physical Servers (Server1, Server2)
4. Two Virtual Servers on Each physical Server, running Esx 3.5, W2k8, SQL 2008
5. Server1 would run a VM for the WSS Front End and the other for SQL 2008
6. Server2 would run a VM for the WSS Front End and the other for SQL 2008
7. Both Front End VMs would be in the same farm
8. I was hopeing to mirror the SQL 2008 with automatic fail-over?? I hear that is a new feature in 2008 (in regards as "automated").
9. The Ciscos would be setup in a way in which:
A. Both have different internet providers.
B. Cisco1, Cisco2 are uplinked together through the LAN
C. Two network interfaces on each server.
D. Server1 interface on the DMZ of Cisco1 with a Public IP, and the other on Cisco2 with NAT and port forwarding of 443.
E. Server2 intraface on the DMZ of Cisco2 with a Public IP, and the other on Cisco1 with NAT and port forwarding of 443.
I am not use to creating such a high availability enviroment and looking for any suggestions. With the solutions I provided, I would think I could handle multiple points of failure (internet, router, server, etc), with a simple DNS change, which I could have monitored and outsourced.
I am not too familiar with SQL, let alone mirroring, so that is my biggest concern. The goal is to have one the other SQL go online automatically when the other fails. When the failed SQL comes back online, I want that to be seemless as well and I want all data to be replicated from the server with the most current database. Is this possible?
I was also looking at a solution from DocAve for high availabilty.
I appreciate all the help!