For LogShipping

    General discussion

  • Require some assistance from users, regarding log shipping. Being aware of normal setup & working I am looking for some guidance in log shipping internals or indepth working of log shipping. Tried hard but out of luck to find it on the INet or its undocumented.
       Regarding log shipping I'm aware of some facts like opening ports
         135 - required by SQL Agent to copy backup files to shared folders on the standby server.
         137/138/139 or 445 required to use UNC shares.
    Some errors or bugs like (3154 / 170) faced when keeping all log backups in the saME directory (sql 8). This is all that I know about log shipping out of books. May you share some more...
    Wednesday, November 17, 2010 4:49 AM

All replies

  • Good reading

    Best Regards, Uri Dimant SQL Server MVP
    Wednesday, November 17, 2010 8:04 AM
  • Under HyperV, turning off host with guests running. They are saved with no dataloss hoever SQL agent jobs are struck with their current readings as seen in JobActivity Monitor and next time host comes up log shipping or any jobs are not running automatically unless you; (a) delete and recreate the schedule (b) manually run the jobs at once. [So] Is there some thing available for a fix on this. (tested on SQL 9 SP3 & 10)
    Monday, November 29, 2010 2:13 PM