We have a failover cluster that was setup prior to my hire, which I don't think we would be able to rebuild from scratch (a consulting company originally set it up). Both nodes are running in a VM environment with nightly snapshots, and the database also has it's normal database-level backups running as well.I'm relatively new to VM's, but my organization has seen great reliability to-date on all of our database instances running as 1-instance per VM. I'm a fan of simplicity, and here's my question: There's an organizational push to move all databases into this cluster as they're upgraded to MSSQL 2014 (everyone is always a fan of uptime, right?), but the applications are not necessarily meeting the criteria of always needing to be up. My gut is telling me to keep everything in a 1-instance per VM setup if some downtime is acceptable. I'm not allergic to new tech, but I'm not sure yet how much tougher it is to manage a cluster when problems arise. Does anyone have some advice on the difficulties surrounding their clustering environments? I'm concerned about pushing more databases into a cluster that I might not be able to support.--=Chuck
↧