my personal blog about systemcenter

Archive for February, 2013

 

Microsoft have released System Center 2012 SP1 Configuration Analyzer

The tool collect configuration info from Operations Manager , Virtual Machine Manager , Service Manager , Orchestrator , Configuration Manager and Data Protection Manager

This post will only cover the scanning on a local DPM Server

 

image

Configuration Analyzer require MBCA 2.0 to be installed , this GUI states 2.1 but the link goes to 2.0 and the documentation states 2.0 also

http://technet.microsoft.com/en-us/library/jj992580.aspx

MBCA Download

http://www.microsoft.com/en-us/download/details.aspx?id=16475

image

Start the MBCA Installer

image

And select a location

image

And 2 seconds later MBCA is ready for action

 

image

Start the Installer for System Center Configuration Analyzer

image

image

Again 5 seconds later we are ready for action

image

Start Microsoft Baseline Configuration Analyzer and select the System Center 2012 SP1 Product to Analyze

image

Select target server and enter credentials

image

And we can see one of the examples on what is being tested , page files size to ensure performance for the DPM installation

image

And what is being tested , dpm database backup is always very important so its great that its being tested

 

With Hyper-V 3.0 we got the ability to replica VM from primary to secondary location so in the case of a site failure we can failover the VM and run them from the secondary location.

This still leaves a case for backup as Hyper-V Replica is a disaster recovery solution and not for long term backup as we can “only” keep 10 snapshots back in time.

From a Microsoft Support point of view there is no support for backup / recovery from a Hyper-V Replica Backup

http://blogs.technet.com/b/dpm/archive/2012/08/27/important-note-on-dpm-2012-and-the-windows-server-2012-hyper-v-replica-role.aspx

This first part will show you what is support , 2nd part will cover the steps needed in case of a failover

From a IO perspective it would be very nice to be able to backup the Hyper-V replica as this would unload the primary storage system

 

image

So in this case we replica the fileserver FS01 from the Hyper-V Cluster to the DPM server DPM01

 

imager

On the target side we have the Hyper-V Replica of the fileserver with the snapshot history so in case of a disaster we can choose what replica to start off from .

image

From a supported backup point of view we need to protect the primary replica , so in this case we backup the VM from the Hyper-V Cluster

image

Supported = Everybody is happy.

 

image

Unsupported = Don’t do it Smile

 

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

When trying to push the Data Protection Manager 2012 SP1 agent to some freshly installed Windows Server 2008 R2 SP1 Servers

 

image

Activation context generation failed for “c:\4d6282c8e2c224197fca9bafef3d\1033\SetupLaunchScreen.DLL”. Dependent Assembly Microsoft.VC90.CRT,processorArchitecture=”amd64″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”9.0.21022.8″ could not be found. Please use sxstrace.exe for detailed diagnosis.

 

image

Got a cloud not load the setup launch screen

 

image

And Agent Operation Failed ID 370

image

Going from the error in the event log the DPM Agent Installer have a requirement on VC Redist 2008

image

Installing 2008 or 2008 SP1

image

And we have success with pushing the agent to the Windows 2008 R2 Server

 

image

And always run a windows update to ensure that VC get patched

So Windows Update is your friend