In Failover Cluster 2008 mailbox2 server network status Unavailable (down).

Hi 
I am new here, & hope i can get some help for the below issue
let me keep it simple scenario 
i have 2 mailbox server ( mbx01 & mbx02)
2 cashub Server ( cshb1-cshb2) all running on hyper-v. last week due to some maintenance in data center i have to bring down all the production environment, once the thing are fixed in DC , i started all the server and found out that my exchange node 2 database
are failed.
In exchange 2010 failover cluster node ( node2 ) is down network status unavailable. due to by exchange node2 database are failed.
also i cannot access the file share witness directory from any of the above server.
can any body assist me on this please 
thank you 

Make sure both the DAG members have access to the witness directory. Check the location and make sure you have access. Open the DAG properties from Node2 and try to update the witness server and witness directory. Check the firewall/antivirus of the witness
server. Try disabling antivirus and firewall. If witness server is not online your databases will go offline. Pleae check
this
Get-DatabaseAvailabilityGroup -Identity DAG -Status | fl name,servers,witnessserver,witnessdirectory,alternatewitnessserver,alternatewitnessdirectory,operationalservers,primaryactivemanager,witnessshareinuse
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

  • Failover Cluster 2008 R2 - VM lose connectivity after live migration

    Hello,
    I have a Failover Cluster with 3 server nodes running. I have 2 VMs running in one the the host without problems, but when I do a live migration of the VM to another host the VM lose network connectivity, for example if I leave a ping running, the ping command
    has 2 response, and 3 packets lost, then 1 response again, then 4 packets lost again, and so on... If I live migrate the VM to the original host, everything goes OK again.
    The same bihavior is for the 2 VMs, but I do a test with a new VM and with that new VM everything Works fine, I can live migrate it to every host.
    Any advice?
    Cristian L Ruiz

    Hi Cristian Ruiz,
    What your current host nic settings now, from you description it seems you are using the incorrect network nic design. If you are using iSCSI storage it need use the dedicate
    network in cluster.
    If your NIC teaming is iconfigured in switch independent + dynamic, please try to disable VMQ on VM Setting for narrow down the issue area.
    More information:
    VMQ Deep Dive, 1 of 3
    http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
    I’m glad to be of help to you!
    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.
    Hi!
    thank you for your reply!
    Yes, We are using iSCSI storage, but it has its own NICs for that (2 independant NIcs just to connect the server with the storage) and they are configured to not use those NICs to cluster communication. The team configuration is just for the LAN connectivity.
    The NIC teaming is configured using BACS4 software from a DELL server and in Smart Load Balancing and Failover (as you can see here
    http://www.micronova.com.ar/cap01.jpg). The link you passed is for Windows Server 2012 and we are running Windows Server 2008 R2, BUT as you can see in the following capture the NICs has that feature disabled
    ( http://www.micronova.com.ar/cap02.jpg ).
    One test that I'm thinking to do is to remove teaming configuration and test just with one independant NIC for LAN connection. But, I do not know if you think another choice.
    Thanks in advance.
    Cristian L Ruiz
    Sorry, another choice I'm thinking too is to update the driver versión. But the server is in production and I need to take a downtime window for test that.
    Cristian L Ruiz

  • Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

    We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
    I've been searching for a "best practices" article for this but have been coming up short.  The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
    to different hardware without failover cluster volumes.
    If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
    Currently, my approach is as follows:
    1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
    2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
    3. Stop the VMMS service on the 2008 r2 hostnodes
    4. copy the virtual machine files and folders over to the new failover cluster volumes
    5. Import vm's into server 2012 r2 hyper-v.
    Any feedback on the opertain I have in mind would be helpful.
    Thank you,
    Rob

    Hi Rob,
    Yes , I agree with that "file copy " can achieve migration.
    Also you can try "copy cluster wizard " :
    https://technet.microsoft.com/en-us/library/dn530779.aspx
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Active-Passive Failover cluster in Windows Server 2008 R2

    Hi,
    As per the client requirements, I build an active-passive Oracle 11g R2 database cluster in Windows Server 2008 R2.
    (Used Microsoft cluster as Client don't have Fail Safe licence)
    As per the configuration, I follow the below mentioned steps:
    a)OS vendor configured Active-Passive Windows Cluster
    b)Installed Oracle 11g R2 on both the nodes with same ORACLE_HOME name
    c)Create Listener and configured it with cluster IP in Node1
    d)Create Database from Node1. Physical files location are all in Storage
    e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2
    f)Configure Listener with the same Oracle SID.
    g)Test database failover from Node2 with Listener registration
    h)Open the Windows Failover Manager to configure the Oracle Database and Listener Service in the Cluster Group
    Now I am facing problem by moving Cluster Group movement. Whenever trying to moving the group, Listerner service is not getting up by Cluster Manager as quorum is not included in the group and that quorum disk is not moving in the failover node with the Oracle Cluster Group. As per my understanding Quorum having information of Cluster IP which has been configured with Listener.
    But when I am shutdown one node, then in the other node all the resources successfully moving and cluster able to online all the resources. I guess at that time Quorum is also moving and thus cluster can able to make Listener online.
    Please suggest how to resolve this issue. Means how can I make Listener up instead having any dependencies with Quorum in the fail over node?
    Thanks a lot for your help.

    hello
    I was going through your post and i am also doing the same thing here at our organisation for Oracle 10g R2
    Can you pls send me any docs u r having for configuration of Oracle in windows clusters .
    And, can you pls elaborate on this point
    e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2.
    Pls send me the details at [email protected] or you can contact me at 08054641476.
    Thanks in advance.

  • Failover did not happen when network switch went down!!! PLEASE HELP

    Hi gurus,
    Yesterday one disaster struck my RAC database. We have two node cluster and it is 10.2.0.2, both of them located in different sites, yesterday suddenly power went down and the one of the network switch went down and got destructed, node one of RAC database was connected to that switch, but the failover did not happen to the node two as this should be the case when one node goes down the other should be available for all the node one sessions/connections.
    when I tried to ping/telnet the node 1, it was not happening because the switch was down, the network guyz connected the cables to other switch available. When I connected to the node 1, it was showing "Oracle is not available" message.
    And when I tried the other node, it was the same case but I did not see any error in alert log file. Then my TL restarted both the nodes and then the database was available.
    I am very confused that how the failover did not happen and how the database went down, PLEASE suggest something to how to identifiy what was happened. Thanks & Regards
    Edited by: user1221 on Mar 18, 2009 1:09 AM

    About Oracle RAC ... you have 2 nodes ... You have to connect 4 IPs.
    I mean
    - IP public node1
    - IP public node2
    - IP Virtual node1
    - IP Virtual node2
    When node1 down
    You can not ping "IP public node1", but you should ping "- IP Virtual node1", because it should up on node2.
    But not bind 1521 port.
    Idea about failover
    you have to create new difference Service...on RAC Database!
    and on your client have to set TNS to on failover and balance (if you used OCI), you can use TAF feature
    Example:
    DB =
    (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = db01-vip)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = db02-vip)(PORT = 1521)) (FAILOVER=ON)(LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = NEW_SERVICE_DB) (FAILOVER_MODE = (TYPE = SELECT) (METHOD = BASIC) (RETRIES = 180) (DELAY = 5))))
    If you use JDBC, can not use TAF.
    Anyway, I suggest you read more about RAC on http://otn.oracle.com/rac and http://oracleracsig.org
    Good Luck

  • OS/hw based failover cluster for WebLogic Server 9.2 Standard Edition

    Hi
    Is it possible to run WebLogic Server 9.2 SE on OS/hardware based cluster?
    I want to get an simple failover environment on a cluster of 2 nodes (active-passive).
    Oracle Database can be run in such scenario with one license with a limit of up time for passive instance.
    Is it the same with WLS licences?
    Regards
    WD

    The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
    Regards,
    tom
    Edited by: TomB on Sep 17, 2010 2:33 PM

  • Configure Hyper V Failover Cluster on Window Server 2012 R2

    I have 3 node cluster of hyper v and configured csv all machine working fine but after run backup machines get paused, so i have removed backup agent, during starting one virtual machine csv volume get un accessible and all machine pertain to that csv get
    offline. subjected are the errors.
    Cluster Shared Volume 'Volume2' ('Volume2') is no longer accessible from this cluster node because of error '(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
    Cluster Shared Volume 'Volume2' ('Volume2') has entered a paused state because of '(c0000015)'. All I/O will temporarily be queued until a path to the volume is reestablished.
    after troubleshooting i found a patch for the related issue but its not working for window server 2012 R2,
    Windows8-RT-KB2838669-x64: its not running so kindly assist how to get this fix.
    Talha Faraz Malik

    Hi TFMalik,
    "To avoid CSV failovers, you may have to make additional changes to the computer after you install the hotfix. For example, you may be experiencing the issue described in the "Symptoms" section because of the lack of hardware support
    for Offloaded Data Transfer (ODX). This causes delays when the operating system queries for hardware support during I/O requests.
    In this situation, disable ODX by changing the FilterSupportedFeaturesMode value for the storage device that does not support ODX to
    1 "
    For details please refer to the link below :
    https://support.microsoft.com/kb/2813630?wa=wsignin1.0
    Best Regards
    Elton Ji
    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.

  • Failover cluster installation - BO server

    Hi,
    I have two BO servers and I have to configure them in failover mode.
    If the principal fail, the second one works.
    Does anyone try to do it before?
    Thanks,
    Julio

    Hi Durecu
    I will follow the steps mentioned but my question is about options to user with sapinst.exe?
    When should I have to usr SAPINST_USE_HOSTNAME?
    1. Central services instance for ABAP installation.
      Use the command line sapinst.exe SAPINST_USE_HOSTNAME=FRSERVERSAP
      Note - during the installation time all the cluster resource should be in Node 1
    During the time of Central service instance for ABAP & JAVA you have to use the Virtual hosts (that is on MSCS SAP Group DNS name, & Cluster disk before that you have to create in MSCS)
    Syntax " SAPINST.EXE SAPINST_USE_HOSTNAME=<*Virtual Host Name*> "
    2 First MSCS node installation => on Node I? Do I need to use SAPINST_USE_HOSTNAME=FRSERVERSAP ???
    Normal SAPINST.exe Without virtual name
    3 Database Instance Installation => Do I need to use SAPINST_USE_HOSTNAME? If yes, do I use FRSERVERSQL???
    Normal SAPINST.exe Without virtual name
    4 Additional or Second MSCS node installation => on Node II? with SAPINST_USE_HOSTNAME?
    Normal SAPINST.exe Without virtual name
    Regards
    Sriram

  • 2 Node Hyper-V failover cluster with sql server

    I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over. 
    The second will act as virtualized failover of the main node with failover instace to act as active to active approach. 
    I hope can someone give me an advice with my question. 

    I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over. 
    The second will act as virtualized failover of the main node with failover instace to act as active to active approach. 
    I hope can someone give me an advice with my question. 
    Sure you can do that. But it's a long story what's better SQL Server FCI or AlwaysOn. See:
    FCI Vs. AlwaysOn
    http://msdn.microsoft.com/en-us/library/ff929171.aspx
    (biggest issue with AlwaysOn - it does require Enterprise license so is COSTY)
    Good idea to ask here:
    SQL Server High Availability and Disaster Recovery
    http://social.technet.microsoft.com/Forums/sqlserver/en-us/home?forum=sqldisasterrecovery
    In any case you'll need either physical or virtual shared storage. For FCI to host everything and witness disk and for AlwaysOn just for witness (AlwaysOn does replication between DAS on it's own).
    Good luck :)
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • MSDTC set up in SQL Server 2008 failover cluster

    Hi Guys,
    I am in the process of setting up failover cluster using SQL Server 2008  (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
    be assigned from SAN or it should be local to the disk ,  Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
    With regards, Gopinath.

    Hi Gopinath,
    Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
    How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
    http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
    How to configure DTC for SQL Server in a Windows 2008 cluster
    http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL Server Failover Cluster Questions

    Dear All,
                I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
    1.  I am receiving MSDTC Warning.  I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not.  I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
    and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
    http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
    2.  During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME".  Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
    would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
    3.  During the instance creation, one needs to provide "SQL Server Network Name".  As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
    for all instances that I create or this is only required once in the cluster:
    4.  During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features.  As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
    it, so which features should be selected? so that there is less workload on the server.
    5.  All the instances use TempDB for databases that are present inside it.  What would be the best practice with respect to TempDB.  One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
    should be the ideal size of the TempDB LUN?
    6.  Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
    Thanks in advance. 

    Hello,
     1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
    refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
    Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
    2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
    Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
    You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
    3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
    4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
    in a failover cluster.
    5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
    6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
    http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • 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

  • SQL Server 2012 Failover Cluster Setup

    I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W.  AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
    2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
    Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
    Pranshul Gupta

    Yes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
    Software  and hardware requirments for sql 2012
    http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
    http://www.yourdba.com/?p=123
    http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
    Developer Edition..
    SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
    Clustering FAQ's
    http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
    SQL Server licensing :
    http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
    http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
    Overview  and support :
    http://msdn.microsoft.com/en-us/library/cc645993.aspx
    FCI Failover Cluster Instances (SQL Server)
    http://technet.microsoft.com/en-us/library/ms189134.aspx
    AlwaysOn Availability Groups (SQL Server) -- AG's
    http://technet.microsoft.com/en-us/library/hh510230.aspx
    Raju Rasagounder Sr MSSQL DBA

  • Hyper-V Failover Cluster - Inconsistent Network Availability

    We've got a Small cluster with, 7 hosts and a dozen or two VM's.  For some reason i'm getting inconsistent availability with the Cluster networks.  The host seem to function fine on there own but theres all types of issues using Migration which
    i'm assuming is because certain hosts think other hosts are unavailable. For Example:
    Cluster Network 1 - From Host 8
    Cluster Network 1 - From Host 10
    As far as I can tell all of the networks are UP. I can ping all hosts on all interfaces.  What criteria goes into determining host availability?

    Hi,
    Maybe you forgot to configure the Live migration Settings,
    In the Failover cluster manager->right click networks-> select the livemigration network.
    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.

  • SQL cluster name on a Windows Failover Cluster

    Hello,
    I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
    Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
    Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
    Thanks for your help,
    Luca

    It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
    SQL Server Network Name —
    Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
    https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
    This will be the name used to identify your cluster on the network. This is the name that will be available on the
    network for the clients to connect SQL instance.
    http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

Maybe you are looking for