my personal blog about systemcenter

Archive for December, 2012

This is one of the errors that shouldn’t exist (mainly because it should have been noticed before the backup tried to complete)

 

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))

Check the Application Event Log on for the cause of the failure. Fix the cause and retry the operation.
For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.

Error Information from Data Protection Manager

 

Event 10102

Failed to create the volume shadow copy inside of virtual machine ”. (Virtual machine ID 21B191E3-516B-42F4-8BD7-601CC7C97CBC)

Looking at the Hyper-V hosting the VM I could see that Hyper-V was unable to create a snapshot of the volume

Looking in the VM there was 0 bytes free , leaving the VSS writer unable to do any work , so after expanding the drive the backup is successful

So now its time to see why the Operations Manager agent  wasn’t installed on the machine.

 

I ran into some trouble with a Hyper-V 3.0 Windows Server 2012 environment , randomly VM’s would enter paused state when Data Protection Manager 2012 performed a backup , Event ID 16060 VM has been paused because it ran out of disk space on C:\Clusterstorage , but after looking at both the CSV and the VM itself there was plenty of space.

image

 

Moving the CSV owner to a dedicated node without VM seemed to solve the problem but as soon as Dynamic Optimization kicked in the host had VM pause again when the backup ran.

After looking around I found this thread http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/7a7ddaca-fb09-4c9a-b0ae-9f3b5e10694d , showing other having the same problem.

So thank you to all thread posters especially Vladimir from Microsoft and Trevor from Outsourcery and Joe from Catapult systems pointing to KB2791729 for resolving the issue

So either move the CSV owner to a node without VM’s or contact Microsoft for a private hotfix until its available for everyone or look in the thread :) above.

 

When converting machines or deploying from the library the default setting for VMM is secure by default so BITS will use HTTPS , this will ensure that data is encrypted from source to target , depending on your data policies it might not be a option to force HTTP , but in many cases we have the VMM placed within the cluster so its unencrypted from the VMM to the Hyper-V clusters it residing on so its very hard to intercept the traffic unless you have full control over the hyper-v servers and the switch they are connected to , but always verify against security policies

This will also greatly improve Physical to Virtual Conversions especially on servers with slow processors

This is screen from Virtual Machine Manager 2012 settings

image

When creating a new machine the Deploy File takes in our demo setup 1.30ish

image

to enable http we need to select “allow unencrypted file transfers” on the host group level

image

and Allow unencrypted transfer on the library in Virtual Machine Manager

image

The same deployment now takes 37 seconds so a significant improvement in performance , and there will be a lighter load on the environment as we don’t have to encrypt all data packages before moving them from the VMM server to the Hyper-V host

 

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