June 7, 2006 at 2:03 am
I used to use log shipping on SQL 2000 and I was able to run a backup of the secondary DB that I could archive this to DVD occassionally.
I am now using SQL 2005 and it seems this capability has been removed? I am unable to back up the secondary DB - does anyone know if this is possible?
If not, is it possible to do a full backup of the primary DB for archiving without affecting the log shipping?
TIA
Howard
June 8, 2006 at 7:16 am
I don't know about the SQL 2K5 question, but you can make a full back-up without affecting log-shipping. Thanks.
Chris
June 8, 2006 at 7:21 am
Thanks - I have now found the new backup option COPY_ONLY has been added to SQL 2005 and will do a backup on the Primary DB without impacting the log shipping state.
Sadly I don't seem to be able to backup the readonly/standby Secondary DB.
June 8, 2006 at 11:10 am
I'm hoping this comment was a typo "I used to use log shipping on SQL 2000 and was able to run a backup of the secondary DB" because you can't run a SQL Backup on the secondary when it is in a warm-standby state. Also, you said "I am now using SQL 2005 ... I am unable to back up the secondary DB". I'm guessing you meant the primary here too.
Out of curiosity, what error message did you get when you tried to do a full backup of the primary database in SQL 2005? Since a full backup doesn't affect Log Shipping in SQL 2000 I would think 2005 would be the same. I was just wondering because we haven't upgraded our Log Shipping pair yet.
June 8, 2006 at 11:14 am
I am pretty sure that's what we did.. but it was a couple of years ago when I worked on that particular SQL2K project. Maybe it wasn't...
I didn't get any error on the primary - I knew that backing it up might truncate the transaction log and corrupt the Log Shipping - I've done that before.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply