<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Backups
»
Create a policy to avoid backups withou...
18 posts, Page 1 of 2
1
2
»»
Create a policy to avoid backups withou copy_only option
Rate Topic
Display Mode
Topic Options
Author
Message
hillock666
hillock666
Posted Wednesday, October 20, 2010 12:36 AM
Valued Member
Group: General Forum Members
Last Login: Tuesday, May 03, 2011 2:56 AM
Points: 69,
Visits: 92
Hi.
We have several databases in full recovery model. Daily we make full backups, but sometimes we need take a full backup for development purposes. I would like guarantee that everyone "remember" check copy_only option. Can I create a policy, or a DDL trigger that avoid this mistake?
Thanks in advance,
Fran
Post #1007482
GilaMonster
GilaMonster
Posted Wednesday, October 20, 2010 2:15 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:43 AM
Points: 37,690,
Visits: 29,948
Are you doing diff backups? If not, it's not so critical to use the copy_only option
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1007516
hillock666
hillock666
Posted Friday, October 22, 2010 4:42 AM
Valued Member
Group: General Forum Members
Last Login: Tuesday, May 03, 2011 2:56 AM
Points: 69,
Visits: 92
Since I 'm not doing differentials backups, hasn't this option any effect?
Thank you!
Post #1009073
GilaMonster
GilaMonster
Posted Friday, October 22, 2010 8:24 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:43 AM
Points: 37,690,
Visits: 29,948
Correct. No full backup (with or without copy_only) breaks the log chain.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1009231
Wildcat
Wildcat
Posted Friday, October 22, 2010 1:28 PM
Old Hand
Group: General Forum Members
Last Login: Wednesday, April 10, 2013 10:10 PM
Points: 307,
Visits: 1,390
GilaMonster (10/22/2010)
Correct. No full backup (with or without copy_only) breaks the log chain.
Gail, I am confused here.
For example, from FULL BAKCUP A to FULL BACKUP B, we have a log chain. If you issue a FULL backup C without COPY_ONLY between A and B, then, you break the previous log chain A to B.
Right?
According to Microsoft, you should backup log after the Full backup C to establish a new log chain.
Post #1009461
Ray Mond
Ray Mond
Posted Friday, October 22, 2010 10:35 PM
Old Hand
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 2:28 AM
Points: 343,
Visits: 1,510
For example, from FULL BAKCUP A to FULL BACKUP B, we have a log chain. If you issue a FULL backup C without COPY_ONLY between A and B, then, you break the previous log chain A to B.
Right?
No. You can make as many full backups as you want between full backup A and B, and you will not break the log chain.
According to Microsoft, you should backup log after the Full backup C to establish a new log chain.
Could you please provide the URL to the article? I would like to see the context the recommendation was made in.
Thanks.
Ray Mond
TLogInfo
- the only FREE tool to analyse your transaction logs. Download
here
.
SQL BAK Reader
- the only FREE tool to inspect your SQL Server backup files without using SQL Server. Download
here
.
Post #1009561
ps.
ps.
Posted Friday, October 22, 2010 11:32 PM
SSCrazy
Group: General Forum Members
Last Login: Thursday, May 02, 2013 2:32 AM
Points: 2,236,
Visits: 3,620
Full Backups do not break transaction log chain.
However they do reset differential backups. If you take full backup wth copy_only option, the differential backup will contain pages that were modified after the last full backup without copy_only option.
Pradeep Singh
Post #1009564
ps.
ps.
Posted Friday, October 22, 2010 11:35 PM
SSCrazy
Group: General Forum Members
Last Login: Thursday, May 02, 2013 2:32 AM
Points: 2,236,
Visits: 3,620
If you have truncated the log, you will need to take a full OR diff backup to start a new log chain.
another case, if ur db has never been backed up(full recovery) then until you take full backup a new log chain wont start. db behaves as if it were in simple recovery mode.
Pradeep Singh
Post #1009565
GilaMonster
GilaMonster
Posted Saturday, October 23, 2010 3:11 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:43 AM
Points: 37,690,
Visits: 29,948
Wildcat (10/22/2010)
If you issue a FULL backup C without COPY_ONLY between A and B, then, you break the previous log chain A to B.
Right?
Wrong.
Full backups do not and never have broken the log chain.
It's trivial to test and, if you want, I can find a blog post from the former program manager of the Storage Engine stating and proving this.
The only things that break the log chain are:
* Switch to simple recovery
* Backup log with nolog/truncate only
* Deleting a log backup (won't stop you taking log backups, will stop you recovering with them)
According to Microsoft, you should backup log after the Full backup C to establish a new log chain.
Link please.
I need to write a scathing email to either the author or the MS documentation people if such an official recommendation exists
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1009577
Wildcat
Wildcat
Posted Thursday, October 28, 2010 11:54 AM
Old Hand
Group: General Forum Members
Last Login: Wednesday, April 10, 2013 10:10 PM
Points: 307,
Visits: 1,390
[quote
The only things that break the log chain are:
* Switch to simple recovery
* Backup log with nolog/truncate only
* Deleting a log backup (won't stop you taking log backups, will stop you recovering with them)
[/quote]
Sorry, after reading Microsoft document 3 times, I misunderstood the concept.
Thanks, Gail.
Post #1012546
« Prev Topic
|
Next Topic »
18 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
