How to setup log shipping

I am trying to setup log shipping from one SQL2008 server to another SQL2008 server for disaster recovery purposes. I had read instructions and all seems to setup well, but I keep getting the error below on the primary server.  I am not positive I have everything setup correctly as this is my first time setting this up, but I followed directions found on the net and they seemed straight forwards. Connectivity between the two servers seems fine, but the primary never writes out the first log even.  I did notice a new file was created in the log directory on the secondary server called. "databasenamedatnumbers.tuf"   I am not sure what the TUF file is? But the database name is the one I am testing with so I am sure it is signifigant.

Thanks
Joe

Message
2009-04-06 13:45:01.19      *** Error: Could not retrieve backup settings for primary ID 'aec07870-0176-4225-8b53-ca2d152d81c0'.(Microsoft.SqlServer.Management.LogShipping) ***
2009-04-06 13:45:01.19      *** Error: The specified agent_id AEC07870-0176-4225-8B53-CA2D152D81C0 or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2009-04-06 13:45:01.19      *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2009-04-06 13:45:01.19      *** Error: The specified agent_id AEC07870-0176-4225-8B53-CA2D152D81C0 or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2009-04-06 13:45:01.21      *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2009-04-06 13:45:01.21      *** Error: The specified agent_id AEC07870-0176-4225-8B53-CA2D152D81C0 or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2009-04-06 13:45:01.21      ----- END OF TRANSACTION LOG BACKUP   -----

Exit Status: 1 (Error)
staticman4414Asked:
Who is Participating?
 
Brendt HessConnect With a Mentor Senior DBACommented:
There are a few possible issues that can cause this that I know of.  Security is one - is the agent's security sufficient to access the log directories on all of the servers?  Setting the SQL Server agent to use a domain account, and ensuring that the domain account has the needed privs is the best way to handle this case.

Other issues can crop up if you add an additional secondary, or if you are working on a cluster.  See the link below for concise descriptions of these issues:

http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/634851b4-d6e6-4f76-bfa3-5bd9dae6de77/
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.