my personal blog about systemcenter

Archive for May, 2012

image

DPM cannot set up an e-mail subscription for this report. The information may be missing or incorrect.

Click Options in the Actions pane, then click the SMTP Server tab, and provide the correct SMTP server name and e-mail address.

ID: 3010

After upgrade from Data Protection Manager 2010 to 2012 I was unable to schedule a report

library!ReportServer_0-1!b4c!05/28/2012-18:44:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.DeliveryExtensionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.DeliveryExtensionNotFoundException: An attempt has been made to use a delivery extension that is not registered for this report server.;

Digging around I found the following error in the Reporting Services Log file

 

image

 

image

Connected to the reporting service instance and entered a smtp server that DPM can use

image

and was then able to schedule a report

I would recommend opening a support case to get a official supported version of the workaround but for the purpose of testing this seemed to do the trick.

 

Data Protection Manager 2012 can protect SQL server 2012 with the exception for Always On Databases this feature should be ready in the Service Pack 1 time frame for System Center 2012.

There is a current  thread on TechNet regarding SQL server 2012 supported that this post was created from

http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/03f1267a-5061-488d-b4d6-e4b3b9b66dd5

 

image

A few steps to install SQL server so we can try to backup / recover a database

image

SQL Features Install

image

We will just install database engine and management tools

image

And place our databases

image

And its time to refill the coffee.

image

Success Smile

 

image

We then need to install the Data Protection Manager agent on the SQL Server 2012

image

Add the SQL Server 2012 host , here SQL12

 

image

Add credentials that can install a agent locallly

image

And with Data Protection Manager Success is always close by Smile

 

image

image

Create a database

image

image

Add some a table where we can add some data

image

Enter a few rows

image

And its time to create the Data Protection Manager Protection Group

image

Create a protection group for servers

image

Browse to the SQL server 2012 server and add the databases with autoprotect

image

Add a name to the protection group , in the demo setup there no autoloader so backup to tape only

image

Keep 5 days and Sync every 15 minutes

image

Success

image

Change journal not initialized or is the wrong size (ID 30118 Details: The volume change journal is not active (0x8007049B))

Almost , getting Replica is Inconsistent all the time

 

image

To resolve the error give SYSTEM sysadmin rights to the SQL Server 2012 Installation

image

And we can now see that the SQL server 2012 database is protected.

image

And to provoke a error , we delete the table we created

image

Go into Data Protection Manager , Recovery select the SQL server 2012 database and what time you want to recover from , right click and recover

image

image

In this case I want to recovery and overwrite the database to the original server

image

And leave the database operational

image

Summary before recivery

image

Success for recovery of the SQL server 2012 database

image

image

And we got the database restores as it was before the table was deleted

I recently ran into a issue where I was unable to set the network on a
virtual machine.

image_thumb[9]

There was a working logical network , VM that spanned the Hyper-V cluster and
everything was working

image_thumb[11]

For the purpose of reproduction I called the “broken” logical network
Trailing Spaces

image_thumb[14]

When I try to set the logical network on the virtual machine

Warning (25133)
Selected Virtual Network Switch (Trailing Spaces) is not
available as a highly available clustered virtual network combination.

Recommended Action
Please choose different highly available virtual
network or if possible another one would be automatically chosen for you.

Warning (25134)
Selected Highly Available Virtual Machine’s logical
network (Trailing Spaces) is not available as a highly available available
clustered virtual network combination.

Recommended Action
Please choose different logical network or set the
appropriate logical networks on all nodes of the cluster.

I get the error that the network is not avaialble

a get-virtualnetwork shows that the network is on all 5 Hyper-V hosts so
after a lot of digging around I see that the

image_thumb[18]

Name on HV05 have a trailing space and after digging around on the Hyper-V
hosts

Virtual Network Manager on HV1-4

image_thumb[6]


Virtual Network Manager on HV05

image_thumb[4]

I can see that HV05 indeed have a trailing space after its display name

image_thumb[22]

So I removed the trailing space on the Virtual Network and refreshed the
cluster

image_thumb[24]

And then I was able to set the correct virtual network and everyone was
happy.

Will you ever run into this ? most likely not

All Virtual Networks was created manually , never trust something that needs
to be done 5 times in a row

Everything should be scripted Smile

— Data Protection Manager 2012 Unable to Protect Sharepoint

Categories: Uncategorized
Comments: No

I ran into a issue with Data Protection Manager where I was unable to protect a sharepoint instalation

The specified account could not be configured for Sharepoint Protection  , no matter what account I used.

728    0F88    05/02    15:53:59.414    18    fsutils.cpp(3873)            WARNING    Failed: Hr: = [0x80070002] : GetFileAttributes failed for C:Program FilesMicrosoft Data Protection ManagerDPMDatasourcesPSExchangeDatasourceConfig.xml
0728    0F88    05/02    15:53:59.414    18    fsutils.cpp(2173)            WARNING    Failed: Hr: = [0x80990a52] : Invalid filespec:DatasourcesPSExchangeDatasourceConfig.xml

Log file was hinted at permissions

image

And guess what I did wrong , noob error tried to do something important from a non elevated prompt

So always remember Run as Administrator