Post reply

Copy Only Full Backups

  • August 8, 2017 at 5:12 am

    #338675

    Hi,

    I know that the copy only option on a Full backup doesn't update the LSN of the database, and therefore doesn't conflict with other backup routines which may include differential and transaction log backups.
    I've only ever had the need to use the copy only option for ad hoc backups, while my normal scheduled backups are running Full backups with Tlog backups.

    However, I've just inherited a server which has a SQL Server maintenance plan that isn't doing any differential or Tlog backups, but the full backup job is set to Copy Only.
    Other than the LSN of the databases being very old, is this a problem?
    Does having a very old LSN cause a problem anywhere else in the system?

    I'm tempted to change this server to bring it in line with all our other ones, however it's going to be decommissioned at the end of the year.
    If having old LSN's isn't going to be a problem anywhere, I'll leave it as it is.
    If it might cause a problem, I'll probably just take a full backup without copy only to update them.

    Thanks for your help
    Steve

  • August 8, 2017 at 5:27 am

    #1954433

    Steve Smith-163358 - Tuesday, August 8, 2017 5:12 AM

    Hi,

    I know that the copy only option on a Full backup doesn't update the LSN of the database, and therefore doesn't conflict with other backup routines which may include differential and transaction log backups.

    Not entirely correct.
    Copy_only full backups don't reset the differential base, meaning it doesn't change which full backup the next differential is based on. That is the only difference to a normal full backup.

    The DB's last LSNs (log sequence number) are updated with every single change to the DB.

    Other than the LSN of the databases being very old, is this a problem?

    The LSN won't be old. It's not a problem.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 8, 2017 at 5:39 am

    #1954437

    Hi,

    Thank you for the quick reply.
    I was definitely confusing LSN's and differential bases there. sorry.

    So, just to be sure, there's no problem with a very old differential base.

  • August 8, 2017 at 6:12 am

    #1954442

    Steve Smith-163358 - Tuesday, August 8, 2017 5:39 AM

    Hi,

    Thank you for the quick reply.
    I was definitely confusing LSN's and differential bases there. sorry.

    So, just to be sure, there's no problem with a very old differential base.

    GilaMonster - Tuesday, August 8, 2017 5:27 AM

     It's not a problem.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 8, 2017 at 6:24 am

    #1954449

    thank you very much as always

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply