Re: Trans Log Maintenance
- From: Ekrem Önsoy <ekrem@xxxxxxxxxxxx>
- Date: Sat, 24 Jan 2009 22:29:21 +0200
I don't think it's an efficient way.
For example, in my lastest project I talked to my customer and asked him: "How much data can you afford to lose?" and their answer was "15 min" so I planned a backup strategy as follows:
Full backup: 00:00
Differential backup: Every six hours from 06:00 to 18:30
Log backups: Ever 15 min from 00:15 to 23:50
If you skip using differential backups and it would take too long time to restore from full and transaction log backups.
Today I heard a story that Paul Randal experienced, he told it on technet radio. He said that there was a bank and they took a full backup in 2004 and since then they were taking only transaction log backups and their database corrupted so they needed to restore their database from the backups and it took their 3 days to restore from that one full backup (which was taken 3-4 years ago) and log backups, can you imagine?
Of course your story wouldn't be like that bank's however I believe you got it.
--
Ekrem Önsoy
"Socrates" <Socrates@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:EA1B9539-D531-4867-A1D4-3EB656BB8FF1@xxxxxxxxxxxxxxxx
Hi,
I'm trying to implement an efficient way to manage trans log in a prod
environment (recovery model full) with the following backup strategy:
- hourly trans log backups
- nightly full backups
Any help is greatly appreciated.
Thanks,
.
- References:
- Trans Log Maintenance
- From: Socrates
- Trans Log Maintenance
- Prev by Date: SQL Server for MOSS Farm
- Next by Date: RE: SQL Server for MOSS Farm
- Previous by thread: Re: Trans Log Maintenance
- Next by thread: RE: Trans Log Maintenance
- Index(es):
Relevant Pages
|