SQL mirroring or SQL mirroring?

Hi,
Lync Topology builder is able to build the SQL mirroring between the hosts. But what about if SQL team like to avoid that to use that? I mean is there big differences if the mirroring is built by topology team, or by SQL own tools?
And how is the supporting?
Technet says about
mirroring "You use Topology Builder to deploy SQL mirroring
". But it does not clarify if there are any differences if the mirroring is built by built in tools of SQL.
Petri

you still can build the Mirror using SQL Management Studio. as long as you have configured all Lync server host names in SQL Security with correct permission,
Lync should be able to manage the mirror. I had to do this on one of the sites and it's functioning without any issues.
When you say, Lync should be able to manage the mirroring, what do you exactly mean by that? How much Lync actually care about the mirroring? Especially in case when witness is not deployed.
Also if there is a fail over on the SQL site which is initialized by the SQL itself (e.g. SQL team member does the fail over). How much that affect for the Lync?
Petri

Similar Messages

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

Error while setting up db mirroring in sql server 2012

Hi Team,
I am trying to setup DB Mirroring in our setup and Need your help here!
I've 3 servers (2 (Principal and witness) of them are in one machine and 1 (Mirror) is in other machine) setup ... Firewalls are turned off on all 3 of them.... I want to set them up as Principle, mirror and witness respectively.... Before configuring the mirroring,
I backed up the database on Principal and restored it on Mirror database (Restore With No Recovery) . I did it first for the DB backup file and then the transaction log file.......
Now, when I configure mirroring on my my principle server and after choosing my respective serves are principle, mirror and witness.When I am trying to start mirroring I am receiving the below error,
TITLE: Database Properties
An error occurred while starting mirroring.
ADDITIONAL INFORMATION:
Alter failed for Database 'COSBCS_TEST_4GL'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.2100.60+((SQL11_RTM).120210-1846+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The server network address "TCP://ADMIN036.cos2000.cos.net.au:5023" cannot be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=1418&LinkId=20476
BUTTONS:
OK
Can you let me know how to fix this error?
Thanks,
Sarvan.N

http://blog.sqlauthority.com/2010/01/11/the-server-network-address-tcpsqlserver5023-can-not-be-reached-or-does-not-exist-check-the-network-address-name-and-that-the-ports-for-the-local-and-remote-endpoints-are-operational-microso/
Best Regards,Uri Dimant SQL Server MVP,http://sqlblog.com/blogs/uri_dimant/
Blog : MS SQL Development and Optimization
Blog : Large
scale of database and cleansing

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

How to resolve Error: 1418 in sql server while mirroring

Hi Support,
I am trying to mirroring a database in sql server. I created a database and took a backup of it and restored on the another instance(i am using same server but with different instances). But after doing all operations and click on start mirroring, then it
showing following error.
The server network address "TCP://indserver.xxxx.local:5022" can not be
reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)
I followed mirroring steps in this "http://www.codeproject.com/Articles/31325/Step-by-Step-SQL-Mirroring-the-ASPState-Database" Here it says, create an user on both principal and mirror server with the same credentials in STEP 3.So please provide
me solution for above error.

Hi Pankaj Sharma,
According to your error message, we need to verify if you backup your database with full recovery model and restore this database to a mirror instance with NORECOVERY option. You need also verify all instances can access every other partner and make sure
endpoints are running properly, you have granted the SQL Service Account CONNECT permission to the listener on the other machine.
If after trying this you are still getting a 1418 error, here's a blog post with a couple of other things to check for:
http://blogs.msdn.com/grahamk/archive/2008/12/08/database-mirroring-error-1418-troubleshooter.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

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 Conectivity error (1418) on SQL Mirroring in SQL Server_2014 Enterprises

I perform this subjected task/activity in DOMAIN environment with Multiple VPN.
No matter what I try, I constantly run into a 1418 error, I've check all my tcp/ip configs both in sql,
and the server 2012 os, on both vms/physical machine.  I’ve
enabled tcp/ip filtering and allowed all connections, rulessets in firewall, I’ve used telnet to connect up.  Nothing
seems to work.  Each
server can ping the other, they can telnet into 5022, & 5023 as well. I don’t know where to proceed from here.  Is
there some config somewhere or issues with vms that I am not seeing?  All
the machines in the mirroring array are server 2012 with same SQL 2014 Ent edition. Now please guide as what can we do to go at next Step....!
Regards,
Zeeshan

Hi Zeeshan,
Please check the following, have you checked the error log? Share the error screenshot here in order to verify the issue.
Make sure that the mirror database is ready for mirroring.
Make sure that the name and port of the mirror server instance are correct.
Make sure that the destination mirror server instance is not behind a firewall.
Make sure that the principal server instance is not behind a firewall.
Verify that the endpoints are started on the partners by using the state or state_desc column the of the sys.database_mirroring_endpoints catalog view. If either endpoint is not
started, execute an ALTER ENDPOINT statement to start it.
Make sure that the principal server instance is listening on the port assigned to its database mirroring endpoint and that and the mirror server instance is listening on its port. For more information, see "Verifying Port Availability," later in this
topic. If a partner is not listening on its assigned port, modify the database mirroring endpoint to listen on a different port.

Using WMI alert for mirroring in Sql server 2012

We are using mirroring in Sql Server 2012 and we are using WMI alerts for some of events such as Connection lost,Manual failover,...
In alert definition we have set the followings:
Type: WMI event alert
NameSpace:
\\.\root\Microsoft\SqlServer\ServerEvents\MSSQLSERVER
Query: select * from DATABASE_MIRRORING_STATE_CHANGE where State = 6
The alert is bing triggered correctly,but on email description instead of having meaningful explaination like 'Connection lost',We have the same query:
Query: select * from DATABASE_MIRRORING_STATE_CHANGE where State = 6
We have used the same implementation in our Sql Server 2008 servers and it is working fine.This mashine (Sql Server 2012) is a new mashine.
I would appreciate if someone help me on this.AlsoI checked and 'Include body of e-mail in notification message' was already set.
Thanks
Aspet
A.G

Are you looking for alerting related to mirroring like below ?
http://www.mssqltips.com/sqlservertip/1859/monitoring-sql-server-database-mirroring-with-email-alerts/
http://technet.microsoft.com/en-us/library/cc966392.aspx
Raju Rasagounder Sr MSSQL DBA

How to configure current SQL high availability cluster using mirroring with dedicated replication NICS?

We have a current HA cluster at center1 which is mirrored to another HA cluster in center2. We have several instances already installed and working which are using one NIC for data and replication. We want to prevent mirror failovers by
configuring a NIC on a replication network which has no DNS server. What are the steps to configure the current SQL instances to use this dedicated NIC for mirror replication?

Hi dskim111,
You can refer the following step by step article to create the dedicated mirroring NIC,
Step by Step Guide to Setup a Dedicated SQL Database Mirroring(DBM on dedicated Nic card)
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/step-by-step-guide-to-setup-a-dedicated-sql-database-mirroring-dbm-on-dedicated-nic-card.aspx?Redirected=true
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.

SQL 2005 mirroring : Abrupt Automatic failover

hi All,
We have a SQL 2005 SP4 mirroring setup of 15 DBs with Principal(P), Mirror(M) & Witness (W).
We have now seen abrupt DB failovers for some of the databases (yest it was 4 out of 15) from P to M.
Errors were seen on Witness server as follows for all Dbs that failed over:
Date 07/01/2015 11:07:48 PM
Log SQL Server (Current - 08/01/2015 12:00:00 AM)
Source spid19s
Message
The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response. Check the service and network connections.
Actions taken:
1. Network and Firewall team reverted that no error detected and no network traffic between the witness server and db server during the db auto failover period.
2. On the system side, we have verified that no hardware error found on either VM or SAN storage, and no Symantec SQL backup jobs running nor anti virus scanning during the db auto failover period too.
3. We did see some high amount of IO activity on P server around failover time. Some IO errors similar to below were seen, however point to note is these errors were not only for the DBs that failed over, but for others including TEMPDB:
Date 07/01/2015 11:07:38 PM
Log SQL Server (Current - 08/01/2015 4:06:00 AM)
Source spid2s
Message
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [R:\SQLDATA\MSSQL.1\MSSQL\Data\<DBName>.mdf] in database [DBName] (5). The OS file handle is 0x000000000000095C. The offset of the
latest long I/O is: 0x0000054ff22000
Questions:
1. I assumed that the Witness keeps polling P & M on DB mirroring endpoints (in our case 5022) to check that the DBs are online, but Network team says there is no activity on that port, is my understanding correct?
2. Is there any other reason for DB failover ?
Link referred:
http://dba.stackexchange.com/questions/22402/what-can-cause-a-mirroring-session-to-timeout-then-failover-sql-server-2005
http://msdn.microsoft.com/en-us/library/ms179344(v=sql.90).aspx
Any help is highly appreciated!!!
Regards,
Mandar

This is common with Mirroring server it is not as resilient to changes as log shipping. Are you aware about
below fact although not directly related to your question
If you plan to use high-safety mode with automatic failover, the normal load on each failover partner should be less than 50 percent of the CPU. If your work load overloads the CPU, a failover partner might be unable to ping the other server instances in
the mirroring session. This causes a unnecessary failover. If you cannot keep the CPU usage under 50 percent, we recommend that you use either high-safety mode without automatic failover or high-performance mode.
Now to your problem
The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response. Check the service and network connections.
I would say there was network dip for more than 10 seconds and since default failover time is 10 seconds and for few databases witness thought principal cannot be reached it initiated failover.
Network team is incorrect to say there was no dip (its common with NOC team not to take responsibility)
This Support Article is worth reading specially the network part
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL 2005 mirroring - time taken to fail over?

I'm looking for an easy way to 'measure' the amount of time it takes our principal Database Server to fail over to our mirror Server in which all regular service will be resumed.
Any help would be hugely appreciated
Thanks guys
ras

http://technet.microsoft.com/en-us/library/ms187465.aspx
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

SP 2013 - Database Recovery Mode When Using SQL Server Mirroring

Hello Community,
Our DBA is configuring a High Availability Architecture for our SharePoint 2013 Farm. Essentially he is using SQL Server Database mirroring with a clustered automatic failover using a witness server. He has informed me that mirroring requires
that the databases are set to Full Recovery Mode, but that several of the databases are set to Simple Recovery Mode, the databases are the following:
SearchService_DB
SearchService_DB_CrawlStore
SearchService_DB_AnalyticsReportingStore
SearchService_DB_LinksStore
WSS_UsageApplication
User_Profile_DB
User_Sync_DB
User_Social_DB
However, when I checked the following article -
http://technet.microsoft.com/en-us/library/cc678868.aspx - I see that Simple Recovery Mode is the default configuration for these databases. So, finally, here is my question - will it be detrimental to these databases to set them to the Full Recovery
Mode?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

This really depends on your recovery objectives. The main reason for taking log backups, aside from truncating the log, is to be able to recover to a specific point-in-time. This is very helpful in mission-critical, highly transactional systems. I have not
seen a SharePoint environment require a point-in-time restore of the content or application service database. So for this case, you can overwrite the LDF bakups. Just make sure that you can recover your databases appropriately and meet your recovery objectives
on the farm level.
As far as the log file growth is concerned, you are correct. If you cap the size of your LDF file to let's say 10 GB, regular log backups will truncate the log, thereby, having space for additional transaction log records. The only risk here is when your
log backups are not frequent enough that the LDF file fills up before the next log backup runs to truncate the log. You run the risk of your database behaving as read-only and that will affect the site collections/applications using those databases
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 failover cluster\mirroring VS AlwaysOn for VDI?

Hi, we have to build high availability SQL 2012 cluster for VDI and we have two options. One option is to build a server cluster with combination of failover and mirroring and other option is to build failover cluster with AlwaysOn.
We are not sure which option to chose. We have contacted Microsoft support to provide us some documents and instructions for failover\mirroring combination but they have send us instructions for AlwaysOn option.
What would be best way to build high availability cluster for VDI? Also, since first option is very complicated, we would appreciated if someone could provide us with some documentation for it (how to build it, what to look out for, etc.) because that is the probably the option we are going to use.
Thank you in advance.
This topic first appeared in the Spiceworks Community

I was recently quoted in eCampus News regarding the recent cyber attack against Penn State, which triggered a number of conversations with CISO’s at various academic institutions. One of these conversations was with Helen Patton, theChief Information Security Officer for Ohio State University. I had a very interesting dialogue with her via email, and asked […]…Read MoreThe post In the Trenches: Helen Patton, Ohio State University CISO appeared first on The State of Security.
Read More

Failover SharePoint SQL Mirror steps?

Hi
I have a stretched SharePoint 2010 farm across 2 DCs. We have a SQL server in each site (2008 R2) using asynchronous mirroring. We use Power Pivot service application - its DB is also mirrored. I set the failover server/database location
using PowerShell for all SP DBs.
We attempted a mirror failover last week using the following process:
1. Activated the mirrored DBs
2. Updated Power Pivot service application to point to the new failover server/db
Afterwards all SP services seemed ok - apart from Power Pivot. We got an error about "unable to refresh data". The reports would load but we could refresh data within those reports.
I just want to ask are we following the correct procedure in failing over?

Hi,
According to your description, my understanding is that the PowerPivot reports could not refresh data after changing the databases.
I recommend to make sure that the following services are running:
Excel Calculation Service; Secure Store Service;
Claims to Windows Token Service; PowerPivot Service.
And check the service account’s permission on the new database.
Please also try to point the PowerPivot service application to the former database to see if the issue still occurs.
Could you please provide more detailed error message in the ULS log?
Thanks,
Victoria
Forum Support
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]
Victoria Xia
TechNet Community Support

Monitor SQL Database mirroring using powershell script

I am trying use the below powershell script to monitor SQL Database mirroring. The motive here is to determine if there are databases which are in "Disconnected" or "Suspended" mode.
I am running the script on the Principal Server:
$returnStateOK = 0
$returnStateWarning = 1
$returnStateCritical = 2
$returnStateUnknown = 3
$NagiosStatus = ""
# Load SMO extension
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null;
# Servers to check
$sqlservers = @("$env:computername");
foreach($server in $sqlservers)
$srv = New-Object "Microsoft.SqlServer.Management.Smo.Server" $server;
# Get mirrored databases
$databases = $srv.Databases | Where-Object {$_.IsMirroringEnabled -eq $true -and $_.MirroringStatus -eq "Suspended" -or $_.MirroringStatus -eq "Synchronizing" -or $_.MirroringStatus -eq "Disconnected"
-or $_.MirroringStatus -eq "None" -and $_.Name -ne "Master" -and $_.Name -ne "model" -and $_.Name -ne "msdb" -and $_.Name -ne "tempdb"};
if ($databases -ne $null)
$databases | Select-Object -Property Name, MirroringStatus | Format-Table -AutoSize;
exit $returnStateCritical
} Else {
Write-Host "All Databaes are Mirrored"
exit $returnStateOK
I have Suspended few databases for testing purpose but when I run the above script the output says "All Databaes are Mirrored"
If I make changes to $database and use it below i.e. I am changing the AND operator to OR after "$_.IsMirroringEnabled -eq $true"
$databases = $srv.Databases | Where-Object {$_.IsMirroringEnabled -eq $true -or $_.MirroringStatus -eq "Suspended" -or $_.MirroringStatus -eq "Synchronizing" -or $_.MirroringStatus
-eq "Disconnected" -or $_.MirroringStatus -eq "None" -and $_.Name -ne "Master" -and $_.Name -ne "model" -and $_.Name -ne "msdb" -and $_.Name -ne "tempdb"};
I get the below output:
Name
MirroringStatus
DB1
Synchronized
DB2
Synchronized
DB3 Synchronized
DB4
Suspended
DB5 Suspended
DB6
Suspended
DB7
Synchronized
DB8
Synchronized
I only want the databases which are Suspended or Disconnected to be listed.

I only want the databases which are Suspended or Disconnected to be listed.
Hi raul-133,
Based on your description, to list the databases which are Suspended or Disconnected ,I recommend you execute the following Transact-SQL statements in SQL Server firstly. If you can get the expected results from this query, then use the SQL Server query
in powershell script. For more details, please review this similar blog:
Monitor database mirroring.
Use master
go
select d.name, m.mirroring_state_desc
from sys.database_mirroring m,
sys.databases d
where m.database_id = d.database_id and (m.mirroring_state in (0,1))
For more details about mirroring state, you can review this article:
sys.database_mirroring (Transact-SQL).
Thanks,
Lydia Zhang

Project Server 2010 failover environment with Database SQL Mirroring

Hello,
We have prod and failover environment. Failover environment created by using farm backup and restore of prod.
my question is : Can we do SQL Mirroring (from prod to failover) of 5 databases (4 PS databases and content db) to keep both the environment in sync. Will this process work in the case of Project
Server 2010. i am in doubt due to timestamp and GUID in config DB.
Also will this process is supportable.
Any help much appreciated.
Thanks

Hello MOhit2020,
I haven't done this type of failover, but I think you would need to setup all your SharePoint and project databases to use a SQL Alias to point to your production databases. When and if your production databases failed, you would update
your SQL Alias to point to the mirror location.
The other nice feature about having SQL Alias setup in SharePoint, is that in the future, if you switch to another SQL Server, the SQL alias makes it easier to handle.
Cheers!
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

SQL mirroring or SQL mirroring?

Similar Messages

Maybe you are looking for