Log shipping: Secondary backup

Last Post 03 Mar 2005 03:45 PM by jgharper. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
jgharper
New Member
New Member

--
02 Mar 2005 07:21 PM
I would like to know how to setup log shipping so I can backup the 'log shipped to' server (failover). When I try to perform a backup, I get a 'warm-standby' error, and it won't backup.
thanks
jgharper
New Member
New Member

--
03 Mar 2005 03:45 PM
I found this snippet from the link (also included).





http://www.microsoft.com/resources/...c1361.mspx



“Generating Database Backups from the Secondary

Since the log shipped database is only a small increment of time out of sync with the primary database, it is a good idea to use it to generate the full database backups. This would keep the primary production server free of the potential overhead and contention incurred by a daily (or scheduled) backup.
It is also important to backup the msdb database on all servers involved with log shipping, including the log shipping monitor. This database contains all the configuration and status information for log shipping. “

That makes it sound like it is not only possible to backup the secondary server, but it is preferred?

jgharper
New Member
New Member

--
04 Mar 2005 02:38 PM
Found my answer:

"Here's MicroSoft's correction to the documentation.


SUMMARY
This article contains a correction and information about an error message that relates to the Microsoft Press book "Microsoft SQL Server 2000 Resource Kit"; ISBN 0-7356-1266-8.
MORE INFORMATION
In the "Microsoft SQL Server 2000 Resource Kit", page 385, in the "Generating Database Backups from the Secondary" topic, the first sentence of the topic states:
Since the log shipped database is only a small increment of time out of sync with the primary database, it is a good idea to use it to generate the full database backups.

The preceding statement implies that you can back up the log shipped database on the secondary server, which is incorrect. The log shipped database on the secondary server is in a read-only state and you cannot use that database to generate any type of SQL Server backup.

The Log Shipping process leaves the database on the secondary server in either a STANDBY or a LOADING status depending upon which option you select when you configure Log Shipping. Both STANDBY and LOADING are read-only states, which prevents any writes to the transaction log. Because the backup process needs to log its operations (backup history), and changes to the transaction log are disallowed, SQL Server does not allow you to perform backups performed against a log shipping secondary database.
The information in this article applies"



You are not authorized to post a reply.

Acceptable Use Policy