Just wondering what some of the backup strategies are out there. Full
backups, log backups, filegroup backups? What are the sizes of your
databases?
Thanks just looking for some insight on what other people are doing with
large data warehouse databases.
--
Have a good day,
JimFYI
we use different strategies depending on the function of the database, eg
for our datawarehouse (approx 120 GB) I use the simple model, with online
backup of the db every night (takes 1,5 hours), before the nightjobs run. We
can always re-run the nightjobs from a give point in time so this scheme
will do.
For high availability production databases, I do log backups every 60
minutes, and a night backup of the db's. That way, the loss of data should
be maximum 60 minutes should we need to restore the database after a fatal
crash. Alse, the frequent backup of the logs keeps their size relatively
small (up to about 5 GB), backup of logs is first to disk for speed, then to
tape for safety.
Hope this is of some use to you...
"JimW" <JimW@.discussions.microsoft.com> schreef in bericht
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||might be worth looking at SQLLitespeed if you have large backups
http://www.imceda.com/
Andy
"JimW" <JimW@.discussions.microsoft.com> wrote in message
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||Just wondering, why backup the datawarehouse? Normally the data come from
other sources anyway, so it should be suficient to backup the production
db's. Now, what I do is I transfer, without data all the object to a backup
database and backup this every night so that I maintain the structure only.
That saves about 50% of the space.
T
"admin" <admin@.wol.be> escreveu na mensagem
news:412f713f$0$321$ba620e4c@.news.skynet.be...
> FYI
> we use different strategies depending on the function of the database, eg
> for our datawarehouse (approx 120 GB) I use the simple model, with online
> backup of the db every night (takes 1,5 hours), before the nightjobs run.
We
> can always re-run the nightjobs from a give point in time so this scheme
> will do.
> For high availability production databases, I do log backups every 60
> minutes, and a night backup of the db's. That way, the loss of data should
> be maximum 60 minutes should we need to restore the database after a fatal
> crash. Alse, the frequent backup of the logs keeps their size relatively
> small (up to about 5 GB), backup of logs is first to disk for speed, then
to
> tape for safety.
> Hope this is of some use to you...
>
> "JimW" <JimW@.discussions.microsoft.com> schreef in bericht
> news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment