March 6, 2013 at 3:13 am
We have a customer who wants to use LiteSpeed for backup process on few SQL Server 2008 EE machines. We have to deploy our product and we are considering system database sizing. What impact LiteSpeed will have on msdb (considering that it is used for backup and restore history, job definitions,...). Or more precisely what LiteSpeed store on msdb, what informations, jobs,...Thanks
March 6, 2013 at 9:48 am
From what I remember, Litespeed does not create any extra, above what a normal backup strategy would i.e. backup history, etc. That would be outside of your sizing requirement
SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
March 7, 2013 at 12:07 pm
Litespeed does not store anything additional over what is stored by native backups in msdb.
With that said, Litespeed can be configured to stored history in a repository which is either local or remote. If you configure that, then you need to be concerned with the Litespeed repository and how large that will get.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
March 7, 2013 at 3:36 pm
I don't see the value in using Litespeed for backups, since the native backup compression in 2008 EE is just as good and doen't cost anything.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply