Log shipping hell?? help!

  •  

    To all gurus out there, help!

    I am not sure how to help you on that,  Nevertheless, I am interested to know if you can help me out with my log shipping.  For two days now, I have been trying to get log shipping going without any luck.

    I have two SQL servers that I'm doing log shipping testing on.  One Enterprise Edition, and one developer's Edition.  On ServerA, I am setting it up as a primary and monitor server.  On ServerB, it is the read-only log shipped server. 

    After I created the initial backup restore on ServerB from ServerA, none of the sequencial logs are shipped or copied to ServerB.  All SQLagents are running under my Windows NT account and I also have admin right from my NT account to these two servers.  I have shared file folders on both network share drive and backup drives.  Again, permission doesn't seems like an issue since my first restore on ServerB was successful.

    The Logshipping monitor keep showing that the transaction logs are not being copied.  I went into SQL agent jobs and Copying and restore on ServerB job history was all successful.

    Is there any other trick I have to teach this puppy to behave like MS is promising?   Your time and help is so much appreciated.

    thanks

    Jon

    DBA/OLAP Developer -
    San Francisco, CA

  • The copy jobs task will say "successful" if it thinks there's nothing to do when it runs. 

    Edit this job step, go to advanced tab, setup an output file to log the actual output of the step.  Then read this file after the task has run.  If any files were actually copied you'll see bunch of text, including 'Copied N files" where N may be 1 or more.  If not, maybe you'll see info that helps track down the problem. 

    We run SQLServer & SQLAgent w/same account on both machines, never had any permissions problems, has always worked the first time.  If it's taking you long time for the initial restore might be good to do testing w/pubs or northwind until you get it all working right--with these small DBs you don't feel bad about discarding the whole thing & starting over.

     

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

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