Copy only backup on 2012 server - by Juha Haapsaari

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 777865 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/30/2013 3:36:50 AM
Access Restriction Public


When full database copy only backup is taken, next transaction log backup taken afterwards link to copy only backup not to previous normal full or differential backup.

Same problem after updating SQL 2012 SP1. Is this then intended functionality change compared to previous versions of SQL server? At least I could not find a documentation about the functionality change.
Sign in to post a comment.
Posted by Juha Haapsaari on 3/2/2013 at 1:24 AM
If I remember correctly it was not only a bug in UI. If restore commands executed individually in correct sequence:
1. restore last normal full backup
2. restore last differential backup (if exist)
3. restore first transaction log backup taken after last differential or normal full backup -> error if copy only full back has been taken after last normal full or differential backup

If restore commands are executed as presented in UI, so use copy only backup also then restore sequence is OK. So it seems that it's actually a problem where copy only full backup really is really used as reference for transaction log backups taken afterwards.
Posted by Microsoft on 2/21/2013 at 10:42 AM
Thank you for reporting this issue - we are investigating and will update you when we have more information.


Posted by Microsoft on 2/20/2013 at 11:40 AM
Looks like a bug in the UI for backup set to restore - I was able to repro in SQL12 RTM version, but if you click on the timeline, previous backups are available, if you select the corresponding full backup, then the backup set will change to show the original full backup.