Hi Everyone,
I am doing some test for database mirroring. I come with come with these two scenarios i unable to test out.
1) The principal database server disks full. In these case is the database mirroring failover will happen?
2) The principal database server and mirror database server disk full. In these case what will happen to database mirroring?
Hello All,
My production SQL DB is on 2008 Enterprise x64 bit I have to build a DB mirror for my production server in other server. Can I know the target system requirement do I need to install the SQL in the target system? is my target system also have the same configuration like OS and H/W? pre-requisites? step by step method for doing DB mirroring?
Yuvi
Here is my scenario. I have 2 database servers, P and M, to serve our production website. P = Principal; M = Mirror.
After some time my Principal crashes. No problem, I've got M, it's been synchronizing, and it has all latest data. So I repoint my production web server to hit the Mirror. Still, all is good.
Now comes the part where I'm fuzzy, and I need to know if my understanding is correct...
The Principal comes back online, but my website is still pointing at the Mirror. I want to repoint the site back to Principal. But P now has old data. Maybe it's been down 3 days and M has 100,000 new records that don't exist in P. When P came back online, did transaction logs begin shipping from M to P to get P back in sync? Would it do that if a Witness were in place? How does P get caught up with all latest data? Do I have to do a full backup and restore from M to P? Is there a way this can be set up to just gracefully (or even easy manual) get P updated and synced? Can the Principal/Mirror roles be easily swapped between the 2 servers? Does that happen automatically with a Witness in place?
Thanks in advance for any help.
Hi All,
We have a strange requirement from one of our client. Exactly saying before configure mirroring as a high availability he wants to know what would be the possible failures can occur in mirroring and how to resolve them. I believe it is hard to have a reported document of it but I'm really grateful if you can share your personal experiences to help me out on this.
To achieve this I need simple scenarios or issue and steps to resolve it. Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----
Hello,
I have a strange problem with the mirror instance of one of our databases,
The mirroring seems to be working, however every 20 seconds or so the error
1438 Severity 16 State 1
The server instance Partner rejected configure request; read its error log file for more information. The reason 1460, and state 1, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry.
is logged in the SQL server log on the mirror instance
The strange thing is that the mirroring seems to be working, while in all cases that i can find on this error this occured during configuration. and the mirroring fails
There is no coresponding error logged in the SQL server log on the principal
Accordig a query on master.sys.database_mirroring on both the mirror and the principal the status of the mirror set is synchronised. There are 88 other databases mirrored the same way between the same instances, without problems. I related the problem to a
specific database, when i stop or pause the mirroring for this specific datbase the errors stop being logged I already removed the mirror database and recreated the mirror config for the database from scratch, but the errors just returned as soon the
mirroring for the database was active again. It looks like there is no problem with the endpoints or the security configuration. (I already tried restarting the endpoints)
Configuration:
Both SQL Server 2008R2 enterprise instances are build 10.50.2811, running on two node Windows 2008 R2 SP1 failover Clusters
Mirroring Configuration is Async (Safety off) between Principal en Secondary, There is no Witness instance (we use mirroring to sync the databases between datacenters for disaster recovery and have no need for automatic failover), I even checked that there
was no witness instance configured by mistake.
Rob Hagman.
Hi,
I am currently setting up an SQL Server Mirror with only two Servers running SQL Server 2008 R2 Standard edition
My setup is using only a Principal and a Mirror with no Witness.
Port being used is 5022 on both servers. I am able to telnet the servers both ways
Only thing I noticed is that the endpoint name is different on each server.
I am able to complete the configuration using the wizard without any issue.
I however when starting the Mirror, I get the attached error message
Thanks
Hi,
As I am going to configure Database Mirroring in sql server 2008 R2. It is giving error 1418.
The server network address "TCP://xyzserver.domain.con:5022" can not reached or does not exist. Check network address name and that the ports for the local and remote endpoints sre operational.(Microsoft SQL Server, Error: 1418)
I have tried the below steps:
1. ALTER ENDPOINT Mirroring FOR DATA_MIRRORING (ROLE = PARTNER, ENCRYPTION = SUPPORTED)
2. ALTER DATABASE PROD_DB SET PARTNER = 'TCP://xyzserver.domain.Com:5022'
3. DROP ENDPOINT Mirroring
SELECT *
FROM sys.endpoints
4. CREATE ENDPOINT Mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 60801 )
FOR DATABASE_MIRRORING (
AUTHENTICATION = WINDOWS KERBEROS,
ENCRYPTION = SUPPORTED,
ROLE=ALL);
SELECT state ,state_desc FROM sys.database_mirroring_endpoints
3. GRANT CONNECT ON ENDPOINT::Mirroring TO ALL
4. GRANT CONNECT ON ENDPOINT::Mirroring TO SA
WITH GRANT OPTION;
GO
I have tried all above the steps. But still I can not resolve the issue.
Can anyboby help me?
Sachin Jain
Hi Everybody,
We use the database mirroring a lot in our product solutions and we have recently experienced a strange behaviour in our failover tests with SQL2008R2.
We have 2 servers running Windows 2008 R2 standard and SQL 2008 R2 standard SP2. (let's call them DB1 and DB2)
We also have a Witness workstation running SQL 2008 Express on a Windows 7
A database from DB1 is mirrored to DB2 in "safety full" mode, with witness. At this stage, the database is principal on DB1 and mirror on DB2
To test the automatic failover, we first restart the DB1 server which has the database in principal mode
After a few seconds, the database on DB2 becomes principal, which is normal , that's exactly what we want.
After a few minutes, DB1 comes back online and its database takes the mirror role (still OK). At this stage then, the database is principal on DB2 and mirror on DB1
when the monitoring application shows that the mirror is synchronized and that both servers are connected to the witness, we restart DB2 to trigger an automatic failover to DB1.
What we see is that DB1 never takes the principal role and the database stays in mirror.
In the DB1 Errorlog, I only see these 2 lines when DB2 disappears, no other message related to the mirroring session.
2014-01-22 08:57:26.91 spid43s Starting up database 'Test123'.
2014-01-22 08:57:26.95 spid43s Bypassing recovery for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
When DB2 comes back online, the database on DB2 keeps its principal status and the database on DB1 stays mirror.
And what is really really strange is that, if I restart DB2 once again, directly after that, DB1 failover normally and the database on DB1 takes the principal role after a few seconds. without any configuration changes between the 2 restarts.
DB1 errorlog shows then :
2014-01-22 09:00:37.53 spid29s Error: 1474, Severity: 16, State: 1.So, if I summarize,
- a first failover from DB1 to DB2 always work
- then, a restart of DB2 never failover to DB1
- a second restart of DB2 always failover to DB1
This is pretty much systematic on one our server couple.
Any explanation for this or any idea where I can search to find the reason of this strange behavior ?
Thanks a lot for your help
Seb
Setup is two 2008 R2 Standard servers with a mirrored database. All works fine without a witness - I can perform a manual failover and my test app works off the failover database. Trying to add 2008 R2 Express as a witness to enable automatic failover, and getting error along the lines of:
The ALTER DATABASE command could not be sent to the remote server instance TCP://%witnesserver.fqdn.com:5022. Error 1456
Found a fairly recent fix for SQL 2008 (r1) for this, but not for R2. Is this still a known problem in R2 or am I missing something crucial?
All the servers use the same service account for all services (it's proof of concept, not production).
Thanks in advance,
Neil
Hi All,
We install the mirroring. After one month log file is full in mirror.
So on that time what will do?
Please suggested to me.
Thanks in advance:)))
hello everyone,
i have a SQL cluster of 4 Nodes for our ms dynamics ax and everything was working fine.
suddenly we had a failure in our main Data Center so we have decided to create a live DR of our cluster to a new Data Center.
i have been looking here and there and found something that said i have to create a mirror to my SQL to the new site.
is it possible to create this mirror or live backup to a new single SQL server 2008 r2 or it should be same cluster as our 4 node cluster and how to do that
thanks
regards
hello sir,
my self chandrika..
If mirroring got failed. How do i know, and what alerts will get ? will please clarify my doubt.
Im wanting to build a staging server for the ETL work to be carried out on my databases before extracting into my Datawarehouse.
Whats the best way to get a nightly copy my source database onto my staging server.
I don't need everything in the source databases, a lot of the tables are redundant so I would like the option of only pulling across the tables I need.
Mirroring looks like I need to mirror the full database, replication seems a bit of a sledge hammer for what I need, and ETL process has a bit of work but this may be the best.
I may be wrong on these any you guys recommend whats the best tool.
Thanks
Hi Guys ,
I am trying to set up Mirroring on my local machine to test SQL2008R2. And when Ever I am trying to start getting this error..
IS anyone has idea?
On Mirror Server Error log has this details
: Database Mirroring login attempt by user.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITY\NETWORK SERVICE' does not have CONNECT permission on the endpoint. State 84.'.
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah