Using an instance in a failover cluster as a witness server

Firstly I absolutely hate the idea of doing this with a passion . . . and then some, in my mind a witness server should have as few if not zero dependencies on any other SQL Server HA technology as possible, it should be a stand alone SQL Server instance.
However, technically would you be able to use an instance which is already in a failover cluster as a witness for a mirrored pair of databases ?.

Yes you can use cluster instance as witness.
https://msdn.microsoft.com/en-IN/library/ms191309.aspx

Similar Messages

  • SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

    I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
    I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
    Node1: DB Engine 1 (named instance DB01)
    Node2: DB Engine 2 (named instance DB02)
    Node3: Analysis Services (named instance DBAS)
    Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
    Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
    required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
    in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
    through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
    R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
    Thank you much for reading. I appreciate any help to get this resolved.
    POSSIBLY NOT RELEVANT...?
    I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
    as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
    help solve the issue.

    When connecting to SSAS in a cluster, you do not specify an instance name.  In your case, you would use the name of the SSAS IP address to connect.
    See:
    http://msdn.microsoft.com/en-us/library/dn141153.aspx
    For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
    SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
    instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
    "SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
    How to Cluster SQL Server Analysis Services for more information and examples.

  • Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

    I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

    Hi KamarasJaranger,
    According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
    and refer to the
    PDF file.
    1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
    2.Discover target portals.
    3.Connect targets and configuring Multipathing.
    4.Initialize and format the Disks.
    5.Verify the Storage Replication Process.
    6.Run the Failover Cluster Validation Wizard.
    7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
    8.Tune Cluster Heartbeat Settings.
    9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
    10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
    11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
    12.Test application connectivity.
    Regards,
    Michelle Li

  • Quorum location for Failover cluster file share witness

    So, I've done quite a bit of searching for what I'm about to propose and I've been able to find nothing.
    I currently have a multi site failover cluster hosting separate 2-node SQL clusters at each site connected through an Availability Group.  For the failover cluster I am using a file share witness hosted on a server at the primary site.  Both sites
    are built entirely on vSphere 5.5 and have full replication for the production servers.  If the primary site goes down (disaster), I'll need to force quorum in the secondary site to a new file share witness.
    Well, I got to thinking...
    Why not just replicate the server hosting the file share?  I completely understand the reasoning behind not putting the file share witness on DFS, but a replicated virtual server, why not?  If the primary site fails, the replicated server hosting
    the file share witness is brought online with the rest of the production servers in the DR site.  In that case, the only thing that changes is the server IP address, but ultimately, the server name and share where quorum is hosted all stays the same.
    Ultimately this prevents needing to find a 3rd geographical/cloud location to host a quorum/witness at.  I can't imagine it's this "simple", but maybe it is.  If this is possible, and there's not something I'm missing, this essentially
    makes the quorum file share witness site agnostic, meaning it could live or be moved anywhere that replication is allowed.
    Ideas, thoughts?  Am I missing something?
    Thanks!
    Chris Miller

    Most likely it would be better to put this question to the High Availability forum -
    https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverClustering
    But, might need a more complete definition of your environment.  Are you saying that you have multiple 2-node clusters, each with one node in the primary and the second node in the DR site?  And you have a single file share server located in primary that
    is used to host the file share witnesses for all these clusters?  You want to use VMware to replicate the file share server to the DR site so that it can be made available should the primary site fail?
    It should work, but it will not be automatic.  After all, the replicated VM will need to be brought online at the DR site so the SQL cluster will recognize it.  That is not an automatic process.  So the cluster will be down until
    you bring the file share server online so it can be recognized.  Not a whole lot different that simply forcing the DR SQL host to run without quorum.
    . : | : . : | : . tim

  • OC4J Instances in Cold Failover Cluster

    I'm running OAS 10.1.2.2.0 on a windows 2003 server under a cold failover clustered environment and was wondering... Is it recommended to have one web application deployed in it's own separate instance? For example, webapp1 deployed to instance1 and webapp2 deployed to instance2? Or would it be better to have multiple web applications deployed to one instance?
    Thanks for any thoughts!

    user7575753 wrote:
    I'm running OAS 10.1.2.2.0 on a windows 2003 server under a cold failover clustered environment and was wondering... Is it recommended to have one web application deployed in it's own separate instance? For example, webapp1 deployed to instance1 and webapp2 deployed to instance2? Or would it be better to have multiple web applications deployed to one instance?
    Thanks for any thoughts!I can say your configuration is ok for single instance failover . Once u like to make cluster and load balance , OAS hs managed and non-managed cluster.
    For Managed Cluster , you must setup either Oracle WebCache or F5 Big/IP . With regard to non-managed cluster, that means nothing required to share .

  • Failover Cluster Manager - Partioned Networks Server 2012

    Hello,
    I have a DR cluster that I am trying to validate. It has 3 nodes. Each has a teamed vEthernet adapter for Cluster Communications and Live Migration. I can start cluster service on 2 of the 3 nodes without the networks entering a partioned state. However,
    I can only ping the I
    Ps for those adapters from their own server . Also, It doesn't matter which 2 nodes are brought up. Any order will produce the same results. Validation gives the following error for connections between all nodes:
    Network interfaces DRHost3.m1ad.xxxxxx.biz - vEthernet
    (vNIC-LiveMig) and DRHost2.m1ad.xxxxxx.biz - vEthernet (vNIC-LiveMig) are on
    the same cluster network, yet address 192.168.xxx.xx is not reachable from
    192.168.xxx.xx using UDP on port 3343.
    Update: I have created a specific inbound rule on the server firewalls for port 3343. The networks no longer show as partitioned. However, I still receive the same errors about communication on port 3343 to and from all nodes on the LiveMig and ClustPriv
    networks. Any help would be appreciated.
    Brian Gilmore Lead IT Technician Don-Nan Pump & Supply

    Windows IP Configuration
       Host Name . . . . . . . . . . . . : DRHost1
       Primary Dns Suffix  . . . . . . . : m1ad.don-nan.biz
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : m1ad.don-nan.biz
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 14-FE-B5-CA-35-6C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::609a:8da3:7bce:c32f%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1091894965
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-14
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::2481:996:cf44:dc3d%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-15
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f884:a35d:aa43:720e%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3 - iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4 - iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.23(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 14-FE-B5-CA-35-6C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::609a:8da3:7bce:c32f%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.113(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1091894965
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-14
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::2481:996:cf44:dc3d%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-15
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f884:a35d:aa43:720e%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-58-CA-14-FE-B5-CA-35-6E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3 - iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4 - iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.23(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : DRHost3
       Primary Dns Suffix  . . . . . . . : m1ad.don-nan.biz
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : m1ad.don-nan.biz
    Ethernet adapter vEthernet (VM Public Network):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : D0-67-E5-FB-A2-3F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9928:4d4f:4862:2ecd%31(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.9.115(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 192.168.9.119(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.9.1
       DHCPv6 IAID . . . . . . . . . . . : 1104177125
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : 192.168.9.21
                                           192.168.9.23
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter vEthernet (vNIC-ClusterPriv):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-18
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::3d99:312c:8f31:6411%32(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.108.33(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1258298840
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter vEthernet (vNIC-LiveMig):
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
       Physical Address. . . . . . . . . : 00-1D-D8-B7-1C-19
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d859:b18a:71d6:8cef%33(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.109.33(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 1358962136
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F2-3C-E0-D0-67-E5-FB-A2-43
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI3-iSCSI1:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #49
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-60
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.26(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter BC-PCI4-iSCSI2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57711 NetXtreme II 10 GigE (N
    DIS VBD Client) #50
       Physical Address. . . . . . . . . : 00-0A-F7-2E-B5-62
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.107.27(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Brian Gilmore Lead IT Technician Don-Nan Pump & Supply

  • Transactional replication from a failover cluster instance to a SQL Server Express DB

    Hello,
    I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
    two instances DB's which both reside on nodes of the cluster.
    Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
    1) Should the distributor need to live on a separate instance?
    2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
    inconsistency between the publisher and subscriber.
    There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
    Thanks in advance.

    1) Should the distributor need to live on a separate instance?
    Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
    2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
    inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
    Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online. 
    Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required.

  • Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

    I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
    Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
    When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
    Any suggestion on resolving this problem?
    Thanks
    Ikad

    Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
    Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
    Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
    to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
    Ikad

  • Failover Cluster in a box

    Hi,
    I'm in the process of building a test environment which requires a failover cluster for a SQL Server Always on configuration of 2 DB nodes. I have a single Windows 2012 R2 host server with Hyper-V installed and my guest OS's configured using local storage
    on this server. 
    In order to create the guest failover cluster, I need to create a Quorum drive - which needs to be shared between the two DB nodes. Using only this physical host server and it's local storage, is this possible to achieve?
    I believe that options for creating a shared VHDX disc are to host it on a CSV or a Scale out file server, but both of these seem to require the creation of a cluster themselves, which will require a Quorum disc on shared storage itself!
    Thanks, 
    David

    Hi,
    I'm in the process of building a test environment which requires a failover cluster for a SQL Server Always on configuration of 2 DB nodes. I have a single Windows 2012 R2 host server with Hyper-V installed and my guest OS's configured using local storage
    on this server. 
    In order to create the guest failover cluster, I need to create a Quorum drive - which needs to be shared between the two DB nodes. Using only this physical host server and it's local storage, is this possible to achieve?
    I believe that options for creating a shared VHDX disc are to host it on a CSV or a Scale out file server, but both of these seem to require the creation of a cluster themselves, which will require a Quorum disc on shared storage itself!
    Thanks, 
    David
    You can run a guest VM cluster on your single node no problem! You can spawn a third VM and expose SMB3 share (or iSCSI target LUN with a CSV on top of it if you want to run old-school) and put your shared VHDX there. See:
    Virtualization: Hyper-V and High Availability
    http://technet.microsoft.com/en-us/magazine/hh127064.aspx
    "You can also cluster the virtual machines (VMs) themselves (“guests”) on a single host. Using virtual networks for heartbeat and virtual iSCSI for the quorum and other
    attached storage lets you create guest clusters, even if the host hardware wouldn’t normally support it."
    StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Exchange 2013 DAG - Failover Cluster Warnings

    I have two new Exchange servers (PROD1 and DR1) that I recently updated to CU8 in preparation for going into production.  After reboots, I noticed that I had a warning on the "Server Manager" window.
    PROD1 lists itself, DR1, and DAG1 as servers though it marks DAG1 as not accessible.
    DR1 lists only itself and PROD1.  It does not list DAG1.
    PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
    In the Failover Cluster Manager of each server, the object of DAG1 is listed as "Offline".  It has two IPs - one for each of the Exchange servers' subnets (this is where I think I screwed up).  The IP for PROD1's subnet is 10.2.8.131
    and is "Failed" and the IP of DR1 is 10.4.8.131 and is "Offline".  The IP of PROD1 is 10.2.8.132 and DR1 is 10.4.8.132.
    Attempts to bring the cluster object online fail "due to the failure of one or more provider resources".
    The instructions I followed to set up the DAG did not mention the need for multiple NICs.  I now think this is incorrect and would be willing to use separate subnets and NICs for the DAG if necessary.  (I could use 10.2.12.X and 10.4.12.X instead.)
    I am currently still able to fail the database copy between DR1 and PROD1 without any problems.

    Hi Jkm,
    As you said :PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
    I suggest you post failover cluster errors to
    [email protected] for our troubleshooting.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Moving VMs from Standalone Hyper-V to Hyper-v Failover Cluster

    Hello All.................I need to move Virtual Machines from Standalone Hyper-V based on Windows Server 2012 R2 to a Hyper-V Failover Cluster based on Windows Server 2012 R2.
    -  The VMs OS is Windows Server 2012 R2
    -  Applications installed on VMs are SCCM, SCOM, SharePoint, etc.
    1.  I am looking for a Checklist that I can run through and move them.  To make sure I do not miss out anything.
    2.  Would a downtime be required in this scenario while the VM is being moved?
    3.  What requires special attention in this scenario?

    Thanks for the reply.
    So, I do not need to do anything and just simply add both the cluster and standalone into VMM and then simply use the Move option.  Please, confirm if I have understood it correct.
    Yes. But be carefull. First shut down your VM's
    if possible and configure them in such a way they don't automatically start. If you install the SCVMM Agent, some Hyper-V related services are restarted, when some VMs start during that process you system may stall. I have seen this multipe times.
    There is another dirty option that worked of us perfectly. Export the VMs. Then import those VMs to a local disk on one Hyper-V Server. Refresh the Hyper-V Server and Virtual Machines on that Hyper-V Server. Give it a few minutes. Then do
    a Live Migration while at the same time makeing it "Highly Available" by moving it to your CSV. Works flawlessly. DO NOT IMPORT THE VMS TO YOUR CSV, otherwise you can't change it to "Highly Avaiable" unless you have
    two CSVs. Importing it straight to a CSV does not make them Highly Available.
    Boudewijn Plomp | BPMi Infrastructure & Security
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

  • Ghost VM resources under failover cluster manager roles

    Hello, everyone,
    I had a Windows 2012 R2 hyper-v host with few VMs running on it. I deployed a second host, and using SC VMM created a failover cluster. Also I added a shared cluster volume and migrated all VMs to the shared storage using SC VMM console. In
    the process I also checked the checkbox to make the VM highly available. Everithyng worked fine.
    Now when I look in to Failover Cluster Manager console I see some "ghost" vm roles. Their names are correspondend to the names of the running VMs, which I also can see in the console. For example I have vm HDCADC01, there is another
    role in the console "SCVMM HDCADC01 Resources", the status  is off, settings are empty.
    Does anyone knows what are these resources? Is it somekind of glitch during the migration? Is it safe to remove them?
    Thank you,
    Jamal.

    Where should I run this command?
    On my VMM server Update-clustervirtualmachineconfiguration command complains that The cluster services is not running.
    On the one of hyper-v server, cluster nodes, "get-vm -name  hdcadc01" returns "Get-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name hdcadc01". The same result is when I used "ghost" resources name.

  • Change "Services and applications" names in failover cluster manager

    Hi. Id like to change "Services and applications" names in failover cluster manager for Windows Server 2008 R2.
    I right click on one and press rename, but when i change the name and press enter i get the message "To rename this service or application please rename the Client Access Point via its property page"
    It's important that we don't change the network name for the service

    Hi,
    Checkout this blog post
    PowerShell for Failover Clustering: Let’s Rename a Few Things
    But keep in mind if you rename the resources and you are using them in a script or backup you need to check this also with the new name.
    Greetings, Robert Smit Follow me @clustermvp http://robertsmit.wordpress.com/ “Please click "Vote As Helpful" if it is helpful for you and Proposed As Answer” Please remember to click “Mark as Answer” on the post that helps you

  • Adding more RAM to all 3 nodes in a hyperV failover cluster, re-validate config?

    No issues with 2012 R2 also. Just add the ram and you will be fine.

    hey spiceheads,
    I have a 3 server node hyper-v failover cluster running hyper-v server 2012 R2.
    two of the servers have 96gb and the other 120gb.  Going to even all three servers to 128gb.
    Once this is done do I need to re-validate?  If so, re-validation would take my cluster completely off-line, correct?
    Thanks,
    ceez
    This topic first appeared in the Spiceworks Community

  • Failover cluster node - You do not have administrative privileges on the server 'servername' ?

    Hi Hello & Good morning Technet's,
    I would like to post a question which i really expecting a solution.
    I got 2 domain in one single forest.
    Domain 1: hg.corp
    Domain 2: iac.corp (iac.corp
    is a tree domain under hg.corp forest)
    Trust : Transitive
    trust between hg.corp and iac.corp
    Domain controller 1: dc.hg.corp
    (for hg.corp)
    Domain controller 2: iacdc.iac.corp
    (for iac.corp)
    I want to make a Fail-over cluster between this 2 domain controllers ( But both are in different domain literally, but in same forest )
    Process Validate cluster in dc.hg.corp
    dc.hg.corp can added, but iacdc.iac.corp failed (Error: You do not have administrative privilages on the
    server 'iacdc')
    Process Validate cluster in iacdc.iac.corp
    iacdc.iac.corp can added, but dc.hg.corp failed (Error: You do not have administrative privilages on the
    server 'dc.hg.corp')
    Technet please provide me a solution for this issue, So i can reduce server box counts.
    Thank you & Have a nice day.
    Shamil Mohamed

    Hi,
    We do not support combining the AD DS role and the failover cluster feature in Windows Server 2012.
    This behavior is by design.
    The related KB:
    You cannot add a domain controller as a node in a Windows Server 2012 failover cluster environment
    http://support.microsoft.com/kb/2795523
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for