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

Confusion regarding which full-backup file to apply on secondary in Log shipping Expand / Collapse
Author
Message
Posted Thursday, February 28, 2013 9:56 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, June 26, 2014 1:18 AM
Points: 90, Visits: 135
Hi we have a log shipping configured at one of client side and is out of shrink for log time . Now client what has happened is that client has taken full backup of database of say on this 27 at 1.00 am and simultaneously transaction log backup job(of log shipping) was running , now on this 28 client took another full backup of same database , also transaction log backup is running and i have all backup file.

My understanding is that due 28 th full backup all transaction backup file generated after 28, 1.00 am must have there LSN changed and so i ,must apply full backup file of 28th and then apply transaction log in order to brink secondary in shrink with primary but my friends say we can apply 27 backup file and then apply all transaction log backup file and as such no LSN change is broken.

please tell me who is correct and
Does file generated on 27 can be applied and then apply each transaction log files
Post #1425149
Posted Thursday, February 28, 2013 10:47 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 7:20 AM
Points: 38, Visits: 432
Hi Anoop,
The Full Database backup taken on 28th is sufficient enough and have all the transaction changes till the 28th. You can apply the 28th full backup and all the Transactional log backups(.trn) after that to bring the Secondary back In-Sync.
Post #1425189
Posted Thursday, February 28, 2013 10:53 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 12:45 PM
Points: 199, Visits: 1,500
Both scenarios are valid as long as you have all of the log files. Full backups won't interfere with the LSN of the transaction log backups.
Post #1425199
Posted Saturday, March 2, 2013 12:38 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, June 26, 2014 1:18 AM
Points: 90, Visits: 135
Hi plz tell me when is LSN chain breaks in case of log shipping.

And as per my knowledge log transactions are dependent one full database backup files and for in that case LSN number is important.
Post #1425830
Posted Saturday, March 2, 2013 5:50 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 12:45 PM
Points: 199, Visits: 1,500
The LSN chain for log shipping is only broken if a log is lost or corrupt. There are other scenarios, but all would envolve using differential backups and mutliple full backups.
Post #1425846
Posted Saturday, March 2, 2013 6:06 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:05 AM
Points: 42,829, Visits: 35,961
anoop.mig29 (3/2/2013)
And as per my knowledge log transactions are dependent one full database backup files and for in that case LSN number is important.


Not true.

Differential backups are dependent on one specific full backup, log files are not.



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 #1425847
Posted Sunday, March 3, 2013 7:40 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, June 26, 2014 1:18 AM
Points: 90, Visits: 135
GilaMonster (3/2/2013)
anoop.mig29 (3/2/2013)
And as per my knowledge log transactions are dependent one full database backup files and for in that case LSN number is important.


Not true.

Differential backups are dependent on one specific full backup, log files are not.


Gail thanks for your reply . can u clarify one more doubt , that if i have full backup and log backup then do i require differential backup or not . if not then why options of differential backup are provided
Post #1425948
Posted Sunday, March 3, 2013 8:10 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:05 AM
Points: 42,829, Visits: 35,961
Require, no. Full and log can restore to a point in time. There are advantages and disadvantages to differentials, there are many places where they are useful.

Consider, for example, a scenario where a full backup takes 4 hours but the only time you have a 4 hour maintenance window is on a Sunday. What do you do for backups?



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

Add to briefcase

Permissions Expand / Collapse