my personal blog about systemcenter

Archive for April, 2014

Backup of Replica VMs is now a supported scenario.

Categories: Data Protection Manager, Hyper-V, Replica
Comments Off on Backup of Replica VMs is now a supported scenario.


  1. Backup of Replica VMs is now a supported scenario.
  2. Only crash-consistent backup of a Replica VM is guaranteed.
  3. A robust retry mechanism needs to be configured in the backup product to deal with failures. Or ensure that replication is paused when backup is scheduled.

YEAH , finally support change , we still pause replica though but YEAH !

DPM 2012 R2 RU2 – KB2958100 – DPM AccessManager Service crash

Categories: Broken, Data Protection Manager
Comments Off on DPM 2012 R2 RU2 – KB2958100 – DPM AccessManager Service crash

Heads up with DPM CU2 , if tapes have been reinventoried DPM will crash , Mike made a SQL script that does a workaround until fixed

I would hold on for now deploying CU2

2003 Support for Data Protection Manager 2012 R2

Categories: Broken, Data Protection Manager
Comments Off on 2003 Support for Data Protection Manager 2012 R2


NOTE: First Attempt Failed Testing Smiley

NOTE: READ THE DOC CAREFULLY AS I DIDNT , + adding the magic step 6.5

Update the protection agents on Windows Server 2003 servers
  1. Install the Microsoft Visual C++ 2008 Redistributable on Windows Server 2003 servers if it is not already installed.



  1. Note The following error occurs if the C++ redistributable is not installed:
  1. Data Protection Manager Setup
    Could not load the setup launch screen. Please contact Microsoft Product Support.
  1. Copy the Windows Server 2003 Agent installer that is located on in the DPM server to the Windows Server 2003 server, and then install the agent.
    • 64-bit: DPM Installation LocationDPMagentsRA4.2.1226.0amd641033DPMAgentInstaller_Win2K3_AMD64.exe
    • 32-bit: DPM Installation LocationDPMagentsRA4.2.1226.0i3861033DPMAgentInstaller_Win2K3_i386.exe
  1. Run the following command at an administrative command prompt:
cd DPM Agent Installation LocationDPMbinsetdpmserver.exe –dpmservername DPM Server Name
  1. Run the following Windows Powershell cmdlet to establish a connection with the DPM server:
Attach-ProductionServer.ps1 DPMServerNameProductionServerNameUserNamePasswordDomain
6.5 , MISSING – Install the MSP before refreshing in the console and reboot after that
  1. On the DPM server, click Refresh two times on the agent that is connected to the management user interface, and then validate that the Health Service state is initialized.

New features in this update rollup

· Support for Windows Server 2003 workloads
DPM 2012 R2 now supports backup and recovery of Windows 2003 servers. In Update Rollup 2, you can now protect Windows Server 2003 by using DPM 2012 R2. The following workloads are also supported in Windows Server 2003:

o Microsoft SQL Server 2005, Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2

o Microsoft Office Sharepoint Server 2007

  • Protection of SQL AlwaysOn with Clustering
    Protection and recovery of availability groups that are built by having or not having clustered instances is now supported and works seamlessly in the same manner that it does for non-clustered availability groups.

Collapse this tableExpand this table





Supported in UR2

Supported in UR2


Supported in UR2

Already supported




Default Install of a rollup

Agent Install CU2 Way




Restart Server



Install the DPMProtectionAgent_KB2958100.msp and reboot again


Agent Install the CU2 way


Refresh in CONSOLE TWICE before trying to protect a resouce.


And Sucess.


DONT Attach the logial way that dont work





DONT Agent Install the logical way ( and the way that dont work)




Install protection agent on failed:

Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on


Error details: %1 is not a valid Win32 application

Recommended action: Verify that the Agent Coordinator service on is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.