I have a production database where I run full DB backups every Sunday at 2AM and log backups every night at 3AM. The weekly full backups are around 100MB, while the log backups are around 1MB. But the log backup running immediately after th开发者_如何学Goe full backup (one hour after) is almost as big as the full backup (100 MB).
It's not a problem, but I'm curious as to why. Can anyone provide some insight?
Is the weekly full backup part of a maintenance plan and/or are you reorganizing/recreating indexes before the full backup? An index reorganization would explain the large logfile.
one thing to check wouldbe if the wildcard/path of the log backup is picking up some archives, or if the large backup is generating enormous log files for some reason...
Are you truncating or shrinking the log after the full backup?
精彩评论