Wednesday, May 02, 2012 10:47 AM
We have 2 SCOM sites which are independent to one another, apart from both Management Servers write their data to the Data Warehouse at the same time it is written to the Operations Manager Database
Currently we are going through DR scenario's and i have been asked if the Data Warehouse becomes unavailable and is down for 5 days (worst case scenario), will the functioning site's Operations Manager Database write the data to the Data Warehouse it has been collecting for those 5 days once the Data Warehouse becomes available again.
I know our Operations Manager DB keep data for 7 days before it is groomed, i'm unsure whether the data would automatically be written to the Data Warehouse once it becomes available again or would i have to initiate a manual process to do this?
Wednesday, May 02, 2012 11:21 AMModerator
"will the functioning site's Operations Manager Database write the data to the Data Warehouse it has been collecting for those 5 days once the Data Warehouse becomes available again."
No - it isn't the OperationsManager database that writes to the datawarehouse - it is the Management Server. There is no Sync between these databases. There would be no manual process to run. The management server would eventually have dropped the data and it would be lost forever (it would never get to the DW database).
Wednesday, May 02, 2012 11:56 AM
Hi Graham cheers for the quick reply.
Just so i have this straight, as it is the RMS which writes the data to both the Operations DB and the Data Warehouse at the same time, there is no retrospective task/job which would could be run on the RMS in order to write the data which the Data Warehouse would have missed while it was off line?
So effectively once the 7th day is reached and the Operations DB is groomed, that data is lost forever as stated above?
Wednesday, May 02, 2012 1:11 PMModerator
Yes - that is correct. It is the Management Server (not necessarily the RMS) that writes information to the databases.
"Alert/Discovery Agents send alert and discovery data to their primary management servers which then write directly to the Operational Database and the SDK service on the root management server then pulls the data from the Operational Database and displays in your console. The sync module on the root management server then reflects the alerts and discovery data changes into the data warehouse. "
The sync that this mentions is for updating items like resolution states on alerts that are already in both databases.
If you need High Availability for the SQL then consider clustering. It depends how important that long term data is to you.
Wednesday, May 02, 2012 1:18 PM
There are synchronization rules that are defined which run on the RMS to synchronize the DW for synchronized data such as availability data, importing MPs, etc. that would be impacted while the DW is unavailable. If your DW database is unavailble past the grooming period defined for the data points in the OperationsManager DB, then yes your DW will be out of synch.
Wednesday, May 02, 2012 1:28 PMModerator
" If your DW database is unavailble past the grooming period defined for the data points in the OperationsManager DB, then yes your DW will be out of synch. "
Sadly it will actually be out of sync before the grooming period. The sync won't sync performance data that is in the SCOM DB but not in the SCOM DW. Performance data is written to both databases "in parallel" and is not synced thereafter.
- Marked As Answer by midgelfc Wednesday, May 02, 2012 1:31 PM
Wednesday, May 02, 2012 1:28 PMCheers Graham, thanks for helping make sense of this, i felt like i was going round in circles in my mind!