Logshipping - SQL server 2008 R2

  • Recently logshipping is configured on one of the sql instances in our environment between two different sql isntances. Everthing looks good other than primary server Lsalert job. It keeps failing on the primary instance. When I verify the log shipping tables on the primary sql instance the Secondary name was updated wrongly. that means seconday server name is udpated as primary server. it' causing this problem. both sql instance are newly built.

    Does anybody had/heard this issue before?

    Thanks.

Viewing 0 posts

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