LOG SHIPPING AND REPLICATION

  • Hi,

    I have four databases in production its in replication

    1. one publication database and other three subscriber databases (all the databases in one instance)

    SQL server 2008 r2 standard edition

    Now my requirement want to create the log-shipping for four databases in Dr server.

    Is it possible means

    steps to be configured in Dr

    what need to take care before create log-shipping in dr server.how to check the Fail back if i lose primary

  • Have a read of this in msdn:

    https://msdn.microsoft.com/en-us/library/ms151224.aspx

    This section addresses what is \ isn't possible:

    Log shipping can be used in conjunction with replication, with the following behavior:

    Replication does not continue after a log shipping failover. If a failover occurs, replication agents do not connect to the secondary, so transactions are not replicated to Subscribers. If a failback to the primary occurs, replication resumes. All transactions that log shipping copies from the secondary back to the primary are replicated to Subscribers.

    If the primary is permanently lost, the secondary can be renamed so that replication can continue. The remainder of this topic describes the requirements and procedures for handling this case. The example given is the publication database, which is the most common database to log ship, but a similar process can also be applied to subscription and distribution databases.

    MCITP SQL 2005, MCSA SQL 2012

  • This was removed by the editor as SPAM

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply