Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1033
  • Last Modified:

DB Mirroring / Auto-Failover, but ODBC?

I think I have a problem.

I'm all excited about finally getting auto-failover in place for some of our databases, using High Safety configuration and mirroring.

For client apps, I know we can edit the connection strings to identify the failover server.

But...it just hit me that some of our backbone (third-party) applications use ODBC DSNs to identify our primary server.

Crap!  I really want to use this configuration, and not a Windows Server cluster or anything like that.

What are my options?  I cannot convert this app to use ODBC.  And I cannot convert it to allow OLEDB connections.

Thanks for any insight on this.
0
bamapie
Asked:
bamapie
1 Solution
 
dqmqCommented:
>What are my options?  I cannot convert this app to use ODBC.  And I cannot convert it to allow OLEDB connections.

That's a bit confusing because the issue was with respect to 3rd party app's that DO use ODBC.  In any case, if the ODBC DSN's are configured with the Native Client provider, then you do get the option for a Mirroring failover server.

Beyond that, you would need to look for some infrastructure in your network layer that redirects DNS assignments or reassigns IP addresses.  Not quite automatic, though.  

0
 
mnachuCommented:
I guess your infrastructure guys can add an entry to the DNS server that has the name of the failed server which maps to the new running server. Wouldn't something like re-directing solve your problem?

Regards,
Nachi
0
 
dhlotterCommented:
High Availability operating mode provides durable synchronous transfer between the principal and mirror databases, as well as automatic failure detection and automatic failover.

High Safety operating mode transfers transactions synchronously, but it does not have a witness server. The synchronous transfer guarantees that all transactions committed at the principal are fi rst committed at the mirror, and it requires the same performance considerations as the High Availability operating mode. However, the lack of a witness prevents automatic failover to the mirror if the principal fails. If the principal fails in High Safety operating mode, you must promote the mirror manually to serve the database. Because High Safety operating mode’s synchronous transfer can affect application performance but does not offer the benefi t of automatic failover, this operating mode is not recommended for normal operations. You should confi gure a Database Mirroring session in High Safety operating mode only when you need to replace the existing witness server. After you have replaced or recovered the witness, you should change the operating mode back to High Availability operating mode.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
dhlotterCommented:
in other words, you would not be able to use high safety mode for automatic failover.
0
 
bamapieAuthor Commented:
dhlotter:  I mixed up my terms.  I meant High Availability.
0
 
bamapieAuthor Commented:
dqmq:

>In any case, if the ODBC DSN's are configured with the Native Client provider,
>then you do get the option for a Mirroring failover server.

Where would I see / configure this?

Thanks
0
 
bamapieAuthor Commented:
Never mind, I see it.  Awesome.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now