December 12, 2012 at 12:46 am
hi ,
you can used copy_only option to take full backup. when transaction log backup job created for same database .
bcoz it will not break lsn squence of database .
December 12, 2012 at 1:45 am
Hemant.R (12/12/2012)
hi ,you can used copy_only option to take full backup. when transaction log backup job created for same database .
bcoz it will not break lsn squence of database .
A FULL backup will not break the log chain LSN if you dont specify the COPY_ONLY option. The only time a log backup is dependent on the FULL backup is when it is the first ever FULL and log backup for the database, or if the database has been changed from Full to Simple to Full.
The only base a FULL backup resets is the differential base
December 12, 2012 at 1:58 am
Hemant.R (12/12/2012)
hi ,you can used copy_only option to take full backup. when transaction log backup job created for same database .
bcoz it will not break lsn squence of database .
Full backups never break the log chain (LSN sequence), no matter what options are specified.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply