Database Mirroring - Witness Server

Hi,
Can I have a setup where both the Primary and the Mirror servers are running on SQL Server 2008 and Witness is running on SQL Server 2005? Somehere, I read that the witness can be of any edition, however the version has to match with the Primary and the
Mirror setup.
Could someone please confirm?
Also, if SQL Server 2008 Standard Edition supports automatic failover on Database Mirroring?
Thanks,

In the Microsoft SQL 2014 docs I see: 
"We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported
only by SQL Server Standard edition and by SQL Server Enterprise edition.
Witnesses, in contrast, are also supported by SQL Server Workgroup and by SQL Server Express."
I figured I'd post this, since I ended up here looking for an answer to this question.  

Similar Messages

  • Witness Server Configuration

    Hi,
              We have configured SQL mirroring between our primary and DR servers. Now we wanted to configure witness server for this in order to enable automatic failover. Can anyone help me what needs to be done on witness server apart
    from base OS. do we need to install sql server on this? Please let me know?
    Regards,
    Varun

    Yes you need to install SQL instance, it can be express edition.
    Add or Replace a Database Mirroring Witness
    https://msdn.microsoft.com/en-IN/library/ms365603.aspx
    http://zarez.net/?p=1696
    Add Witness to Existing SQL Server Database Mirroring
    http://www.sqlservercentral.com/blogs/mssqlfun/2014/11/10/add-witness-to-existing-sql-server-database-mirroring/

  • Database MIRRORING in SharePoint 2010 - What to do in absence of Witness server

    Hi,
    Our environment is divided in 2 DC's, DC1 has our database cluster(2 nodes) and the DC2 has our mirroring server. 
    Now as part of DR test, DC1 will be shut down. So our Mirrored server in DC2 should cater all requests. To achieve this, I have set "Failover Server" for our content DBs, service application DBs from Central Admin > Manage Content DB/Service
    Application. I will set failover server for Config DB using Powershell.  However I DONOT have "witness server" in place.
    Now here are the things which I need help on:
    1. Once I set "Failover Server" for content DB in Central Admin, where can I see these changes? I mean where is that config file where this change is set?
    2. As we do not have a Witness Server, what all steps will be followed manually to achieve this failover? 

    You do not need to use a SQL Alias when implementing mirroring, or failing over to the mirror.
    You simply need to update each database's FailoverServer value, e.g.:
    $db = Get-SPDatabase | where {$_.Name -eq "SharePoint_Config"}
    $db.FailoverServer = "SQLMirroringPartner"$db.Update()
    All databases should have this parameter and can be handled in this way (some databases, such as Usage and Sync, aren't recommended to be mirrored as they hold transient information).
    To failover, you will manually initiate bringing the secondary online via SQL Server Management Studio.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Database mirroring with witness server and availability set

    Hi,
    I got two VMs Sql1 and Sql2 with mirroring between them, they are in the same availability to achieve 99.95% SLA.
    My mirroring config requires a witness server, while configuring a witness server you can specify only one server.
    From what I read online load balancing two witness servers and providing the load balancer ip as the witness server will not work.(is that right? or I can do that?)
    Anyway, how can i make sure the witness server(since it doesn't have a partner) has 99.95% SLA?
    Thank You!

    Thanks Manesh.
    Availability set ensures that not all the VMs in the Availability set will go down at the same time, and it's possible that only one VM in the Availability set will stay online.
    Therefore, if I will put the two partners and the witness in one Availability set there is the chance that both partners will be down at the same time.
    On the contrary, if the witness will be out of the Availability set, I can be sure that one partner will always be online.
    So including the witness server in the availability set will hurt the High Availability of the database.
    Always remember that only VMs that do the exact same job should be in the same Availability set.

  • How to get the SQL Primary and Mirrored Database Server Name from Witness Server

    Hello,
                    Can Someone help me with the way to get SQL Primary and Mirrored server name from Witness server?
    Any Powershell script/SQL Query..etc or share the alternative?
    Regards,
    Julie

    select principal_server_name,mirror_server_name,* from sys.database_mirroring_witnesses
    -Prashanth

  • Mirror and Witness Connection in a Disconnected state immediately after adding Witness Server to Mirror session.

    After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
    The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
    ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
    After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
    The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
    Any idea's why the state between Mirror and Witness Connection remains Disconnected?
    Thanks,

    I have the same problem.  All 3 servers are on a workgroup and I'm using certificates. All three servers are connected via  switch.  This is a test environment, with the principal server being a 64 bit OS with Windows Server 2003 R2 with SQL Server standard x64, the witness server is a Windows server 2003 SP2 x32 with SQL Server Express, and the mirror is Windows XP x32 with Sql Server Standard. Using hard coded static IP addresses (FQDN makes no difference, and they get resolved to IP addresses anyway!).  The mirror server log shows
    'The server instance Witness rejected configure request, read its error log file for more information
    but of course there are no errors logged on the witness server - not by SQL, nor in the event log.  When the witness is set on the princial server, the Database mirroring monitor shows almost immediately that the witness and prinicapl servers are connected, but it takes quite a few seconds before the witness/mirror state is shown as disconnected.  Until then the entry is blank.  The monitor also shows High Saftey with automatic failover, which isn;t true - since the mirror and witness are not connected, no failover occurs when the principal is taken offline.
    Since I'm running terminal services on the XP machine to interact with the witness and principal server, I find it hard to image that there are network issues. 
    If the witness can connect with the principal and the principal can conect with the mirror, under what circumstances will the witness NOT connect with the mirror?  When I check the witness server for entries in the database_mirroring_witness view the following is shown:
    RTJobs TCP://primary-sql:5022 TCP://192.168.100.14:5022 2 FULL 1 1 2263BD97-1004-4D73-9966-7AFB89E5626E A6EE18DF-19C4-48EC-8C06-77074EF5A275 0 1
    Interestingly the IP address of the prinical server is replaced by the Sql Server instance name (primary-sql) but this doesn't happen for the witness.  

  • Can we use SQL Server 2012 Web Edition as a witness server in mirroring?

    Hi All,
    Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
    Grateful to your time and support. Regards, Shiva

    Hi All,
    Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
    Grateful to your time and support. Regards, Shiva
    As Per BOL
    We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported only by SQL Server 2005 Standard and later versions and by SQL Server 2005 Enterprise Edition and later versions.
    Witnesses, in contrast, are also supported by SQL Server 2005 Workgroup and later versions and by SQL Server 2005 Express Edition and later versions. Except during an upgrade from an earlier version of SQL Server, the server instances in a
    mirroring session must all be running the same version of SQL Server. For example, a SQL Server 2005 witness is supported when you are upgrading from a SQL Server 2005 mirroring configuration but cannot be added to an existing or new SQL Server 2008 or later
    mirroring configuration.
    A witness can run on any reliable computer system that supports any of these editions of SQL Server. However, we recommend that every server instance that is used as a witness correspond to the minimum configuration that is required for the SQL Server Standard
    version that you are running. For more information about these requirements
    http://technet.microsoft.com/en-us/library/ms175191.aspx#SwHwRecommendations
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Database Mirroring and Replication in SQL Server 2008 R2

    I have configured the mirroring and replication between 4 servers (A,B,C,D).i.e, Mirroring between A to B and C to D, Replication between A and C. The configuration was a success and I am able test the replication(B to C) when I have failed over the mirroring
    dbs(A to B). The replication works fine after the mirroring fail over but I am not able to check its status in the Replication monitor. When I am having any insert in a table which is replicated in B, it is reflected back to C..it means the replication is
    working fine.
    Any thought on how I can view the status of replication from mirrored server. I tried adding the publisher in the monitor, but no luck. If I check the snapshot agent status, it says could not retrieve the info, same with the log reader agent status.
    Any suggestions on this please.
    Thanks, Siri

    For example in your case...
    Server A is principal and Server B is Mirror with either Manual or Automatic Failover.
    Server A is replicated to Server B ( publisher & B is subscriber )
    In Server A Database named Test_Mirror_Replication is configured for both mirroring and Replication.
    Now you have failed over your Database 'Test_Mirror_Replication' from Server A to Server B.
    After the Failover Server A will act as Mirror for DB 'Test_Mirror_Replication' & Server B will act as Principal for DB 'Test_Mirror_Replication'
    Hope my understanding is correct ?
    If yes then have you tried monitoring the replication after registering in other instance with current principal database sql instance name ? I mean current Publisher database name sql instance ? not your old sql instance name which was before the mirroring
    role change or failover...
    Hope you are trying with mirror database server name ?
    Raju Rasagounder MSSQL DBA

  • Alert: SQL Server Service Broker or Database Mirroring Transport stopped

    Hi Team,
    I got this error message even no one DB configured as mirroring ???
    Alert: SQL Server Service Broker or Database Mirroring Transport stopped Priority: 0 Severity: 2 Resolution state: New
    Alert description: The Database Mirroring protocol transport has stopped listening for connections.

    Can you check the rule. By default the configurations are disabled state that is the reason you are getting the alert.
    If it's not configured properly then you might need to override it
    --Prashanth

  • SQL Mirroring Requirement (Witness server) in LYNC 2013

    Hi Everyone,
    We are designing a Highly Available solution of for LYNC 2013 and planning to add a witness server to the backed SQL server.
    Following are my Queries.
    1)For the witness server should the SQL server be dedicated to the LYNC infrastructure or it can be used to host other databases.
    2)I am assuming the Witness Database should be in the same Domain?
    3)What is the version of the SQL server that is supported as the Witness server, can this be the Free SQL express edition ?
    Waiting for some replies :-)

    1)For the witness server should the SQL server be dedicated to the LYNC infrastructure or it can be used
    to host other databases.
    It Can be used to host other database
    2)I am assuming the Witness Database should be in the same Domain?
    Yes 
    3)What is the version of the SQL server that is supported as the Witness server, can this be the Free SQL
    express edition ?
    http://technet.microsoft.com/en-us/library/gg398990.aspx
    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" Regards Edwin Anthony Joseph

  • SQL Server 2005: Monitoring Database Mirroring

    Hi All,
    I use SQL Server 2005 with mirror enable.
    Are there anyway to check/monitor/verify whether all data at principal are transit to mirror serer ?
    Regards,
    Pitou

    What is operation mode of the mirroring configuration?
    http://technet.microsoft.com/en-us/library/cc917680.aspx#XSLTsection126121120120
    /*If transaction safety (or just 'safety') is set to FULL, the principal and mirror servers operate in a synchronous transfer mode. As
    the principal server hardens its principal database log records to disk, it also sends them to the mirror. The principal then waits for a response from the mirror server. The mirror responds when it has hardened those same log records to the mirror's log disk.
    When safety is set OFF, the principal does not wait for acknowledgment from the mirror, and so the principal and mirror may not be fully synchronized (that is, the mirror may not quite keep up with the principal).*/
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Migrate Mirror Database to New Server

    Hi,
    I need to migrate my SQL server Mirror Database to
    a new server. my current setup is as below
    1. server A principal (192.168.1.100)
    2. server B Mirror     (192.168.1.200)
    now i have a new server (Server C) to replace server B as below
    1. server A principal (192.168.1.100)
    2. server C Mirror     (192.168.1.300)
    my question is how to migrate mirror db to new server without any affect or downtime on principal server, please share idea/experience for above.
    note: SQL SERVER 2008R2 EE(64BIT), Win2008R2 EE 64bit.
    Regard
    Faisal Wahid

    Thanks for your quick response.
    Is it possible something like in oracle (pardon as i am oracle DBA not sql server guy), 
    (Oracle Steps to migrate standby(mirror) db to new server)
    1. Pause replication on primary(principal) 
    2. Move standby(mirror) database files to new server(using copy/rman/etc).
    3. Update connection information (TNS in oracle) on primary(principal) to point new server.
    4. Start replication on primary(principal).
    the above steps will simply migrate the standby(mirror) database to new server,
    can we do something like above in sql server?

  • Error in Starting Database Mirroring

    Hai Everyone.. I have an issue in mirroring which i described below.
    I am getting the above error when i click on "start mirroring" button. I turned off firewall in my antivirus. 
    And i also executed the below script in both my principal and mirror server. Because i created both the instances in my system only. And i am accessing those instances with windows authentication.
    Go
    GRANT CONNECT ON ENDPOINT:: EMP1_MIRRORING TO [DEVLAP5170\login];
    Go 
    -- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.

    Hi,
    How’s everything going?
    Also, see prerequisites for database mirroring:
    For a mirroring session to be established, the partners and the witness, if any, must be running on the same version of SQL Server.
    The two partners, that is the principal server and mirror server, must be running the same edition of SQL Server. The witness, if any, can run on any edition of SQL Server that supports database mirroring.
    The database must use the full recovery model.
    Verify that the mirror server has sufficient disk space for the mirror database.
    When you are creating the mirror database on the mirror server, make sure that you restore the backup of the principal database specifying the same database name WITH NORECOVERY. Also, all log backups that were created after
    that backup was taken must also be applied, again WITH NORECOVERY.
    Helpful link:
    Prerequisites, Restrictions, and Recommendations for Database Mirroring
    http://msdn.microsoft.com/en-us/library/ms366349.aspx
    Thanks.
    Tracy Cai
    TechNet Community Support

  • 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

  • Database Mirroring

    If database in suspect mode what is going to be happen in mirroring? will it failover?

    Yes I would say yes because suspect mode mostly likely occurs due to Hardware failure,
    improper shutdown of the database server,
    corruption of the database files, and of course unavailable database files and so on...
    And as we all know in mirroring
    unplanned downtime can be caused by hardware failures such as storage failure, by power outages, by human error, or by natural disasters, all of which can cause the production server as suspect mode or data center to be unavailable.
    However if we talkling about Suspect_pages The principal recognizes a page read error, marks the page with an 829 error (restore pending), inserts a row into the suspect_pages
    table in MSDB with the error status, and requests the page from the mirror. If the mirror is victorious in reading the page, it returns the page to the principal who applies it. After the page is repaired, the principal marks the page as restored — that is,
    event_type =
    5 in the suspect_pages table. Then any deferred transactions are resolved.
    You can use this code SELECT
    * FROM
    sys.dm_db_mirroring_auto_page_repair
    catalog view to  displays corrupted pages in the data mirroring environment.
    If the mirror fails, then the principal continues functioning, so the database continues to be available to the clients. The mirroring state is DISCONNECTED, and the principal
    is running exposed in this case. You can use the sys.database_mirroring
    catalog view to see the mirroring state on the principal server. Make sure you have plenty of disk space for the transaction log to grow on the principal and be sure to bring the mirror server online before you run out of disk space and your other option
    will be using this code to break the database mirroring session ALTER DATABASE
    <database_name> SET PARTNER OFF if you have to.
    If the
    witness is lost, the database mirroring session will continue functioning
    without interruption, and the database will be available. 
    However If the
    principal server is lost, the failover scenario
    depends on the transaction safety (FULL or OFF) and whether a witness is present. if we talk about
    FULL with a witness If Server A fails, then Server B will be the Principal but witness down Server B will not be able to Serve. so if we talk about
    without a witness if the Principal fails the database is not accessible to client unless you don't have to go several
    steps to make it available. Finally we talk about Principal with OFF (no witness) if the
    principal is lost the database will be unavailable and then your option is to FORCE FAILOVER 
    I hope this will help and give you idea to make more research about it and overcome your problem. Good Luck

Maybe you are looking for