May 4, 2004 at 9:21 am
How do the full and transaction logs relate to each other? For example, if I have a log of transactions that have been logged and my FULL back-up is run, will my next transaction log backup include those transactions, or will those have been captured in the full backup?
I preform a reindex on the DB and then do a full backup expecting that the transaction log backup would be small right after the full backup is performed, but it's huge. It's obviously capturing the log entries from the reindex.
I thought transaction log backups were differential and started from the last full backup. Is this incorrect?
Thanks - Matt
May 4, 2004 at 2:24 pm
A full database backup doesn't truncate the inactive portion of the log. That occurs after the log backup. That's why the log is still contains the entries for the reindex after the database backup.
Greg
Greg
May 4, 2004 at 3:52 pm
Can I shrink the log as part of the full back up job safely? Or would doing that wipe out transactions that I would need to recover the db?
May 5, 2004 at 6:33 am
Hi,
you might do a "backup log with truncate", then a "backup database",
and until the next DB-Backup do a "backup log with no_truncate" every 15 minutes or so.
Best regards
karl
May 6, 2004 at 3:00 am
The right way to perform backups is to backup the database followed immediately by a backup of the transaction log. This way, you maintain the logs at a reasonable size (unless someone does a million-row delete - it happens!), and you can perform an point-in-time recovery.
The best way to prevent runaway log growth is to limit its size. That way, you can also prevent someone from performing that proverbial million-row delete. However, this has its pitfalls as well, and you may have to schedule regular transaction-log backups during the day...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply