DPM 2012 R2 Online Protection - Online Recovery Point Creation Failed

Hi
We are moving from protecting our DPM server with another server to use an Azure Data Vault. 2 of the Protection Groups work fine, but the third - protecting a pair of Folders - fails. On the DPM MMC it shows Online recovery point creation
failed, and in the Event Log it shows -
Creation of online recovery points for D:\ on blah.blah.co.uk have failed. The last online recovery point creation failed for the following reason: (ID: 3188)
The operation attempted cannot be performed at this time because a backup or restore operation is currently running. (ID: 100049)
The DPM server is the only one conducting any backups. The target server is Win 2003 (for the moment).
Could anyone give me any pointers?
Thanks

Ok, nobody any more ideas?
The latest test involved 9.75GB on the protected server. I created the protection group and this was the outcome:
Replica volume: 15.98 GB allocated, 0 KB used | Recovery point volume: 3.70 GB allocated, 0 KB used
I then create a recovery point and then deleted all 9.75GB on the protected server. And did a full restore from DPM. It then gave following outcome:
Replica volume: 15.98 GB allocated, 9.85 GB used | Recovery point volume: 3.70 GB allocated, 654.86 MB used
Then after the creation of the first recovery point (sync + recovery point), I get this:
Replica volume: 15.98 GB allocated, 4.79 GB used | Recovery point volume: 13.70 GB allocated, 3.27 GB used
As you can see DPM took the 9.75GB and added it to the recovery volume. And strangly it took away half of the replica volume.
In addition I get 3 entried in my logs:
1) The used disk space on the computer running DPM for the recovery point volume of E:\ has exceeded the threshold value of 90% (DPM accounts 600 MB for internal usage in addition to free space available). If you do not allocate more disk space,
synchronization jobs may fail due to insufficient disk space. (ID: 3169)
2) Synchronization jobs for E:\ on ****** have failed. (ID: 3115)DPM has run out of free space on the recovery point volume and will fail synchronization for E:\ on ***** in order to prevent existing recovery points from being
deleted. (ID: 30195)
3) Creation of recovery points for E:\ on ****** have failed. The last recovery point creation failed for the following reason: (ID: 3114)DPM does not have sufficient storage space available on the recovery point volume to create
new recovery points. (ID: 214)
I hope someone can help me with this.
regards,
Maurice

Similar Messages

Recovery Point creation fails because change traking has been marked inconsistent

I have a Hyper-v Cluster that is backed up using DPM 2012 SP1, for the last week when recovery point creation attempts to run I receive the following error message.
Change Tracking has been marked inconsistent due to one of the following reasons
1. Unexpected shutdown of the protected server
2. Unforeseen issue in DPM Bitmap failover during cluster failover of one or more datasources sharing the tracked volume. (ID 30501 Details: The parameter is incorrect (0x80070057))
After this error it performs a consistency check, it completes and a backup is stored, but as soon as it does another recovery point creation it fails again with the same error.
I have a Server 2012 R2 Hyper-v cluster with 2 virtual hosts and a quorum disk acting as the deciding vote. The backups completed for a month prior to this with no problems. No event seems to have triggered this problem it is just completely out of the blue.
I have update roll-up 8 on DPM and have both hosts within the cluster updated. They seem to consistently fail on one virtual host and intermittently fail on the other virtual host.
The event logs do not have any errors other than Event ID 1 VDS basic provider

Hi,
Lets see if cleaning up all the filter bitmaps clears up the problem.
To get to a clean state please delete DpmFilter* files from “System Volume Information” using following steps.
1. Open an administrative command prompt and run:
       C:\>fltmc unload DpmFilter (run on all cluster nodes)
2) From one of the Cluster nodes, run:
       C:\>psexec -s cmd (psexec is
www.sysinternals.com tool used to run cmd under system account)
3) In this new command prompt (running as system) run:
       C:\>CD C:\ClusterStorage
       C:\ClusterStorage>For /d %i in (volume*) do del /s "%i\System Volume Information\DpmFilter*"
Note: The * includes (DPMFilterBitmap{Guid}, DPMFilterStatus, DPMFilterLog, DPMFilterTrace*)
4) verify files are deleted by running
        “dir /s /b DpmFilter*”
        exit
5) Then load the filter again on all nodes
       C:\>fltmc load DpmFilter (on all cluster nodes)
6) Run DPM Consistency check against all the VM's to re-start normal protection.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Recovery point creation failing

Hoping for some ideas,
I have a secondary backup for offsite purposes that I recently realized started failing at creating recovery points. The synchronizations complete fine but then instantly fails the recovery point with the error "No recovery point was created, either
because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID 208)". Synchronization has occurred and there are always changes as this is a file server. I ran a consistency
check which also completed without error. Seems to be some sort of database issue to me. I've been searching for answers but not having any luck.
Thanks!

So I have been fooled once again. Since my OP, I have realized even though the CC and sync jobs say completed with a green check icon, they actually failed with the same error:
Type: Synchronization
Status: Completed
Description: The job completed successfully with the following warning:
The synchronization job failed due to an internal error. (ID 117)
Kind of misleading, "It successfully completed failing"
The only tip I found was to create a current recovery point on the primary right before running a CC on the secondary but it still failed with the same error. I'm hoping to get this sorted out before I just decide to start it from scratch as it's about 7TB
of data and the best option for that is to bring the secondary onsite here to make the initial transfer.
Any ideas appreciated.

DPM (2012R2 ur 4) Azure Online recovery point creation fails

HI,
I am using SCDPM 2012 R2 UR4 to backup some files on premise. I created a backup vault - installed the Azure Agent on DPM (registered it), I downloaded the Azure Backup Vault credential file and provided it during registration process (it showed the correct
subscription and region) and configured online backup.
The backup to azure fails with Windows Azure Backup Agent cannot connect to the OBEngine service.
I already re-started the service - no problem. No firewall locally - not sure what ports are required on outgoing company firewalls (didn't see anything in the documentation). I also created a new backup vault in azure and did the same procedure again. But
the result is the same. Please does someone have any other ideas?

Hi,
Are there any events in the application event log after the failure ?
Can you look in the CBEngineCurr.errlog in the C:\Program Files\Microsoft Azure Recovery Services Agent\Temp directory after the failure and see if you can find an error that will point you in the right direction.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 unable to connect to Database after failed Update Rollup 4 Installation

We have a DPM 2012 R2 Server with SQL Server 2012 installed locally.
We tried to install Rollup 4 for DPM 2012 R2 (KB3009516) using Windows Update
and it failed with error code 0x80070643. Now when we open the DPM Console
it is totally empty (no Protection Groups, Servers, Disks, just like a fresh install).
In the eventlog we get a lot of Errors and warnings:
Event 941 (MSDPM)
Unable to connect to the DPM database. Make sure that SQL Server is running and that it is configured correctly.
Cannot open database "DPMDB" requested by the login. The login failed.
Event 4209 (MSDPM)
The description for Event ID 4209 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM Writer encountered an internal error. Please restart the DPM Writer service, and then try the backup operation again. For additional troubleshooting information, review the application event log and the DPM Troubleshooting Guide.
Event 107 (Report Server Windows Service (MSSQLSERVER)
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event 274 (SQLISService110)
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
Attempting to load default config file.
Then there are some Errors/warnings from SQLSERVERAGENT about failed scheduled Jobs.
I think the failed Installation changed some database Settings, so that now the DPM Console
cant access the database anymore.
I would be happy if someone can help me getting this Server working again!

Our biggest problem is, that the DPM is not working any more. So there is no chance to backup the SQL Server via DPM.
I think the main problem is that DPM have no access to the database. Every time I start the DPM Application, I get an error "verify that the DPM service is running on this computer". In the eventlog are many errors that the msdpm service was unable
to connect to DPM Database. Another "information" is that the user 'nt authority\system' failed to open the database of dpm.
We've tried to reinstall the DPM but its still the same problem. I suppose that is a corrupt database.
Tomorrow I try to restore the database and hope it will be the solution of our problem.

DPM 2012 R2 Repoting Protection Status as OK but no replica exists for the volume

2012R2 server running 2012R2 DPM. I am using LeftHand SAN as my DPM disks for storing backups. Our production SAN is an EMC VNX5300. I have created a mount point of a LUN and attached it to the DPM server. I have attached a snapshot to the mount point. When
I brought the volume online in Disk Management, it assigned it a drive letter. I removed the drive letter and connected it to a mount point in an empty folder in C:\ActiveVolumes. I am able to browse the folder and look at data in the folder without issue
(except having to elevate for some of the folders when browsing through GUI). In DPM, I created a new protection group. I added the mount point path (C:\ActiveVolumes\MyMountPoint) as a member of the PG. I walked through the wizard and configured my short
term and long term protection options as I have done for other jobs. I had it create the group. At the end of the process, it reported success. Based on having done this with other mount points in similar ways, I was expecting the volume to spend some hours
creating its replica as it is multiple hundreds of gig in size. After less than 15 minutes, it was sitting there with a Green OK display for Protection Status. That seemed entirely to quick so I started to investigate. When I tried to create do anything, it
failed. I looked in Monitoring/Failed jobs for yesterday and today. There was a failed job for the PG that said as follows:
Type: Replica creation
Status: Failed
Description: The Operation failed since DPM was unable to access the file/folder
\\?\Volume{GUID}\Company\Logs\Cleanup\filename.txt on dpm01.domain.pri. This could be due to the file/folder being corrupt or the file system on the volume being corrupt. (ID 2036 Details:
The file or directory is corrupted and unreadable (0x80070570))
There is a second error stating that No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID 208)
When I check the file in question on the original source, it is fine. When I connect to the mount point on the dpm server, browsing to the location, I find that the file says it is indeed corrupt. I will open a call with EMC as well, but it is a little concerning
that a single file can prevent a whole replica from being created. I also tried deleting the corrupt file and tried to synchronize again and it failed on another file in the same folder.
Some additional stuff I noticed as different:
In PG setup wizard, when expanding the DPM server under available members, after a few minutes, I get the following error:
"DPM is unable to enumerate contents in <longalphanumericstring> on the protected computer dpm01.domain.pri. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs Quorum Disk (for cluster) and other removable media cannot
be protected. (ID:38)"
Followed by the following:
"The database of this DPM server is located on a remote instance of SQL server.
To protect the database of this DPM server, you must install a protection agent on the computer running the remote instance of SQL server. After the protection agent is installed, open this wizard, navigate tot eh remote instance of SQL server, and select
the DPM database for protection.
Production server name: dpm01.domain.pri
DPM SQL DB name: MSSQLSERVER
DPM Protection agent: Not Installed"
The above is inaccurate because I am running the SQL on the same machine as my DPM server in the default SQL instance name. I have gotten both of the above errors before when trying to backup other mount points but I was able to back up those mount points
without issue.
I also noticed a difference since I created my first mount point backup. I created two folders on the root of the C: drive. ActiveVolumes and StaticVolumes. I had attached mount points under StaticVolumes previously (c:\staticvolumes\imagefolder1, etc.)
and was able to back those up without issue. When I was configuring that one, it allowed me to select to backup StaticVolumes and then it gave me a warning about mount points and did I want to back those up to. To which I replied yes, back them up. When I
was configuring this one, backing up ActiveVolumes was not an option, only the mount point below it. And it never gave me the warning about mount points. I don't know if this has anything to do with this problem.
Any assistance you can provide on figuring out why this isn't working would be much appreciated. I tried deleting the PG and starting over and got the same results. I am at a loss for how to back this up right now.

Hi,
Not sure what you want help with. Did you fix the underlying volume corruption issue ? For future posts, please limit the scope to a single well defined problem so the community can assist you best.
Please re-define a single problem statement if you still want assistance, other wise mark the post as resolved.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

DPM 2012 R2 long backup to tape job randomly fail after installing SCCM 2012 Client

Hello,
I'm managing a two nodes 2012 R2 file server cluster that contains a 16To CSV. I'm using DPM 2012 R2 to backup this entire shared volume directly to LTO 4 tapes, the job last about 55h.
Since SCCM 2012 client has been installed(I don't manage it), the tape jobs are failing ramdomly after several hours with the error:
Type: Tape backup
Status: Failed
Description: The DPM service was unable to communicate with the protection agent on serverX.xxxx.xxx . (ID 52 Details: The semaphore timeout period has expired (0x80070079))
More information
End time: 19/07/2014 03:11:06
Start time: 18/07/2014 22:00:00
Time elapsed: 05:11:05
Data transferred: 768 289,56 MB
Cluster node serverX.xxxx.xxx
Source details: G:\
Protection group members: 1
Details
Protection group: File Server Tape Protection
Library: Quantum PX500 Series Medium Changer
Tape Label (Barcode): File Server Tape Protection-00000230 (000043L4)
If I uninstall SCCM 2012 client, no more issue, backups succeed. I've asked our SCCM team, no specific task has been scheduled or deployed in SCCM.
I can't see anything abnormal in logs.
Any idea?

I have disabled "Configuration Manager Maintenance" and I have also tried to set the registry value HKLM\Software\Microsoft\CCM\CcmEval\NotifyOnly to TRUE and still the same issue.
I can't find any correlated errors in the Windows event logs, task scheduler history neither in the DPM logs.
I've increased the log level of DPM by following the following procedure
http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/how-to-collect-dpm-verbose-logs.aspx
Now i'm suspecting the maintenance job of Windows 2012 R2, i'll try to disabled this task. But the fact is that I don't have this backup issue if SCCM 2012 client is not installed.
I'm waiting for next logs and will keep you informed

Distribution Point creation failed. possible cause : distribution manager does not have the sufficient access right to the computer

Hi All,
I had this really disturbing experience with
SCCM 2012 SP1.
OD : 2008r2 Enterprise 64bit
Possible cause: Distribution Manager does not have sufficient rights to the computer.
Solution: Verify that the site server computer account is administrator of the computer.
in Distmgr.log says :
DPConnection::Disconnect: Revert to self
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.xxx\, logged-on as ssm\sccmadmin
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.x\, logged-on as ssm\sccmadmin
SMS_DISTRIBUxxx ON_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
Failed to find a valid drive on the distribution point ["Display=\\PNGBRANCHSERVER.xxx"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.myx
DPConnection::Disconnect: Revert to selfxxx
MS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
GetContentLibLocation() failed SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to get the content library path on server PNGBRANCHSERVER. SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to install DP files on the remote DP. Error code = 16389
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
STATMSG: ID=2370 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMSVR. SITE=SSM PID=2660 TID=16280 GMTDATE=Sun May 25 23:34:30.428 2014 ISTR0="["Display=\\PNGBRANCHSERVER.ssm.com.my\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.\"
ISTR1="PNGBRANCHSERVER.S" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\PNGBRANCHSERVER.\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.my\"
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
I have tried many of the solution provided unfortunately nothing positive happened.
Appreciate your input before engaging premier support.
Thank you

Hi，
NO_SMS_ON_DRIVE.SMS
This file is used to prevent Configuration Manager from installing binaries to a volume. By default, when you install System Center 2012 Configuration Manager on a remote Site System, the SMS Site Component Manager Service installs the binaries (files and
folders) for the Site System on the NTFS-formatted volume that contains the most free space. You may want to use an NTFS volume other than the default volume for your remote Site Systems by preventing ConfigMgr from enumerating certain NTFS volumes.
In order to prevent CM from enumerating an NTFS volume, on the remote server you can create a text file that is named NO_SMS_ON_DRIVE.SMS and put the this file on the root folder of all NTFS volumes where you do not want to install the binaries (SMS folder)
for the ConfigMgr components.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lenovo T61p - Product recovery disc creation fails

Hi,
I tried creating a set of product recovery disc, the process started decently to extract the information/files. Then the process abruptly stops and gives a msg saying "The process has encountered an internal error."
Pls Help.
Rgds,
Sumit

As lead_org says, call Lenovo and explain the problem you have encountered, especially the error message, "The process has encountered an internal error." If they don't offer to send you free recovery media, politely explain to them that it's not your fault that you can't make the media on your own. If you're firm and persistent (call back later and try another agent) they will relent
Cheers... Dorian Hausman
X1C2, TPT2, T430s, SL500, X61s, T60p, A21p, 770, 760ED... 5160, 5150... S360/30

DPMRA crashing after update to DPM 2012 R2 UR2

Hi,
we have a problem on our DPM2012 R2 server.
The DPM servers OS is Windows Server 2012.
After applying Update Rollup 2, the DPMRA service on the DPM server started crashing when trying to create a new recovery point or trying to synchronize:
Faulting application name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Faulting module name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Exception code: 0xc0000005
Fault offset: 0x000000000023442c
Faulting process id: 0x630
Faulting application start time: 0x01cf606a8d5b3262
Faulting application path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Faulting module path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Report Id: ed0d579b-cc5d-11e3-9436-00155d0f6501
Faulting package full name:
Faulting package-relative application ID:
When DPMRA crashes, the DPM jobs fail:
The replica of CDC-RND-SQL01\Tfs_RnD_Configuration on CDC-RND-SQL01.dev.local is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
DPM failed to communicate with the protection agent on WP-DPM02.alpha.local because the agent is not responding. (ID: 43)
Creation of recovery points for WPCLUSTERSQL\WSS_Content_WP-SP-INTRA_TEMP on SQL Server (MSSQLSERVER).WPSQLCluster.alpha.local have failed. The last recovery point creation failed for the following reason: (ID: 3114)
DPM failed to communicate with the protection agent on WP-DPM02.alpha.local because the agent is not responding. (ID: 43)
Creation of recovery points for WPCLUSTERSQL\CDC-INTRA-SPS01_WSS_Content_80_Changes01 on SQL Server (MSSQLSERVER).WPSQLCluster.alpha.local have failed. The last recovery point creation failed for the following reason: (ID: 3114)
The protection agent on WP-DPM02.alpha.local was temporarily unable to respond because it was in an unexpected state. (ID: 60)
Already tried disabling UAC, firewall is disabled, checked network connectivity, reinstalled agents on the protected servers.
Does anyone have encountered this? How did you solve it?
Here are a few DPMRA logs:
DPMRA_log_01.log
DPMRA_log_02.log

Hi,
For those experiencing the below DPMRA crash after installing DPM 2012 Sp1 UR6 or DPM 2012 R2 UR2
DPMRA.exe, version: 4.1.3441.0 = DPM 2012 Sp1 UR6
DPMRA.exe, version: 4.2.1226.0 = DPM 2012 R2 UR2
Faulting application name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Faulting module name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Exception code: 0xc0000005
Fault offset: 0x000000000023442c
Faulting process id: 0x630
Faulting application start time: 0x01cf606a8d5b3262
Faulting application path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Faulting module path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Report Id: ed0d579b-cc5d-11e3-9436-00155d0f6501
Faulting package full name:
Faulting package-relative application ID:
You can run the below Windows Powershell script on the DPM Server to clean up the *DPMRA.CRASHDETECT files. This should eliminate the dpmra crashes until a new fix is released to address the original problem.
1) Stop MSDPM and DPMRA Services.
2) Copy / Paste the below script into notepad and save as deletecrashfiles.ps1
3) Open Windows PowerShell using administrative privilege.
4) Run the deletecrashfiles.ps1
5) Restart the DPM services.
#get DPM install path
$dpmsetup = "HKLM:\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup"
$dpminstallregkey = get-itemproperty $dpmsetup
$installpath = $dpminstallregkey.installpath
$path = $installpath + "\Volumes\Replica"
cd $path
function GetFolders($path)
$folders = Get-ChildItem "."
foreach ($folder in $folders)
if (Test-path $folder.Name -pathtype Container)
#write-host $folder.name
GetCrashitems(".\"+$folder.Name)
else
#write-host $folder.Name
function GetCrashItems($path)
$crashfile = "dpmra.crashdetect"
$folders = Get-ChildItem $path
foreach ($folder in $folders)
#write-host $folder
if (Test-path $folder.fullname -pathtype Container)
write-host 'getting items from ' +($folder.fullname)
$items = Get-ChildItem $folder.fullname
foreach($item in $items)
if ($item.name -match $crashfile)
write-host 'Deleting *dpmra.crashdetect file: '$item.fullname
$item.delete()
GetFolders $path
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

DPM couldn't find valid recovery points for VM listed as having numerous recovery points when writing to tape

I'm seeing the following events when DPM tries writing to tape:
Log Name:      DPM Alerts
Source:        DPM-EM
Date:          15/02/2014 12:01:07
Event ID:      3311
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <backup server FQDN>
Description:
The back up to tape job failed for the following reason: (ID: 3311)
Backup of Non VSS Datasource Writer on <PROD server FQDN> cannot be completed. DPM could not find a valid recovery point on disk. (ID: 30126)
All VMs on each of the affected servers have recovery points but
When performing disk to disk to tape backups (d2D2T), tape backups will fail if a new disk based backup is not created before the next scheduled tape backup. DPM always makes tape backups by mounting last successful disk based recovery point.
This is so we don't need to transfer data over the network since that most recent data is already on the DPM server. Look to see why the disk recovery points are failing and correct that to prevent tape backups from failing.
http://social.technet.microsoft.com/Forums/en-US/a9b80780-2a5c-43bc-8111-ee35db56f359/backup-tapes-dpm-2012?forum=dpmtapebackuprecovery
Is this the only time that recovery points are verified? Can I do a manual verification of recovery points? I'm concerned that some of the backups I have may be corrupt. If that's the case I need a way of finding out which ones are affected and a way to
resolve the issue. Unfortunately I've not found much,the DPM error code isn't even listed in the official documentation. http://technet.microsoft.com/en-us/library/hh859159.aspx Other threads where people have seen this issue seem to be for older versions
of DPM (I'm using the latest 2012 R2 fully updated).

Hi,
I've been having some difficulty running the Powershell command, see below. I've been using this for guidance http://technet.microsoft.com/en-us/library/hh881586%28v=sc.20%29.aspx where am I going wrong here?
$Pg = Get-DPMProtectionGroup
-DPMServerName <dpm server name here>
$Ds = Get-DPMDatasource
-ProtectionGroup $Pg[1]
New-DPMRecoveryPoint
-Datasource $Ds
-Disk -DiskRecoveryPointOption -WithDataIntegrityCheck
PS C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin> New-DPMRecovery
Point -Datasource $Ds -Disk -DiskRecoveryPointOption -WithDataIntegrityCheck
New-DPMRecoveryPoint : Missing an argument for parameter
'DiskRecoveryPointOption'. Specify a parameter of type 'Microsoft.Internal.Ente
rpriseStorage.Dls.EngineUICommon.EngineConstants.DbEnums+CreateDiskRecoveryPoin
tOption' and try again.
At line:1 char:44
+ New-DPMRecoveryPoint -Datasource $Ds -Disk -DiskRecoveryPointOption
-WithDataInt ...
+
~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo
: InvalidArgument: (:) [New-DPMRecoveryPoint], Par
   ameterBindingException
    + FullyQualifiedErrorId : MissingArgument,Microsoft.Internal.EnterpriseSto
   rage.Dls.UI.Cmdlet.ProtectionCmdLets.CreateRecoveryPoint
PS C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin>

Identify which disk recovery points are stored on?

We have 3 disks in DPM, one of which is flaky and keeps going missing from DPM. We started by migrating our most important datasources to another disk (on a temporary basis) while we ordered a new SAN with the view to moving everything onto the new
SAN. This has worked for most datasources but I have a problem with one.
For the purpose of this thread we have:
Disk 1 - old, flacky disk
Disk 2 - temporary disk
Disk 3 - new SAN
I am trying to move a datasource from disk 2 to disk 3 but am getting the following error:
Set-ProtectionGroup : D:\ has recently been migrated. You cannot migrate D:\ again until the recovery points on the previous replica volume are available.
(ID: 31224)
At C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\MigrateDatasourceDataFromDPM.ps1:129 char:4
+ Set-ProtectionGroup $mpg
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-DPMProtectionGroup], DlsException
+ FullyQualifiedErrorId : ChainedMigrationError,Microsoft.Internal.EnterpriseStorage.Dls.UI.Cmdlet.ProtectionCmdLets.CommitProtectionGroup
Prior to attempting this, I removed (using remove-recoverypoint) the old recovery points I believed to be on Disk 1 rather than waiting for them to expire on their own. This worked for other datasources but doesn't work for this.
I found an SQL query on another fourm post and ran it:
use DPMDB
select dsk.NTDiskNumber,vol.MountPointPath,ag.NetbiosName, ds.DataSourceName, vol.Usage as "1=REPLvol 2=RPvol", vol.VolumeSize,lr.lastbackuptime
from tbl_IM_DataSource as ds
join tbl_PRM_LogicalReplica as lr
on ds.DataSourceId=lr.DataSourceId
join tbl_AM_Server as ag
on ds.ServerId=ag.ServerId
join tbl_SPM_Volume as vol
on lr.PhysicalReplicaId=vol.VolumeSetID
and vol.Usage in (1,2)
join tbl_SPM_Extent as ext
on vol.guidname=ext.guidname
join tbl_SPM_Disk as dsk
on ext.diskid=dsk.diskid
where ntdisknumber=4 and lastbackuptime < getdate()-7 and NetbiosName='FILESERVER1'
order by lastbackuptime
and the output is:
NTDiskNumber MountPointPath
NetbiosName DataSourceName
1=REPLvol 2=RPvol VolumeSize
lastbackuptime
4 File System\vol_783bc0f9-8382-4df5-8f72-819ba012f68f
FILESERVER1 D:\
2 359766425600
2014-05-13 08:01:08.000
4 File System\vol_783bc0f9-8382-4df5-8f72-819ba012f68f
FILESERVER1 D:\
1 2238049157120
2014-05-13 08:01:08.000
Is that DPM telling me there are still recovery points on that disk? If not, is there a way to tell which recovery points pertaining to this datasource are still on Disk 1?

That message sounds like it expects data to be on the old disk but it may be having issues. These are all dynamic volumes so taking the disk offline and then back online usually fixes dynamic disk errors. Then do a rescan in DPM.
I usually find the volume on the disk by using disk manager.
Go to the protected item (e.g. VM, volume, etc.) in the Protection view
In the bottom pane, choose the Click to view details link to get the path
Right-click on the path and copy it.
Paste the path into Notepad or similar so you can see it
In the path, there will be a GUID prefixed by "vol_"
Open Disk Manager (diskmgmt.msc)
Look for the volume that has DPM-vol_GUID where GUID is from step 6. Click on it and that will highlight the partition in the display at the bottom of disk manager. That is the disk that holds all the data for that protection item.
Sometimes it can be hard to tell which partition is highlighted on the disk and I'm sure there is a simpler, more elegant way.
After you find the partition, you could clone it onto a new disk.
You may have to end up just replacing the disk and recreating the replica. You can do that by following the information in this post (http://social.technet.microsoft.com/Forums/en-US/fa0402d3-67d4-4fe5-8ed1-5666fd6b0ff6/dpm-disk-failure?forum=dpmstorage).
Replace the bad drive and then run DPMSYNC -Reallocatereplica.
Not sure if this helps...
Rob

Recovery points and consistency checks are failing for one disk on file server. Access is denied (0x80070005)

Good day! I've built a new DPM 2012 R2 server and migrated or re-created jobs from my older 2012 SP1 DPM servers as trying to upgrade them was not working out. The DPM R2 server is running great besides this one issue. The problem is with a file
and print server at a remote office. Since it has around 750 GB of user data on it I chose to do manual replica creation on the data disk, (E:) but created the C:\ drive replica normally, over the WAN. The manual replica creation was successful, and the initial
consistency check and recovery point creation worked as expected, however, since then it will not create another RP or run a CC on the E:\ drive. Recovery points on the C:\ drive are being created properly. When I try to run a CC I get this error: "An
unexpected error occurred while the job was running. (ID 104 Details: Access is denied (0x80070005))" I've tried to drop protection on the two directories of the E:\ drive (retaining data) and re-create, but that didn't help. I've even done a recovery
from the initial RP to verify that it was created properly, and that worked as well.

Hi,
Access Denied error is usually caused by Antivirus software. Please disable real time scanning on the DPM Server for DPMRA process.
928840 You receive job status failure messages in Data Protection Manager
http://support.microsoft.com/default.aspx?scid=kb;EN-US;928840
For DPM 2012 the path has changed.
To resolve this problem, configure the antivirus program to exclude real-time monitoring of the Dpmra.exe program on the Data Protection Manager server. By default, the Dpmra.exe file is located in the following folder:
%ProgramFiles%\Microsoft System Center 2012\DPM\DPM\Bin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 fails to back up one of two disks on file server

Good day! I've built a new DPM 2012 R2 server and migrated or re-created jobs from my older 2012 SP1
DPM servers as trying to upgrade them was not working out. The DPM R2 server is running great besides this one issue. The problem is with a file and print server at a remote office. Since it has around 750 GB of user data on it I chose to do manual replica
creation on the data disk, (E:) but created the C:\ drive replica normally, over the WAN. The manual replica creation was successful, and the initial consistency check and recovery point creation worked as expected, however, since then it will not create another
RP or run a CC on the E:\ drive. Recovery points on the C:\ drive are being created properly. When I try to run a CC I get this error: "An unexpected error occurred while the job was running. (ID 104 Details: Access is denied (0x80070005))" I've
tried to drop protection on the two directories of the E:\ drive (retaining data) and re-create, but that didn't help. I've even done a recovery from the initial RP to verify that it was created properly, and that worked as well.

Open command prompt on target file and print server, change directory to
C:\Program Files\Microsoft Data Protection Manager\DPM\Temp> and run below command
C:\Program Files\Microsoft Data Protection Manager\DPM\Temp>find /i "[0x80070005]"
DPMRACur*.errlog >C:\Errors.txt
Paste the output here from C:\Errors.txt

DPM 2012 R2 Online Protection - Online Recovery Point Creation Failed

Similar Messages

Maybe you are looking for