Cluster existing R2 server with multiple instances?


i have existing server 1+ years old 5 instances.  i received notice hardware genie visiting company second node server.

experienced in win2003/sql2005 clustering.  this win2008 , sql 2008 r2  server components.

my plan idea make dns entry node1 data name of cluster.  in true cluster still reference instances via clusername\instancename ?   fake dns entry mycluster.  

mycluster\erpprod

mycluster\inhouseprod

or clustering different respect instances?  

as tweak code on to mycluster\erpprod can set up mycluster cluster after drop fake dns.

does make sense?    

 

so have standalone single server 5 non-clustered sql server 2008 r2 instances? , want move instances new cluster on new hardware or want rebuild existing server, combine new server build 2-node failover cluster?

from application server point of view, clustered sql server named instance (sql2k, sql2k5, sql2k8, sql2k8r2 ,sql2012, sql2014) on w2k, w2k3, w2k8, w2k8r2, w2012, w2012r2 similar in use cluster group network name\sql server instance name format in connection string. default sql server instances use cluster network name.

the cluster group network name network name each clustered sql server instance. in w2k8/w2k8r2 services , applications groups. in w2012/2012r2 "server name" under roles.



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group