Log Shipping Error

• SQL-Sgt

  SSC Enthusiast

  Points: 178

  More actions

  September 14, 2016 at 9:25 pm

  #1901004

  The issue is the secondary server was renamed. If you check the servername you will notice it is incorrect.

  SELECT @@SERVERNAME

  These commands will correct the server rename and then it requires a restart of SQL Server.

  sp_dropserver 'WRONGNAME'

  GO

  sp_addserver 'NEWNAME', local

  GO

  If you cannot restart the SQL Server immediately then you will need to correct the secondary servers copy job and restore jobs commands.

  "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\sqllogship.exe" -Copy 6494A057-7D63-4DAD-9A3F-1EBFCA98E1EE -server WRONGNAME

  "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\sqllogship.exe" -Restore 6494A057-7D63-4DAD-9A3F-1EBFCA98E1EE -server WRONGNAME

  Change it to the new name of the instance

  "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\sqllogship.exe" -Copy 6494A057-7D63-4DAD-9A3F-1EBFCA98E1EE -server NEWNAME

  "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\sqllogship.exe" -Restore 6494A057-7D63-4DAD-9A3F-1EBFCA98E1EE -server NEWNAME

• -=JLK=-

  Valued Member

  Points: 63

  More actions

  May 1, 2020 at 2:40 pm

  #3748079

  This solution worked for me.  I had cloned the primary server vm and renamed it but didn't rename the DB server internally.  Once I used the sp_Dropserver/sp_Addserver AND updated the Copy/Restore jobs, everything worked fully.

  -=JLK=-
  Theory is when you know something, but it doesn't work.
  Practice is when something works, but you don't know why.
  Programmers combine theory and practice: Nothing works and they don't know why.