Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4532

Windows Server Failover Cluster, failover cluster instances and Always On HA, in a nutshell: everything

$
0
0

 

Hi all of you,

My goal is trying to grasp all the knowledge as well as all the ins and outs behind one Always On HA along with Failover Cluster Instances atmosphere. At home.

 

Before proceeding, could you please be so kind to tell me if I've got all the pieces needed for that??

  • Machine 1 (Architecture: x64.). It runs Windows 7 Ultimate Pro OS and runs 4 instances: Sql2k8Express, Sql2k8 R2 and Sql2k12 (Enterprise Evaluation 180 day, solid state disk, 16 Gb RAM and so on, good one. This machine runs a Domain Controller based on Windows Server 2012 DataCenter Evaluation 180 days in my VM VirtualBox platform along with one Sql2k16 CTP3 Evaluation Edition.
  • Machine 2 (MacBook), up to the moment only using NAT internet connection for consuming internet data. This one goes on your own way. In a future I would like to attach to my virtualized Windows Server 2012 domain controller. No worries up to the moment.
  • Machine 3 (Architecture x32). It does runs Windows 7 Ultimate Pro OS connected beatifully to the former virtualized 2012 domain controller. Runs a couple of Sql instances, Sql2k8 and Sql2k5.
  • Machine 4 (Architecture x64), runs a Windows 7 Pro, no Sql Server instances installed, only MongoDb server.

Having in mind the aforementioned facts, can I deploy one Failover Cluster Instance from Machine 1 (VirtualBox one) adding as second node, Machine 3?

Must be a 2008/2012 server? I mean, the second node.

I don't know if I've been sufficiently clear on my request, let me know…

Thanks in advance for any input/advices provided


Viewing all articles
Browse latest Browse all 4532

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>