Log shipping

  • We are using SQLServer 2005 and setting up log shipping with a Primary, Secondary and Monitor server.  When I go thru' the setup of log shipping and let SQLServer backup and restore my database, it insists on trying to put the .tuf file in c:\windows\system32.  Is there any way you can change the location of this file?Thanks for any help
  • Have you tried doing a manual restore.  We had to because our primary database was over 100 gig and being shipped a long distance.....was much quicker to backup/zip/ship/unzip/restore then setup log shipping after the fact.   Worked well.

    Not exactly what you were looking for, but hope that this helps.

    Eric

     

  • Hi Eric,

    Yes - I have tried it this way and it works.  I just wondered if anyone had got the automatic way working with the .tuf file in a different location.  On another note, on our secondary server, the Log Shipping monitor is always saying that our Restore is out of date (even though it isn't).  Is yours correct?  I have tried removing log shipping and putting it back on but with no joy.  It might be a permissions thing.

  • I have one server that always says the same thing....

    The problem it is for an old test database that I deleted.  SQL server was not smart enough to clean up all of the log shipping system tables and even though I have done a manual cleanup of them....I still cannot find out where that last entry is....so my one server always says it is out of sync....even though the database or the jobs that were created for the DBATest database are out of synch.....lol

    If you get rid of yours, let me know

    EP

  • I just went thru all of my system tables in the MSDB database.   There were several tables in there with old information that the SQL server didnt clean up.  

  • log_shipping_monitor_alert
  • log_shipping_monitor_error_detail
  • log_shipping_monitor_history_detail
  • log_shipping_monitor_primary
  • log_shipping_monitor_secondary
  • log_shipping_primaries 
  • log_shipping_primary_databases
  • log_shipping_primary_secondaries
  • log_shipping_seoncdaries
  • log_shipping_secondary
  • log_shipping_secondary_databases
  • Try running the following script

    select

    * from Log_shipping_monitor_secondary

    There is a restore threshold column in there that I bet you could reset to something higher than the Threshold aleart

    Worth a try

    EP

  • Hi Eric,

    I will have a look at these tables and see if I can get it cleaned up.  I will let you know how I get on.  2005 is so much fun sometimes

     

  • Viewing 6 posts - 1 through 5 (of 5 total)

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