Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Troubleshooting General DPM Issues

Updated: April 21, 2010

Applies To: 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.

  1. Attach agent from primary DPM to the newly added computer.

  2. Run SetDPMServer -DPMServerName <primaryDPM.domain.com> on the newly added computer.

  3. Make sure the primary protection is green.

  4. Now run modify protection group on the secondary DPM server for the protection group containing affected data source.

    1. Expand the primary DPM server node in the Modify Protection Wizard.

    2. Expand the SharePoint front-end/resource group to which the new computer was added.

  5. Save the protection group.

DPM engine on secondary server stops working after it is denied access to a file on the primary server with the following stack:

Access to the path '\\dpmserver.contoso.com\MTATempStore$\PSInfo\78b18367-eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.</ExceptionMessage><ExceptionDetails>System.UnauthorizedAccessException: Access to the path '\\dpmserver.contoso.com\MTATempStore$\PSInfo\78b18367-eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)

at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)

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 (http://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:

  1. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Computer Management to open Computer Management.

  2. In the console tree, expand the node to Computer Management/System Tools/Shared Folders.

  3. Right-click Shared Folders, select All Tasks, and click Configure Shadow Copies.

  4. Click the volume where you want to make changes, and then click Settings.

  5. In the Settings dialog box, change the settings as appropriate.

Note the following:

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Administration group might be able to perform this procedure.

  • There is a limit of 64 shadow copies per volume that can be stored. When this limit is reached, the oldest shadow copy will be deleted and cannot be retrieved.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.