Showing posts with label 3days. Show all posts
Showing posts with label 3days. Show all posts

Friday, March 30, 2012

Log shipping trn file retention

What's the logshipping trn file retention most DBA usually set, 1,2 or 3
days? I am curious. In our production database, we set our LS file retention
for 3 days and I am just wonder if it 's too long or too short. Is there a
guideline or some short.
Thanks in advance
PhilN wrote:
> What's the logshipping trn file retention most DBA usually set, 1,2 or 3
> days? I am curious. In our production database, we set our LS file retention
> for 3 days and I am just wonder if it 's too long or too short. Is there a
> guideline or some short.
> Thanks in advance
>
We use a home-grown log shipping process here, and keep a solid week's
worth of backups. As each log is restored, it is zipped up into an
archive for that day. At any given point, we have 7 zip files,
containing the t-logs for the previous 7 days.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log shipping trn file retention

What's the logshipping trn file retention most DBA usually set, 1,2 or 3
days? I am curious. In our production database, we set our LS file retention
for 3 days and I am just wonder if it 's too long or too short. Is there a
guideline or some short.
Thanks in advancePhilN wrote:
> What's the logshipping trn file retention most DBA usually set, 1,2 or 3
> days? I am curious. In our production database, we set our LS file retenti
on
> for 3 days and I am just wonder if it 's too long or too short. Is there a
> guideline or some short.
> Thanks in advance
>
We use a home-grown log shipping process here, and keep a solid week's
worth of backups. As each log is restored, it is zipped up into an
archive for that day. At any given point, we have 7 zip files,
containing the t-logs for the previous 7 days.
Tracy McKibben
MCDBA
http://www.realsqlguy.com