July 28, 2008 at 8:27 am
I am evaluating the possible use of log shipping for a database on a server to a disaster recovery site. This database I frequently issue backups against production (grab a transaction log usually) and restore to development for dev's to test and write code. If I setup log shipping, as far as I can understand I will not be able to do that as it would break the log chain. Will it still ship a manual backup of the log? What is the best way to get a copy of prod down to dev on demand?
July 28, 2008 at 9:32 pm
Use the COPY ONLY option for backups. This won't break the backup chain.
August 1, 2008 at 3:56 am
[font="Verdana"]Full & differential backups of log shipped database in primary server won't break log shipping in SQL Server 2005.
If you take a tlog backup of log shipped database in primary server, then the same needs to be restore in secondary server else log shipping will be breaked.[/font]
Regards..Vidhya Sagar
SQL-Articles
August 1, 2008 at 7:40 am
I don't understand how you can just 'grab a copy of the transaction log'. You'll still need to restore the trx log backups made from the last full/diff backup you have up to the current log backup. Wouldn't it be possible to use trx log backups that have already been made, as part of the log shipping process?
As for the 'best way' to get a copy of the production database, it'll depend on your situation. What I used to do was schedule a full database backup during off-hours, restore it, scrub out/change the sensitive data, back that database up, and make that backup available to developers to use to their hearts content.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply