Troubleshooting General DPM Issues
应用到: System Center Data Protection Manager 2010
The following table provides troubleshooting guidance on general System Center Data Protection Manager (DPM) 2010 issues.
General DPM Issues
Issue | Possible Cause | Resolution |
---|---|---|
DPM stops working when master DB is recovered. |
If the master DB was protected from the same instance as DPMDB, DPM will stop working when the master DB is recovered. |
|
Scheduled jobs not getting triggered when DPM uses a remote SQL instance |
Ensure that the SQL Server services are running as inbuilt accounts (local system network service) or domain accounts. Running the SQL Server services under the "Managed service account" is not supported. |
|
Some of the DPM Management Shell cmdlets do not work on DPM servers that have NETBIOS names longer than 15 characters. |
If the NETBIOS name of the DPM server is longer than 15 characters, use the clipped name within the cmdlets. |
|
Unable to add GUID Partition Table (GPT) disk to storage pool. |
To resolve this issue, either retry the operation or wait 30 sec. |
|
After switching back protection, jobs for some data sources start failing with Access Denied errors. |
A new backend/physical node was added to a SharePoint farm or cluster after switch protection. This node was protected directly by the secondary server. The primary DPM did not know about this new node until protection was switched back. |
|
DPM engine on secondary server stops working after it is denied access to a file on the primary server with the following stack:
|
Lack of permissions to a share or a name resolution conflict. |
Change the name resolution order. For more information see How to change name resolution order on Windows 95 and Windows NT (https://go.microsoft.com/fwlink/?LinkId=187186). |
The user cannot open DPM Administrator Console. |
If the user is a member of a group other than the Administrators group, such as Backup Operator, they will not have access to DPM Administrator Console. |
You must add the user to the Administrators group. |
Error 30115: DPM failed to synchronize changes for <Datasource Type> <Datasource Name> on <Server Name>. |
The shadow copy storage area did not have sufficient storage space to hold the churn on the protected computer. |
Retry the operation at a later point when the churn is expected to be lower. |
Error 30116: VSS has deleted a shadow copy. |
The shadow copy storage area might have run out of disk space on the server <server name>. |
Increase the space allocated for the shadow copy storage area for protected volumes on this computer. To change the settings for shadow copies, do the following:
Note the following:
|