All these DB have to be secure and also you have to keep backups.
Operations Manager Database :
Main database use by SCOM used to store all configuration for all your management groups. All changes in SCOM (Management group changes, add/modification/remove of Management Packs) are reflected in this DB.
If it's corrupted or lost and you don't have any backup, you'll have to rebuilt all your Mangement Groups.
Reporting Databases :
Reporting Datawarehouse is used to store collected data for a longer periode that the OpsMgr DB to be able to retrieve old data in the different report we can use.
If it's corrupted or lost and you don't have any backup, you will lost all the old data used for reporting purpose.
Audit Collection Database :
Mainly used for security auditing and governmental compliance reporting, a lost of data will result in sanctions against the compagny. It's a real priority to make sure backups are well working on this DB.
RMS Server encryption key :
Data in the OpsMgr DB are encrypted with the RMS encryption Key. Having issues with the key will result in the lost of all the configuration information of the management groups .
An other point is that the key is asked to promote a MS as RMS in case of crash of the RMS.
IIS Configuration and metabase :
If metabase is corrupted, Configuration will be lost. Rebuilt or reconfiguration will be easier with backups.
Management packs :
I would say, it's better to keep the MP sources you have imported (Provided, customs, and override MPs) in a kind of library outside SCOM. If you have to reinstall a management group for example with the same version of each MPs that are not up-to-date, it will be easier to reimport from you library.
Hope I don't forgot anything.. will update the post in this case... let me know if you detect that I missed something !
This posting is provided "AS IS" with no warranties.
No comments:
Post a Comment