Solved

How to setup log shipping

Posted on 2009-04-06
1
1,828 Views
Last Modified: 2012-05-06
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)
0
Comment
Question by:staticman4414
1 Comment
 
LVL 32

Accepted Solution

by:
bhess1 earned 250 total points
ID: 24091551
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

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

SQL Server engine let you use a Windows account or a SQL Server account to connect to a SQL Server instance. This can be configured immediatly during the SQL Server installation or after in the Server Authentication section in the Server properties …
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now