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