Backup procedures for server

  • I have setup a maintenance plan that runs a full backup of a TDE enables database nightly.

    but before it runs the backup it runs a file cleanup task to remove anything older then 1day.

    I was looking at this b/c since I enabled TDE the backup drive doesn't have a lot of free space b/c the backup went from 17GB compress to 80 ish GB.

    At 8 pm The backup system is supposed to pull all data from the backup folder.

    The backup/cleanup runs at 12:05 am aprox 4hrs later

    I was thinking that if A. I know that the backup system got all the data and B. that the full backup completed successfully I wouldn't need any of the transaction log backups prior to creation of the the full backup.

    So my thinking would be after the backup maintenance plan runs the only file i would have in that backup folder would be the full database backups.

    1. Does this make sense?

    2. Am I missing anything that would cause me restore issues down the road? (only removing the files after a validated full backup was taken)

    Thanks!

  • I think this my have gotten lost in the holiday weekend.

  • And what if the full backup that completed successfully won't restore? Completing doesn't mean it's good. If you're using RESTORE VERIFYONLY, that checks the header of the backup file only.

    So, you delete all the tran logs before the full backup. Next day something goes wrong, you go to restore but the full backup's damaged and won't restore. The tran logs are gone, so assuming you still have the previous night's full backup, you restore and lose ~36 hours of data. Is that acceptable?

    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

Viewing 3 posts - 1 through 2 (of 2 total)

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