Does CMDB need SQL Full Restore?
Updated: 29 Nov 2010 | 8 comments
This issue has been solved. See solution.
Hi
I did run out of space on my SQL Server. I found out that the CMDB.LDF is grown above 7 GB. The Only Database with Recovery Model set to "Full" is the Altiris CMDB. Is this necessary or is it still working wiht Bulk or even better Basic Recovery Model?
mRiz
Discussion Filed Under:
Comments
Hi mRizz. I have checked the
Hi mRizz.
I have checked the properties for the Altiris database for CMS 7.0.MR1 and for CMS 7,1 installations - on both my servers the settings for the DB log file are: "By 500 MB, restricted growth to 2097152 MB". Are you using the 6.x version? Seems like in 7.x the log file should not be more than 2 GB in any circumstances.
Thank you,
Alex.
Hi We are using 7.0
Hi
We are using 7.0
Did you check on the SQL or the Altiris Server?
In my config the Altiris
In my config the Altiris server and the SQL server on the same computer
Just in case: my Sym DB settings:
CMDB_IntelAMT
I looked trough the settings
In the CMDB_IntelAMT_log is a starting value of 7450 - increasing by 10% max 2 GB defined.
Obviously the 2 GB limit is not working because of the higher starting value.
I dont know what this database is holding, but we are not using AMT in our Environment.
Absolutely Not!
Hi mRizz,
You should absolutely NOT use "Full" logging settings on the NS's database; as you see it causes many problems (not the least of which being slow performance and huge transaction log file size)! There are several "best practices" documents which suggest using only Simple transaction logging, and AFAIK it is the default setting out of the box if you let the NS installation create the database. If your DBA team created the DB for you and then you pointed the install at it, then that could be the source.
As long as you have nightly DB backups (and ideally regularly scheduled optimizations/defrags/index rebuilds), you should be fine.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Recovery Model
There are few cases where you really want to use "Full". "Simple" is best for the vast majority of applications.
Unless you're doing some kind of DB replication, checkpoint recovery, or log-shipping, then Full is overkill and your transaction log can get WAY too big.
Default Install
Unfortunately we have no database team, so we have no defrags/rebuilds ect but we have a nightly Backup.
I did an automatic install with an symantec employee. All other Databases in this SQL Instance are set to basic so it has to be the Altiris installer to change the values. We have no DB replication ect.
What ist the best way to change the settings.
Set Recovery Model to Basic
SET CMDB_IntelAMT_log Starting Value to 500 MB
Restart SQL Services?
Solved
Solved with Support
http://www.symantec.com/business/support/index?page=content&id=HOWTO1752
Would you like to reply?
Login or Register to post your comment.