We have one VPS (Windows 2008 R2+IIS7.5), with an asp.net mvc 3 application.
The main question is: how to handle issues when Windows needs to reboot? (after installing Windows Updates or anything else). The goal is to make the website 24/7, but first it's ok to show a message to the users. (we'll be back soon, something like app_offline.htm)
Our application uses SQL and also writes/reads some files (uploaded photos, documents) which are not stored in SQL.
What do you recommend?
- Load balacing with ARR? (with 1+2 servers, but what if the front-end server needs reboot?)
- Windows failover cluster?
- SQL failover cluster?
- What to do with uploaded files?
I really don't know what would be the best (and simplest) solution.