Sharepoint 2010 backup fails "has been stopped becuase this operation depended on another backup operation.. ID 30200"
-
Friday, July 29, 2011 6:10 PM
Just building out our SharePoint 2010 environment, have data migrated into it, and just created the DPM 2010 protection group. The first couple backups worked fine but subsequent backups are failing for a specific Content Database (Config Database for that ContentDB and other ContentDBs run fine). Don't see any errors in SharePoint or SQL or from VSSadmin and I do see the SQL database backup running successfully for the ContentDB that fails in DPM.
I've rebooted all servers involved, tried modifying the protection group, consistency checks, etc. SharePoint environment is all Windows 2008 R2 SP1 and SQL is 2008 R2.
Prepare for backup operation for SQL Server 2008 database SQLSERVER1\Content_DB on SQLSERVER1.domain.name has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)
All Replies
-
Wednesday, August 10, 2011 5:30 PM
I have the same thing, were you able to resolve it?
-
Wednesday, August 10, 2011 8:12 PMModerator
I am keying in on a specific key word you have here in the error message.
"Prepare for backup operation..."
This makes me think that the backup is failing prior to the snapshot being prepared. Now I know this sounds really simple. But here is where I would start looking to troubleshoot this issue.
Something happened prior to the sharepoint backup of the content DB that makes me think the issue is on the farm itself.
Look for VSS error in the event logs on the farm as well as the DPM Servers Jobs tab under monitoring. Review the failures prior to and just before the failure to see if it helps.
You can also review the msdpmcurr.errlog and the wsscmdletswrappercurr.errlog. They are nothing more than txt files that you can review at the time of the backup. Keep in mind that DPM will display the time in your timezone and the .errlog will be in UTC/GMT.
Both files can be found on their respective servers in the temp folders of either the Microsoft DPM\DPM\Temp folder or the Microsoft Data Protection Manager\DPM\Temp
I would suspect just from the error message without looking at logs, that the error is actually on the SharePoint farm!
Walt Whitman [MSFT System Center DPM Team] This posting is provided "AS IS" with no warranties, and confers no rights. -
Wednesday, August 10, 2011 8:41 PM
Don't see any errors on the Sharepiont server (no warnings/failure events in the msdpm.curr.errlog, the wsscmdletswrappercurr.errlog, or the app/system Log). Do see errors int he msdpmcurr.errlog on the SQL server but they really don't seem to give much more of a clue to what is going on than the error message rolled up in DPM does.
Key ones are :
0F44 1190 10-Aug 17:36.2 27 BackupMachine.cs(2596) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING BackupMachine : FAILURE - BACKUP, errorCode=PrmAbortPrepareForBackup
0F44 1190 10-Aug 17:36.2 1 TaskExecutor.cs(843) 821DE265-35A9-48F1-852F-03608F30AEE1 FATAL Task stopped (state=Failed, error=PrmAbortPrepareForBackup; 0; None), search "Task Diagnostic Information" for details.
Log filtered just for job 821DE265-35A9-48F1-852F-03608F30AEE1:
0F44 1564 10-Aug 17:03.6 1 TaskExecutor.cs(81) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL GenerateWorkplan(job=4f1d59bf-994e-49bc-9837-76e3a8c311b7) - Entering
0F44 1564 10-Aug 17:03.6 1 TaskExecutor.cs(127) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL GenerateWorkplan(job=4f1d59bf-994e-49bc-9837-76e3a8c311b7) - Finished (error=False), executing GenerateWorkplanCallback
0F44 1480 10-Aug 17:03.8 1 DPMTaskController.cs(70) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL (job=4f1d59bf-994e-49bc-9837-76e3a8c311b7, taskId=821de265-35a9-48f1-852f-03608f30aee1) DPMTaskControllerHelper : ExecuteTask - CheckTaskStatus returned ReadyToExecute
0F44 1480 10-Aug 17:03.8 1 TaskExecutor.cs(692) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Setting up Fsm: verb[3d859d8c-d0bb-4142-8696-c0d215203e0d]
0F44 1480 10-Aug 17:03.9 27 CommonLoop.cs(343) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL DatamovePollingCmdTimeoutInMin = 30
0F44 1480 10-Aug 17:03.9 27 CommonLoop.cs(343) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL DatamovePollingCmdTimeoutInMin = 30
0F44 1480 10-Aug 17:03.9 1 TaskExecutor.cs(489) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL ExecuteTask(job=4f1d59bf-994e-49bc-9837-76e3a8c311b7) - Starting task instance
0F44 1704 10-Aug 17:03.9 2 EventManager.cs(88) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Publishing event from TaskInstance.cs(407): TaskStart, [TaskID=821de265-35a9-48f1-852f-03608f30aee1]
0F44 1704 10-Aug 17:03.9 1 TaskInstance.cs(444) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Task: Initial transition enqueued, startState='Backup.StartState'
0F44 1704 10-Aug 17:03.9 27 BackupMachine.cs(1897) 821DE265-35A9-48F1-852F-03608F30AEE1 ACTIVITY BackupMachine : Starting machine execution
0F44 9.00E+04 10-Aug 17:03.9 27 FindActiveNodeBlock.cs(884) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Found Principal server for DatasourceId = d9b6fe43-8355-43e8-a621-94e029d76386 Server= xsql5.ccs.local
0F44 1480 10-Aug 17:03.9 27 OperationTypeLock.cs(766) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL In LockServer() of ReplicationOperationTypeLock, returning lockStatus = AcquiredLock
0F44 1480 10-Aug 17:03.9 2 EventManager.cs(88) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Publishing event from Replica.cs(1948): ReplicaStatusChange, [DataSourceID=ea205111-c50c-4e6f-9a7c-bf5bb52c6f4f]
0F44 1480 10-Aug 17:03.9 27 OperationTypeLock.cs(671) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL In Lock() of ReplicationOperationTypeLock, returning lockStatus = AcquiredLock
0F44 1704 10-Aug 17:35.0 27 FsmBlock.cs(130) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING Backup.ReplicaPreBackupBlock : <-- Exited FSM block with FAILURE (errorCode = PrmAbortPrepareForBackup)
0F44 1704 10-Aug 17:35.0 27 RARequestor.cs(188) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Sending Command RACancelAllSubTasks to RAForRead on server xsql5.ccs.local for workitem 363770d7-c38b-44ce-b034-8ea0dff34da1
0F44 1190 10-Aug 17:35.3 27 FsmBlock.cs(118) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Backup.OnFailure(1).RAPostBackupBlock : <-- Exited FSM block with SUCCESS
0F44 1190 10-Aug 17:35.3 27 RARequestor.cs(188) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Sending Command RACancelAllSubTasks to RAForWrite on server xdpm1.ccs.local for workitem 8f76c233-a5ff-4697-8c1c-59ea5eaa6e05
0F44 1190 10-Aug 17:35.3 27 RARequestor.cs(188) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Sending Command RACancelAllSubTasks to RAForRead on server xsql5.ccs.local for workitem 363770d7-c38b-44ce-b034-8ea0dff34da1
0F44 1190 10-Aug 17:35.5 27 BackupMachine.cs(2737) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING BackupMachine : DBCleanup on backup failure with errorCode=PrmAbortPrepareForBackup
0F44 1190 10-Aug 17:35.5 27 BackupMachine.cs(2745) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL BackupMachine: Cleaning up ROlist for DatasetId [e375ae6f-26fe-4ece-85fc-5206929fb155] on backup failure, will also mark Dataset as Invalid
0F44 1190 10-Aug 17:36.0 2 EventManager.cs(88) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Publishing event from ServerAlert.cs(722): AlertStateChange, [ObjectId=a82531a6-324a-45ac-af77-3ede77b9520f]
0F44 1190 10-Aug 17:36.2 27 BackupMachine.cs(2510) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL BackupMachine : Updated Failed TaskCount RaiseOrUpdateShadowCopyFailedAlert for ReplicaId:ea205111-c50c-4e6f-9a7c-bf5bb52c6f4f
0F44 1190 10-Aug 17:36.2 2 EventManager.cs(88) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Publishing event from Replica.cs(1948): ReplicaStatusChange, [DataSourceID=ea205111-c50c-4e6f-9a7c-bf5bb52c6f4f]
0F44 1190 10-Aug 17:36.2 27 OperationTypeLock.cs(812) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL UnlockServer() of ReplicationOperationTypeLock, returning
0F44 1190 10-Aug 17:36.2 27 OperationTypeLock.cs(702) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL In Unlock() of ReplicationOperationTypeLock, returning
0F44 1190 10-Aug 17:36.2 27 BackupMachine.cs(2596) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING BackupMachine : FAILURE - BACKUP, errorCode=PrmAbortPrepareForBackup
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING Task Diagnostic Information - <?xml version="1.0" encoding="utf-16"?>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <TaskExecutionContext>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmWriterId>a65faa63-5ea8-4ebc-9dbd-a0c4db26912a</PrmWriterId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmDatasourceId>d9b6fe43-8355-43e8-a621-94e029d76386</PrmDatasourceId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmActiveNodeName>sqlserver1.domain.local</PrmActiveNodeName>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmLogicalReplicaId>ea205111-c50c-4e6f-9a7c-bf5bb52c6f4f</PrmLogicalReplicaId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmDatasetId>e375ae6f-26fe-4ece-85fc-5206929fb155</PrmDatasetId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmPhysicalReplicaId>e896e72a-8865-4ea0-98fb-7f6792142685</PrmPhysicalReplicaId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmReplicaValidity>Valid</PrmReplicaValidity>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmReplicaStatus>Idle</PrmReplicaStatus>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <PrmOwnerLockId>00000000-0000-0000-0000-000000000000</PrmOwnerLockId>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <TEVerb>DeltaReplicate</TEVerb>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <TEErrorState>Backup.RAPreBackupPending</TEErrorState>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <TEErrorDetails><?xml version="1.0" encoding="utf-16"?>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <q1:ErrorInfo ErrorCode="30200" DetailedCode="0" DetailedSource="0" ExceptionDetails="" xmlns:q1="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd">
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <q1:Parameter Name="datasourceid" Value="d9b6fe43-8355-43e8-a621-94e029d76386" />
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <q1:Parameter Name="datasourcename" Value="sqlserver1\Foundation-Content_Company" />
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <q1:Parameter Name="protectedgroup" Value="-" />
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING <q1:Parameter Name="servername" Value="sqlserver1.domain.local" />
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING </q1:ErrorInfo></TEErrorDetails>
0F44 1190 10-Aug 17:36.2 1 TaskInstance.cs(800) 821DE265-35A9-48F1-852F-03608F30AEE1 WARNING </TaskExecutionContext>
0F44 1190 10-Aug 17:36.2 2 EventManager.cs(88) 821DE265-35A9-48F1-852F-03608F30AEE1 NORMAL Publishing event from TaskInstance.cs(825): TaskStop, [TaskID=821de265-35a9-48f1-852f-03608f30aee1]
0F44 1190 10-Aug 17:36.2 1 TaskExecutor.cs(843) 821DE265-35A9-48F1-852F-03608F30AEE1 FATAL Task stopped (state=Failed, error=PrmAbortPrepareForBackup; 0; None), search "Task Diagnostic Information" for details. -
Wednesday, August 10, 2011 8:50 PMModeratorIf you run a vssadmin list writers on the SQL Server are all writers coming back in a stable state [1] or are tehy listed as waiting on completeion [5]?
Walt Whitman [MSFT System Center DPM Team] This posting is provided "AS IS" with no warranties, and confers no rights. -
Wednesday, August 10, 2011 9:20 PM
They all come back with [1] Stable/No Error. See the Log and Database backups happening in SQL, no errors in the SQL Error Logs or the System/App log on the SQL server.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No errorWriter name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No errorWriter name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No errorWriter name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {0a66663e-90c6-4d6f-8e8d-ec511808b029}
State: [1] Stable
Last error: No errorWriter name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {9f0fe415-0ccd-46b0-99e1-f952c76949a4}
State: [1] Stable
Last error: No errorWriter name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {5cb7370d-8dd1-45e0-ba06-6ee75a32832d}
State: [1] Stable
Last error: No errorWriter name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {2c7fa7e9-f146-4910-9a34-e621929cd591}
State: [1] Stable
Last error: No errorWriter name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {a300ade1-e5d3-4e06-ad3b-d3ca0264b930}
State: [1] Stable
Last error: No errorWriter name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {238e2628-b48d-411a-a484-4eba0076d923}
State: [1] Stable
Last error: No errorWriter name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {ab5f3061-fc5d-48c5-8049-23f0f4b9849b}
State: [1] Stable
Last error: No errorWriter name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {58e8f2eb-9e4a-4ad3-99f5-887e0cf48aec}
State: [1] Stable
Last error: No error -
Thursday, August 18, 2011 3:15 PMModerator
mrg_,
I think you would be better served opening a support case with Micrsoft at this point. without errors to go on it will be difficult to determineexactly what is going on with out a deep look at the systems.
Walt Whitman [MSFT System Center DPM Team] This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer by Walt Whitman [MSFT]Moderator Thursday, August 18, 2011 3:15 PM
.png)
