Could not retrieve backup settings for primary ID in Log shipping

Posted by user1723139 on Server Fault See other posts from Server Fault or by user1723139
Published on 2012-10-05T13:31:47Z Indexed on 2012/10/08 3:38 UTC
Read the original article Hit count: 429

Filed under:

Logshipping

I am doing log shipping between two Amazon EC2 instances running Windows Server 2008 R2 with SQL Server 2008 R2 standard edition.

Both the instances are in the same domain and I can access the shared folders between the instances. The SQL server service account, agent service account are all running under a domain account.

When I activate log shipping (with stand by mode restore in secondary server), the initial backup gets restored on the secondary.

After that the backup operation is getting failed and i get the following error message:

*** Error: Could not retrieve backup settings for primary ID 'xxxxxx-xxxx-xxxx-xxxx-4d772cd7337e'.(Microsoft.SqlServer.Management.LogShipping) ***

*** Error: Failed to connect to server IP-0A7653F2.(Microsoft.SqlServer.ConnectionInfo) ***

****** Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server.******** 

**The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(.Net SqlClient Data Provider) ***

**----- END OF TRANSACTION LOG BACKUP   -----****

Any ideas?

Related posts about Logshipping

How to achieve the following RTO & RPO with logshipping only using SQL Server?

as seen on Server Fault - Search for 'Server Fault'
Trying to come up with viable backup restore & logshipping solution for achieving the following: 15 minutes Recovery Point Objective (no more than 15 minutes data loss at any time) 5 minutes Recovery Time Objective (must be able to get the db up and running back by 5 minutes) Considering using… >>> More
SQL Server 2008 Logshipping not Restoring

as seen on Server Fault - Search for 'Server Fault'
I am getting the following errors during the restore part of the Logshipping process on my secondary server: 2010-04-01 10:00:01.85 Error: The file 'F:\UK_20100327090001.trn' is too recent to apply to the secondary database 'UK_Backup'.(Microsoft.SqlServer.Management.LogShipping) … >>> More
Biztalk 2009 logshipping with SQL 2008

as seen on Server Fault - Search for 'Server Fault'
Hi, I am setting up biztalk logshipping for Biztalk 2009 database. Following http://msdn.microsoft.com/en-us/library/aa560961.aspx article, I am doing the following to setup biztalk logshipping on destination server: Enable Ad-hoc queries by: sp_configure 'show advanced options',1 go reconfigure go sp_configure… >>> More
Could not retrieve backup settings for primary ID in Log shipping

as seen on Server Fault - Search for 'Server Fault'
I am doing log shipping between two Amazon EC2 instances running Windows Server 2008 R2 with SQL Server 2008 R2 standard edition. Both the instances are in the same domain and I can access the shared folders between the instances. The SQL server service account, agent service account are all running… >>> More
log shipping of biztalk database on SQL server 2008 standard edition

as seen on Server Fault - Search for 'Server Fault'
Hi, I want to do log shipping for biztalk databases on SQL server 2008 standard edition (server A) to another SQL server 2008 standard edition (server B). I was told that for biztalk, logshipping is not like standard logshipping. I was able to find 2 links: http://msdn.microsoft.com/en-us/library/cc296836%28v=BTS… >>> More

Developer IT