log shipping failed, until i changed the SQLServer srvc account

  • I thought log shipping permissions were mostly based around the agent job account, specifically:

    1. Does agent on primary server have access to backup share.

    2. Does agent on secondary have access to copy backups to dest share.

    3 Does agent on secondary have access to restore backups from dest share.

    log shipping restore job would not work for me. I kept getting an error "cannot open backup device...Operating system error 5". The agent account was given full admin access to server and sql server ( for testing), but no luck.

    Only after I changed the sql server account for the sql server srvc on the secondary to match that of the agent would the restore job work.

    This proves to me that the sqlSrvr service account needs access to the backup dest share also.

    why is this?

  • The agent does the copy, but the restore is always handled by the engine. The log shipping agent (sql agent or proxy accnt) "asks" the engine to perform a restore, just like when you submit a restore command from SSMS. You (and your account) are not performing the restore, the engine is.

  • Makes perfect sense. Thanks!

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

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