SQL Transaction Log Backups?

[Jeff_Jeske]

All of our SQL backups come from flat file exports to a replicated windows reparse point.
These SQL flat files are generated once a day and backed up to TSM once a day. When the backups run we also capture the transaction logs.

This scenario provides data protection for almost all situtions except something like data corruption. If the server gets corrupted odds are the replicated disk will be corrupted and so will the transaction logs. If this happens it is possible that we could lose an extended window of transaction logs.

What is the standard for backing up SQL transaction logs? Do you send them to TSM more often than once per day?

 

[bheisser]

we send our sql backups (one per day) and our transaction logs to a network share and use TSM to back them up (once a day). We have tsm reset the archive bit and only delete them (via script) if the archive bit has been reset. This enables us to always have the latest backup availble on a disk and and all transaction logs pertinent to the last backup (we just use the standard sql maintenance to do this (no tdp)

 

[Jeff_Jeske]

Thanks for the reply. Does anyone backup the transaction logs more frequently?

 

[Trident]

Hi,

We have several SQL clusters that we do logbackup on a hourly basis using TDPSQL. Works like a charm. Full backup is done once a week.

Basic SQL servers have full backup once or twice a week and logbackup twice a day.

 

[GregE]

We also do transaction log backups for seversl SQL DBs hourly, using TSM TDP.

 

[dig1tal]

Trident/GregE

Are either of you doing daily differentials in between full backups? If not, what's the restore like for a full + logs with the last full backup occuring 4 days ago?

 

[Trident]

Hi,

I have only once client that uses differential backup. Works fine.

We have run restore from full backup and then added almost 7 days of hourly logbackups. It works fine. It may take some time, if some of the logs resides on tapes and not on disk.

 

[GregE]

We're doing differentials as well on some of the DBs that we do transaction logs on. Haven't restored one yet.