I'm deploying 2 host-servers (PowerEdge R200) to host our company DNN website (and to host the server application of our software package).
I'm building the following setup (Visio drawing is amateuristic, I'm not a professional system administrator: the 3 "grouped" guests represent a singel Windows Server 2008 R2 install, which act as a Domain Controller, Webserver and SQL Server):
IP Addresses are incorrect by the way and don't mind the "CLUSTERED" label at the SQL Servers, I'm not clustering since I don't have shared storage.
The setup loadbalances incoming traffic with Keepalived (round-robin) on a Debian guest between Production Guest #1 and Production Guest #2.
The setup has been build and SQL Server 2008 Enterprise have been installed on all systems.
At this point I'm trying to decide on how to configure the SQL servers.
At first I thought I'd use Peer-to-peer transactional replication between the SQLServer#1 and SQLServer#2, so both servers would be able to run completely independant of eachother, should this be needed.
I did find some posts however stating that SQLReplication isn't recommended for usage with DNN. These are quite old posts though and I understand Peer-to-peer replication has been improved a lot in SQL Server 2008 (in comparison with SQL 2005).
I'm not knowledgeable enough on neither SQL nor DNN to decide wether this combo would be any good.
Advice on this matter would be appreciated, since I doubt if I'm heading in the right direction with this setup.