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

In which file is the transaction was backed up Expand / Collapse
Author
Message
Posted Tuesday, January 22, 2013 11:53 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, February 6, 2014 4:58 AM
Points: 225, Visits: 127
First let me apologize if this is not the correct palace for this topic but it is strongly connected.

when we perform a full database backup the engine marks the place in the database from where all new transaction should be kept in the next transaction log packup.

what is not cleared to me is where is the transaction that started before the full backup started and ends
1. during the full backup ?
2. after the full backup completed ?
3. after a few transaction logs where also backed up after the full backup completed

Backed up in which backup file will I find it ?


for the connivance of the discussion lets say that a full backup takes place once a day and takes about 30 minutes.
Transaction log backup takes palce every 10 minute

The discussed transaction time is about 50 minutes.



Post #1410359
Posted Wednesday, January 23, 2013 12:04 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 @ 10:19 AM
Points: 43,026, Visits: 36,192
1) Included with the database backup and the all log backups that occur while it's running
2) Included with the database backup and the all log backups that occur while it's running
3) Included with the database backup and the all log backups that occur while it's running

Full backups do not have any effect on the log backups that occur. The full backup backs up enough of the transaction log so that it can be restored consistently.

A full backup does not mark where the next log backup should start from, a log backup always backs up from where the previous log backup finished up to current.



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 #1410365
Posted Wednesday, January 23, 2013 12:25 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, February 6, 2014 4:58 AM
Points: 225, Visits: 127
Thanks

My Conclusion from you answer is that if I don't have to keep the transaction log backups that occurred since the transaction stared and prior to the full database backup, in order to be able to restore the database to a point in time if it fails after the backup was done and the transaction finished (all three cases ).

Is my conclusion correct?



Post #1410370
Posted Wednesday, January 23, 2013 12:50 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 @ 10:19 AM
Points: 43,026, Visits: 36,192
Mostly.

You can restore the full, then any log backups. However, what happens if that full is damaged and won't restore? If you've deleted the log backups prior to it, then you won't have the option of restoring a previous full backup and rolling the logs forward.



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 #1410381
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse