TLog Backup Confusion
-
Hi Guys,
New to the Forum, been very helpful so far.
One question I have though.
I've recently setup a new Database Maintenance plan to do a full backup every hour and a TLog backup every 10mins.
The first run did the full backup okay, then the TLog backup completed at ~300Mb.
Everytime after this the TLog backups are either 46kb or 111kb, never back to ~300Mb. I don't quite understand why this is so. Should I be concerned?
-
Is there reindexing job in your maintenance plan? Mmaintenance plans reindex with DBCC DBREINDEX. And Microsoft recomend to use DBCC INDEXDEFRAG insted of DBCC DBREINDEX if you log grows. Here is an article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;873235
-
The maintenance plan only covers backups. I haven't turned any optimizations on just yet. :/
Also check the TLog script to make sure and appears to be just doing the backup...
Any idea? Is it a bad thing?
-
As I understand, your first TLOG backup was 300Mb? Then, it could be something NOT to worry about. The database is used before the first backup, then the first TLOG backup can be big.
It never repeated that big?
-
At the most 110Kb.
My concern is am I loosing something? Do i need to keep this large backup?
I'm guessing not as it's no doubt a flush out etc etc, but still makes me a little uneasy.
It was the first TLog backup ever done on the server (as far as I know).
-
You do not need to keep it.
Just try out the next Full dump to restore it to a different databasename and see for yourself that all the needed data is in there. It never hurts to test a recovery
-
Cheers mate. A backup isn't a backup until you test it.
Just didn't quite understand it.
But a backlog makes sense. They all sit there with the 'archive flag' and never got backed up.
Thanks again.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply