my personal blog about systemcenter

All posts in Operations Manager

 

Its that time a year again a clean install of the servers in our combined playground and demo enviroment , ripped out 5 old servers and added 4 new ones saving 20kw hours a day and with our power cost its adds up to 150ish euro a month.

The enviroment currently is mixed playground and customer facing demo enviroment this is mainly due to resource constrains and with new servers version hopefully presented at build its not getting any easier to fit , so more servers are on their way

 

image

Part one is the basic hyper-v enviroment , next is vmware and xen adding up with 6 servers dedicated to hypervisors.

Part two is Data Protection Manager 2012 SP1 running in a phsycial box to protect the enviroment

There are 2 other servers reserved for Virtual Machine Manager bare metal deployment everything else will be virtual.

Part three is “just” the remaining systemcenter parts , with focus om VMM/Service Manager and Operations Manager , and the integration glue with Orchestrator , Config Manager will follow for patching and protection but since i need to do a windows-noob.com from end to end to deploy it its a nice to have at some point in time.

Part four is Direct Access , PKI , Remote Desktop Services

Part five is everything else Smiley

 

I recently ran into a problem where the Data Protection Manager replica of the Exchange 2010 Database kept failing with Replica is Inconsistent  , after a rerun with Preform Consistency Check the result was the same

 

image

Looking at the event log on the Exchange Server listed possible VSS writer error

 

Event 2112

The Microsoft Exchange Replication service VSS Writer instance b730cfbf-41a4-40bd-8b08-ac7a7bc0c333 failed with error code 80070015 when preparing for a backup of database ‘Database1’.

Event 2024

The Microsoft Exchange Replication service VSS Writer (Instance b730cfbf-41a4-40bd-8b08-ac7a7bc0c333) failed with error 80070015 when preparing for a backup.

 

But the vssadmin list writers

Writer name: ‘Microsoft Exchange Writer’
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {a1f4aad9-ecfb-434e-a765-db63590ab810}
State: [1] Stable
Last error: No error

reported no errors

 

The replica of Exchange Mailbox Database Database1  inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

 

DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,
the error may not reoccur.
(0x800423F3))

 

But looking at the Exchange databases I would see that the passive database had failed

 

image

Reseeding the database and rerunning the job fixed the issue

image

 

But then again we should always look at operations manager first Smiley

I recently ran into a problem with adding new host to a existing 2008 R2 Cluster , the cluster had the host installed storage mapped and joined to the cluster outside of VMM.

 

When trying to add the host it ended up with a Error 2927

image

 

Error (2927)
A Hardware Management error has occurred trying to contact server VMM2012 :n:CannotProcessFilter :The data source could not process the filter. The filter might be missing or it might be invalid. Change the filter and try the request again.  .
Unknown error (0x8033801a)

Recommended Action
Check that WinRM is installed and running on server VMM2012 For more information use the command “winrm helpmsg hresult”.

 

Installing the agent manually ended up with the same result

running winrm quickconfig on the VMM and Hyper-V host didn’t change anything everything else seems to be working , looking though the VMM log history I found Warning (24375)

image

And the one thing I didn’t check , Virtual Machine Manager Agent Service on the Virtual Machine Manager Server was stopped

image

After starting the service I could add the new hyper-v host to Virtual Machine Manager.

 

image

So the key here is to always look at Operations Manager before starting manual troubleshooting as it would have told us right away what was causing problems.

Operations Manager + Virtual Machine Manager = Working Better Together

 

One of the great things with Operations Manager is the wide vendor support.

IBM have created a storage manage pack for their storage products , the documentation for the newest version can be found here http://pic.dhe.ibm.com/infocenter/strhosts/ic/index.jsp?topic=%2Fcom.ibm.help.strghosts.doc%2Fscom-homepage.html , currently the version is 1.3 , IBM regularly updates the storage management pack for adding features and new storage systems

Its a pleasure that IBM provides a high quality management pack for Operations Manager (HP pay attention) other vendors could be inspired

 

Version 1.3 that came out middle of December can be download from http://www-933.ibm.com/support/fixcentral/swg/doSelectFixes?options.selectedFixes=IBM_Storage_Management_Pack_for_Microsoft_SCOM_v1.3.0&continue=1

image

the installer is available in a 32 and 64 bit version

image

Selecting Customer will allow you to only select the management packs valid for your environment

image

We only have StorWize running here so removing everything else

image

Logon to the StorWize V7000 system to create a user we can use for monitoring purpose

 

image

Go to Users  – > Monitor and create a new user

image

The management pack can use user/pass or ssh key in the newer StorWize Microcode so we will stick with user/pass

 

image

The management pack leaves a shortcut to the client configuration tools , to start the configuration you need to run as administrator otherwise the configuration will not work

image

image

image

scomu.cmd --add -t storwize --ip 10.151.0.105 --authmode password –username scom --password xxxxxxxxxx

Syntax for adding the 10.151.0.105 StorWize with username and password

image

to verify the connection run scomu –list it will generate a html file with the connected storage systems

 

image

Before importing the management pack ensure that server proxy is allowed for the computer where you installed the Storage Management Pack

 

image

image

Select the management packs and install.

image

The discovery of the StorWize system is target all windows computer and runs every 4th hour

image

We will create a override disabling it against all windows computers and the create a override enabling the discovery for the Windows Computer object that we installed the management pack on.

image

after kicking the health service we will see the discovery of our StorWize showing up as objects in Operations Manager

image

and we can now see active alerts on the storage system , so its time to configure the smtp server for alerting in the storwize

image

there are no diagram views defined but right click diagram view

image

give you a nice overview of the storwize “moving” parts.

image

Since the management pack is sealed (and i don’t want to unseal it) i create a new management pack

image

And a diagram to add our StorWize

image

And we know have a management pack with the StorWize default view in it

 

Microsoft have released updates for Operations Manager 2012 Update 3 on Windows Update

So after a new installation of Operations Manager 2012

image

The updates now appears in Windows Update

This means that agents also will be updated so ensure that you always get the servers patch before setting the updates free for the clients

 

image

and we are now hands off in the installation Smiley

Product: System Center Operations Manager 2012 Server – Update ‘System Center 2012 – Operations Manager UR3 Update Patch’ installed successfully.

Very Handy , just make sure that Operations Manager infrastructure is patches in the correct order before patching everything else