July 15, 2009 at 2:22 am
Hello everybody,
I am trying to setup database mirroring.Mirroring started and manual failover is possible.but when i shutdown the principal server ,mirror server is not changing to principal.
error log in principal site
Database mirroring is active with database 'Target' as the principal copy. This is an informational message only. No user action is required.
error log in mirror site
Log was restored. Database: target, creation date(time): 2009/06/25(08:52:45), first LSN: 11339:1419:1, last LSN: 11339:1479:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\BOND1\tlog1.trn'}). This is an informational message. No user action is required.
2009-07-15 09:27:45.95 spid22s Database mirroring is active with database 'target' as the mirror copy. This is an informational message only. No user action is required.
2009-07-15 09:28:11.45 spid20s Error: 1474, Severity: 16, State: 1.
2009-07-15 09:28:11.45 spid20s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://saismssqlsvr.sais.bw:5023'.
2009-07-15 09:28:11.53 spid22s Database mirroring is inactive for database 'target'. This is an informational message only. No user action is required.
2009-07-15 09:28:11.53 spid20s Error: 1474, Severity: 16, State: 1.
2009-07-15 09:28:11.53 spid20s Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://saismssqlsvr.sais.bw:5023'.
2009-07-15 09:28:53.60 spid22s Database mirroring is active with database 'target' as the mirror copy. This is an informational message only. No user action is required.
2009-07-15 09:39:07.00 spid20s Error: 1474, Severity: 16, State: 1.
2009-07-15 09:39:07.00 spid20s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://saismssqlsvr.sais.bw:5023'.
2009-07-15 09:39:07.09 spid22s Database mirroring is inactive for database 'target'. This is an informational message only. No user action is required.
2009-07-15 09:39:07.09 spid20s Error: 1474, Severity: 16, State: 1.
2009-07-15 09:39:07.09 spid20s Database mirroring connection error 4 'An error occurred while receiving data: '10053(An established connection was aborted by the software in your host machine.)'.' for 'TCP://saismssqlsvr.sais.bw:5023'.
2009-07-15 09:50:33.23 spid22s Database mirroring is active with database 'target' as the mirror copy. This is an informational message only. No user action is required.
I am using domain administrator account to log in to the sql servers.
Please help
Thank You,
Susan
July 15, 2009 at 2:33 am
susan.susan28 (7/15/2009)
I am trying to setup database mirroring.Mirroring started and manual failover is possible.but when i shutdown the principal server ,mirror server is not changing to principal.
Which mode do you have the mirroring set up with? Synchronous or asynchronous? Is there a witness server?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 15, 2009 at 2:40 am
I want to set up mirroring in synchronous mode.There is not witness.I am using sql server 2005 standard edition sp2
Thank You
Susan
July 15, 2009 at 2:58 am
You cannot do auto-failover without a witness server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 15, 2009 at 3:12 am
Ok.Can you please guide to setup a asynchronous type mirroring because when i use the database mirror iwzard to set up mirroring the asynchronous option is disabled.
Thank You Susan
July 15, 2009 at 3:18 am
Asynchronous mirroring is only available on Enterprise edition. So on Standard your only option is synchronous with witness or synchronous without witness.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 15, 2009 at 3:27 am
I dont have much experience with standard edtion.Yes i need sysnchronous without witness but when the principal is down how the mirror side we can make as principal and accessible to the application.Becuase when i stop principal server the mirror server is still in recovery mode.
Thank You,
Susan
July 15, 2009 at 3:39 am
susan.susan28 (7/15/2009)
I dont have much experience with standard edtion.Yes i need sysnchronous without witness but when the principal is down how the mirror side we can make as principal and accessible to the application.Becuase when i stop principal server the mirror server is still in recovery mode.Thank You,
Susan
There are some really good articles on TechNet that outline database mirroring in SQL 2005 on all editions..
July 15, 2009 at 3:45 am
susan.susan28 (7/15/2009)
Yes i need sysnchronous without witness but when the principal is down how the mirror side we can make as principal and accessible to the application.Becuase when i stop principal server the mirror server is still in recovery mode.
You have to manually fail it over. You cannot have automatic failover without a witness.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply