Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2009
    Posts
    3

    Unanswered: Log Shipping Trouble on a larger db

    I am attempting to create log shipping between our production server and a server that has been created as out standby source. The primary database BACKUP file is approximately 157 GB. It is taking us about twenty five minutes to do a FULL BACKUP and about another fifty minutes to send the the BACKUP file over to the secondary server. From there it takes about another thirty five minutes to RESTORE the database in STANDBY. Upon completion I have been attempting to use the Log Shipping Wizard on the
    primary server to set up the log shipping between the primary and secondary servers. Upon completing the required information for the wizard to set up the log shipping I can see the three SQL jobs created (lsbackup on the primary and lscopy and lsrestore on the secondary) but the backup job fails from the start.

    I have set up smaller log shipping jobs without much difficulty. However, this one has me completely stumped as to what to do. I have tried scripting based on other succesful log shipping jobs, re-doing the STANDBY database while the rest of the log shipping jobs remain in place. I have tried breaking everything and scripting the jobs one by one. Nothing seems to work. Does anyone have any suggestions how I can establish log shipping for this database?

    Your help would be greatly appreciated.

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Is there any error associated with the backup jobs/ Maybe in the SQL server errorlog?

  3. #3
    Join Date
    Dec 2009
    Posts
    3
    Thank you for your quick response. The backup job appears to be fine, but on the secondary server the copy and restore jobs are giving this error....


    COPY
    *** Error: Could not retrieve copy settings for secondary ID '869ec87f-ac6f-43d9-aec3-deddc1e2e8e9'.(Microsoft.SqlServer.Management.LogS hipping) ***<nl/>2009-12-09 17:15:01.18 *** Error: The specified agent_id 869EC87F-AC6F-43D9-AEC3-DEDDC1E2E8E9 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***<nl/>2009-12-09 17:15:01.18 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShippin g) ***<nl/>2009-12-09 17:15:01.18 *** Error: The specified agent_id 869EC87F-AC6F-43D9-AEC3-DEDDC1E2E8E9 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***<nl/>2009-12-09 17:15:01.18 *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShippin g) ***<nl/>2009-12-09 17:15:01.18 *** Error: The specified agent_id 869EC87F-AC6F-43D9-AEC3-DEDDC1E2E8E9 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provi,00:00:01,0,0,,,,0

    RESTORE
    Error: The specified agent_id BB2F2C26-39DF-4C3E-B83B-9F1D4475F0DB or agent_type 2 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***,00:00:01,0,0,,,,0

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Any help here:

    Log Shipping Copy Fails

  5. #5
    Join Date
    Dec 2009
    Posts
    3
    Thank you very much for your help! It was a connection issue between the Secondary Server and the Primary. Once that was changed it sucked up all of the tran lof backups and now has a whole lot of tran log restores to do. Thank you again!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •