When Should I Delete Database Backups?

Published On: 2015-03-18By:

Recently this question came up with a client that I’ve been working with. In this case the problem was that disk space alarms were going off for the disk which held the database backups. The proposed solution was to change the log backup retention from 24 hours to 16 hours.

The problem with this solution, which I pointed out is that from 5pm until midnight you now have no way to do any log restore operations which means that you’ve lost your point in time restore capabilities.

Log and full backups shouldn’t be deleted from the disk until the full backup from the next cycle of backups has been completed. This way you are sure that you’ve always got a full backup to restore from. In a perfect world I’d like to see 2-3 days worth of full and t-log backups kept on disk so that if there is ever a problem with a corrupt database backup you can restore from the prior full backup and then roll two cycles of t-log backups forward.


Contact the Author | Contact DCAC


Globally Recognized Expertise

As Microsoft MVP’s and Partners as well as VMware experts, we are summoned by companies all over the world to fine-tune and problem-solve the most difficult architecture, infrastructure and network challenges.

And sometimes we’re asked to share what we did, at events like Microsoft’s PASS Summit 2015.

Awards & Certifications

Microsoft Partner   Denny Cherry & Associates Consulting LLC BBB Business Review    Microsoft MVP    Microsoft Certified Master VMWare vExpert
INC 5000 Award for 2020    American Business Awards People's Choice    American Business Awards Gold Award    American Business Awards Silver Award    FT Americas’ Fastest Growing Companies 2020   
Best Full-Service Cloud Technology Consulting Company       Insights Sccess Award    Technology Headlines Award    Golden Bridge Gold Award    CIO Review Top 20 Azure Solutions Providers
Share via
Copy link