Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Log backups while Full/Differential backups are running Expand / Collapse
Author
Message
Posted Wednesday, April 24, 2013 3:15 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
pdanes (4/23/2013)
I assume then, that the reading of log records is a one-time event? That is, after doing the primary read, it catches up with the log records once, and doesn't continually go back and check for more transactions that may have accumulated while it was catching up the previous transactions?


The backup process reads the data files (extent at a time), after finishing it reads and adds to the backup file all the log records from time that the backup started or oldest open transaction at the time the backup completed, whichever is older (I incorrectly said 'started' earlier) to the last log record at the time that the data copying portion completed. Since that is done after the data copying portion completed, that's a fixed portion of the log and can't change further (no need to back up log records that were added while backing up log records, they're not needed for a consistent restore).

So, short of doing a restore to someplace safe and examining the data manually, there's no real way of knowing at exactly what point the backup captured the database, except that it is internally consistent?


You can pretty much say it's the time that the backup completed, because unless you have some odd case where half the database changes during the backup, the data copying portion of the backup is the vast majority of the time.



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 #1445813
Posted Thursday, April 25, 2013 10:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 30, 2014 6:14 AM
Points: 9, Visits: 49
just for me to understand the point, so when there is atrasaction log backup will can not do differential backup at the same time or what
Post #1446615
Posted Thursday, April 25, 2013 3:31 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, October 14, 2014 11:19 AM
Points: 340, Visits: 954
GilaMonster (4/24/2013)
You can pretty much say it's the time that the backup completed, because unless you have some odd case where half the database changes during the backup, the data copying portion of the backup is the vast majority of the time.

Ok, thanks for the info. Some of these discussions sure get involved, considering how simple a question sets them off.
Post #1446737
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse