Post reply

Log Shipping

  • August 10, 2009 at 2:48 pm

    #208375

    I was attempting to configure log shipping from IDQ-SP.DB to IDQ-UK.DB, and, even though I incurred no errors and the configuration was properly set up on the secondary server, the primary server appeared as though no action had been taken. The LSBackup_DB and LSAlert_IDQ-SP were not created and, when I click on IDP-SP.DB's Properties -> Transaction Log Shipping, the checkbox is not populated.

    I ran the stored procedures on the primary that would render information about the primary and primary -> secondary info, but no information was returned.

    Any assistance is appreciated.

    Thanks.

  • August 10, 2009 at 6:21 pm

    #1037164

    even though I incurred no errors and the configuration was properly set up on the secondary server, the primary server appeared as though no action had been taken.

    Thanks.

    How did you configure logshipping? What is the recovery model of the database that you want to logship?

  • August 10, 2009 at 6:32 pm

    #1037167

    Thanks for your reply. I have attempted to configure log shipping using both the wizard and by using a script (that is generated by SSMS). The database is using a full recoverery model.

  • August 10, 2009 at 6:59 pm

    #1037170

    When you configure logshipping through wizard once final step is done, does it say that logshipping configuration is successful?

  • August 10, 2009 at 9:21 pm

    #1037205

    Yes.

  • August 11, 2009 at 6:28 am

    #1037353

    is your backup generated in the setup network folder? Did you give sufficient rights on that directory?

    Vivek Shukla - MCTS SQL Server 2008

  • August 11, 2009 at 7:30 am

    #1037394

    rob.shelton (8/10/2009)

    Yes.[/quote

    Please execute the following and see whether it has any data in that or not on Primary Server

    select top 1 * from msdb.dbo.log_shipping_primaries

    select top 1 * from msdb.dbo.log_shipping_primary_databases

    on Secondary server execute the following

    select top 1 * from msdb.dbo.log_shipping_secondary

    select top 1 * from msdb.dbo.log_shipping_secondary_database

    Please see if this returns any results or not.

    If this returns results, see thev value for backup_job_id in msdb.dbo.log_shipping_primary_databases and then extract the job name and see whether backup job is there or not. This backup job is transaction log backup job.

    Similary check for copy and restore jobs in log_shipping_secondary_database and see whether these jobs are created or not.

    If you don't find any results, then logshipping is not configured for the database for which you are trying to configure.

  • August 11, 2009 at 9:40 am

    #1037527

    Nothing was returned on the primary servers, but information was returned from the secondary servers.

    When I attempt to configure log shipping using the SSMS wizard or the scripts generated by the wizard, neither gives any indication of a failure or an error. However, only the secondary server is set up correctly.

    The primary, for all appearances, looks as if nothing was configured. The associated jobs aren't created and the primary database's log shipping configuration checkbox isn't checked.

  • August 11, 2009 at 10:09 am

    #1037569

    Hi Rob,

    I don't know what exactly is happeneing. If possible can you run a trace on primary server, by putting a filter running with your account and configure logshipping, that will capture details. This is the only way we can figure it out, why logshipping is not getting configured on primary.

    Murthy

Viewing 9 posts - 1 through 8 (of 8 total)

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