my personal blog about systemcenter

All posts in Data Protection Manager

Backup with ODX enabled on HP 3PAR with Data Protection Manager

Categories: 3PAR, Data Protection Manager, DPM, Hyper-V, Windows Server 2012 R2
Comments Off on Backup with ODX enabled on HP 3PAR with Data Protection Manager

 

So far we had a mixed experience with ODX and HP 3PAR  , backup was painfull with locked luns , moving vm around was even more painfull with data corruption

So until now we have disabled ODX on everything 3PAR related other arrays have issue with backup , and since its software the solution so far have been a mix between HP and Microsoft

This is “only” a issue when doing backup of a CSV volume standalone host havent been affected again back to the mix between HP and Microsoft

From what we seen so far

 

 

2012 R2 with April update and http://support.microsoft.com/kb/2966407 will fix

Assume that you install update 2919355 on a Windows 8.1-based or Windows Server 2012 R2-based computer. When you try to back up some Hyper-V virtual machines that reside on cluster shared volumes, you receive an error message that indicates the backup request has failed.
Here is a sample of the error messages that you may encounter when this issue occurs:

Error(s): vss_e_unexpected_provider_error
Csv writer is in failed state with unexpected error

 

On the 3PAR side we have upgraded to 3.1.3 and will apply some more patches tomorrow and continue testing

SCOPE

Windows Server 2012 or Windows Server 2012 R2 hosts with ODX in use with HP 3PAR StoreServ Storage running HP 3PAR OS version 3.1.2 GA, 3.1.2 MU1, 3.1.2 MU2, 3.1.2 EMU2, or 3.1.2 MU3.

RESOLUTION

Upgrade the HP 3PAR OS on the HP 3PAR StoreServ Storage to 3.1.2 MU2 or later if running a lower HP 3PAR OS version. Next apply the patch as follows:

  • For 3.1.2 MU2 and 3.1.2 EMU2, apply Patch 11 followed by Patch 36.

  • For 3.1.2 MU3, apply Patch 30.

 

image

So after Windows Patches and Upgraded 3PAR we can now backup mutiple VM (was 2 before) and move data around with ODX enabled.

What remains for the next week is to move VM around with storage migration to verify that the data corruptions also is history.

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.

Takeaways

  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.

http://blogs.technet.com/b/virtualization/archive/2014/04/24/backup-of-a-replica-vm.aspx

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

http://social.technet.microsoft.com/Forums/en-US/e9f4801e-6a6f-440f-ad05-65758007db69/dpm-2012-r2-ru2-kb2958100-dpm-accessmanager-service-crash?forum=dataprotectionmanager

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

clip_image002

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.

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

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

  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
 DPMProtectionAgent_KB2958100.msp
  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

Primary/Secondary

Clustered

Standalone

Clustered

Supported in UR2

Supported in UR2

Standalone

Supported in UR2

Already supported

clip_image003

clip_image004

clip_image005

Default Install of a rollup

Agent Install CU2 Way

clip_image013

clip_image014

clip_image015

Restart Server

clip_image017

image

Install the DPMProtectionAgent_KB2958100.msp and reboot again

image

Agent Install the CU2 way

clip_image026

Refresh in CONSOLE TWICE before trying to protect a resouce.

image

And Sucess.

DONT DO THIS-

DONT Attach the logial way that dont work

clip_image019

clip_image021

clip_image023

clip_image024

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

clip_image007

clip_image009

clip_image011

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.

WINDOWS SERVER 2003 SUPPORT COMING BACK TO DPM 2012 R2

Categories: 2003, Data Protection Manager, DPM
Comments Off on WINDOWS SERVER 2003 SUPPORT COMING BACK TO DPM 2012 R2

As many pointed out 2003 Supported was removed in Data Protection Manager 2012 R2

Steve found a public annoucement that its on its way back

http://www.buchatech.com/2014/03/windows-server-2003-support-coming-back-to-dpm-2012-r2/

Hello Folks, I am the GPM for the DPM product group and sincerely apologize for this. Not supporting an already supported server OS for back-up is DPM 2012 R2 was a mistake. We are fixing this in the next update roll-up for DPM scheduled to be released shortly. Thanks for your patience.

Shreesh Dubey

This is good news as Data Protection Manager wont hold down a suite upgrade all the way around , ITS NOT A FREEE PASS to keep goofing around with 2003 servers , they are close to end of life , upgrade/migrate/power off but until you do at least we can soon again protect 2003 workloads with Data Protection Manager 2012 R2

Now go off and migrate Smiley