none
Failing over database to Mirrored Server RRS feed

  • Question

  • we have a classic ASP application that some how does not have a capability to automatically fail over to Mirrored database,

    i need to manually failover database to mirrored server and then manually connect asp page,

    Please advise precautionary measures needs to be take.


    k

    Friday, December 20, 2013 3:34 PM

Answers

  • This is where monitoring should be put in place. Classic ASP does not have the capability to automatically get redirected to the mirrored instance should a failover occur. You need to define the process that outlines the list of tasks that you will perform should this occur. For example

    • Detect failover
    • Change connection string to point to the mirrored instance

    This will be dependent on how you architect your application. Do you have NLB set up for your application? How does your application connection string look like? Are you using DNS aliases?

    You need to be concerned with your recovery objectives (RPO/RTO) and service level agreement (SLA) because these should be the basis of all your approaches. For example, if you require an RPO and RTO of 1 hour, do you have your database mirroring configuration in synchronous or asynchronous? Do you automate the application redirection or do you manually perform the task? How often do you need to run your monitoring solution so that you immediately get alerted when this occurs?


    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog | Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course


    Friday, December 20, 2013 10:58 PM
    Moderator

All replies

  • If you not configure witness then automatically fail over will not work.
    Friday, December 20, 2013 3:55 PM
  • i know i need to manually failover, 

    but the question is what should ben the concerns and precautionary measures?

    REgards


    k

    Friday, December 20, 2013 4:11 PM
  • This is where monitoring should be put in place. Classic ASP does not have the capability to automatically get redirected to the mirrored instance should a failover occur. You need to define the process that outlines the list of tasks that you will perform should this occur. For example

    • Detect failover
    • Change connection string to point to the mirrored instance

    This will be dependent on how you architect your application. Do you have NLB set up for your application? How does your application connection string look like? Are you using DNS aliases?

    You need to be concerned with your recovery objectives (RPO/RTO) and service level agreement (SLA) because these should be the basis of all your approaches. For example, if you require an RPO and RTO of 1 hour, do you have your database mirroring configuration in synchronous or asynchronous? Do you automate the application redirection or do you manually perform the task? How often do you need to run your monitoring solution so that you immediately get alerted when this occurs?


    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog | Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course


    Friday, December 20, 2013 10:58 PM
    Moderator