Log Shipping Jobs Never Get Created

  • Hi

    I have primary and secondary Windows 2003 servers running SQL Server 2005 9.0.1399. These servers aren't part of a domain.

    I have successfully been running transaction log shipping from the primary to the secondary server for some months. However we now have to replace the secondary server with something with more performance and so I've set up an identical (as far as I can tell) replacement secondary server.

    The problem I'm encountering is when I try and set up transaction log shipping between the primary and the replacement servers. When I do this the database gets copied to the secondary server OK and it's restored into standby more OK. However the jobs don't get created on the secondary server and so log shipping doesn't happen.

    No errors are returned to the primary server during the job creation stages of log shipping setup (I'm using SQL Server Management Studio to do the set up). Also no errors are reported in the event logs on the secondary server; but no jobs are listed under the agent.

    I've also tried copying the creation script out of Management Studio across to the secondary server and running it against the server. All the command are executed OK; but no jobs appear in the jobs list.

    I tried manually creating a job on the secondary server and this worked fine so it doesn't appear to be an issue with job creation per se.

    Can anyone suggest why this isn't working? I've been at this for days and it's driving me nuts :w00t:

  • You probably need to add the new sql server to the list of servers that the production server can access to use the sp_addserver to add additional log shipping servers. Also make sure that your production server is listed when you run these commands and that your srvstatus is 1089 if not fix it by using the sp_dropserver and sp_addserver

    select * from sys.sysservers where srvid=0

    select @@servername

    select * from sys.servers

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

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