The System Center Data Protection Manager (DPM) 2007 Health Model contains procedures that you can use when troubleshooting DPM events.
DPM alerts are based on the following two events that appear in Event Viewer:
- Event ID 1. Appears when the alert occurs (Level – Error).
- Event ID 2. Appears when the alert is resolved (Level – Information).
Operations Manager uses the Health Model to capture information such as the following:
- A disk in the storage pool has been removed or is not working properly.
- The tape library is offline.
- The Exchange Server or the SQL Server database is offline.
In the DPM Health Model, troubleshooting steps for each alert includes knowledge about how to:
- Diagnose the root cause.
- Resolve each root cause.
- Verify that normal service has been restored.
Following are the DPM alerts:
DPM Alert - Disk missing (3120)
This alert is generated in Data Protection Manager (DPM) when the specified disk in the DPM storage pool could not be detected or has stopped responding. Until the disk is working properly, all protection activities that rely on this disk will fail.
Cause
See the Alert Details pane for more information on the cause of this alert. A disk in the storage pool has been removed or is not working properly.
Resolution
The error conditions and recommended actions associated with each Disk missing alert are provided in the alert details. Follow the recommended action in the alert to retry the job.
On the Disks tab in the Management task area, check the status of the disks.
If a disk is missing:
- Rescan the disk configuration.
- Verify the physical disk connection and perform the rescan again.
If the disk is no longer available, you can remove the disk from the storage pool. To continue protecting the affected data, stop protection of data sources using the Delete option, then add the data sources to a protection group again.
If the replica and the recovery point volume are missing:
- Remove all the protected objects from the protection group.
- Use the New Protection Group Wizard to re-protect the objects to the same group or to a different protection group.
If only the recovery point volume is missing:
- Remove the protected object from the protection group.
- Create a replica manually and add it to the protection group.
For more information, see Managing Disks in DPM Help.
To restore protection after replacing a disk:
In the DPM Administrator Console, remove the disk from the storage pool configuration to prevent future Disk missing alerts.
DPM allocates disk space for the members on a healthy disk, creates the replica, and performs a consistency check. Scheduled synchronization jobs and recovery point creation jobs will resume. (Recovery points that were stored on the missing disk are no longer available.).
When resolved
To check if the issue is resolved:
- Remove the disk from the storage pool.
- Check if DPM detects disk availability in the storage pool.
Additional Information
For more information, see Planning the Storage Pool in DPM 2007 Planning Guide.
.gif)
Back to top
DPM Alert - Agent not reachable (3122)
This alert is generated in Data Protection Manager (DPM) when the protection agent on a specified server could not be contacted. Subsequent protection activities on this server may fail if the connection is not established.
Cause
See the Alert Details pane for more information on the cause of this alert. DPM is not able to contact the protected server because one of the following has occurred:
- There is a network issue.
- The server has been powered down.
Resolution
The error conditions and recommended actions associated with each Agent not reachable alert are provided in the alert details. To resolve this alert, do the following:
- Fix the issue manually by turning on the protected server.
- On the Agents tab in the Management task area, check the status of the agent. Try a refresh to reconnect to the computer.
When resolved
When the protection agent is reachable.
Additional Information
For more information, see How to Update Protection Agent Status in DPM Help.
Back to top
DPM Alert - Backup to tape failed (3311)
This alert is generated in Data Protection Manager (DPM) when the backup-to-tape job on the specific tape fails.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- The tape is stuck in the drive.
- The home slot of a tape currently in the drive is already occupied by another tape.
- The tape dismount failed.
- The tape was decommissioned.
- Network failure.
- Permissions to the protected object are not available.
- The tape is marked suspect.
- Data on the tape is corrupt.
- The tape drive is not operating correctly.
- The tape drive is not online.
- Read or write errors on the tape.
- There is no free tape in the drive.
Resolution
The error conditions and recommended actions associated with each Backup to tape failed alert are provided in the alert details. Retry the job from the recommended action in the DPM Alert User Interface (UI).
When resolved
This alert resolves when one of the following occurs:
- The drive operates correctly.
- There is a free tape in the drive.
- The tape dismount succeeds.
- The tape does not have read or write errors.
Additional Information
For more information, see Managing Tape Libraries topic in the DPM 2007 Operations Guide.
Back to top
DPM Alert - Agent incompatible (3121)
This alert is generated in Data Protection Manager (DPM) when the DPM protection agent that is installed on the specified file or application server is not compatible with the version of DPM that is installed on the DPM server.
On the protected server, the DPM protection agent records changes to protected data and during synchronization transfers these changes from the protected server to the DPM server. If the protection agent is incompatible with the current version of Data Protection Manager, all protection and recovery activities for the protected server will fail until a compatible version of the protection agent is installed.
Cause
See the Alert Details pane for more information on the cause of this alert. A more recent version of Data Protection Manager was installed on the DPM server, but the DPM protection agent on the file or application server was not updated.
Resolution
The error conditions and recommended actions associated with each Agent incompatible alert are provided in the alert details. Follow the recommended action in the alert to retry the job. From the DPM server that is protecting the file server, update the DPM protection agent that is installed on the protected server.
When resolved
When the protection agent is upgraded or uninstalled.
Additional Information
Back to top
DPM Alert - End-user recovery permissions update failed (3123)
This alert is generated in Data Protection Manager (DPM) when synchronization occurs on the specified DPM server, but the permissions that are required for end-user recovery of the data are not updated.
When end-user recovery is enabled in DPM, the replica must be updated with the required access permissions for end-user recovery. Whenever synchronization occurs, the access permissions are updated if changes have been made. Updating the permissions is necessary because it ensures that only authorized end users can recover previous versions of data from the DPM server.
Cause
See the Alert Details pane for more information on the cause of this alert. The error conditions and recommended actions associated with each End-user recovery permissions update failed alert are provided in the alert details. For more information, see How to Display Alert Details in DPM Help. Possible causes include:
- The DPM server was unable to communicate with the protected server.
- DPM was not able to access the Active Directory (AD) directory service.
- DPM was not able to update the Active Directory database.
- The Active Directory schema on the DPM server is not configured properly for end-user recovery.
Resolution
The error conditions and recommended actions associated with each End user recovery permissions update failed alert are provided in the alert details. To resolve this alert, manually synchronize the replica in DPM or wait for the next scheduled synchronization job to run. For more information, see How to Synchronize a Replica in DPM Help. In most cases, this alert will self-resolve and become inactive after the synchronization job is completed.
If the alert details in DPM state in Active Directory schema are not configured properly for end-user recovery, extend the Active Directory schema again. For more information, see How to Enable End-User Recovery in DPM Help.
When resolved
When the end-user recovery permission propagation is successful, or when end-user recovery is turned off.
Additional Information
For more information, see DPM 2007 Deployment Guide in DPM Help.
Back to top
DPM Alert - Catalog build failed (3312)
This alert is generated in Data Protection Manager (DPM) when the backup-to-tape job completed, but the catalog was not built correctly. Although no data is lost, rebuild the catalog to access the data of the backup job.
Cause
See the Alert Details pane for more information on the cause of this alert. The DPM database has grown to the fullest extent and there is no more space on the disk. Possible causes include:
- Network issues happened during the build of the catalog, after the backup completed successfully.
- DPM database could not be accessed.
- The DPM service is down.
- Before cataloging happened, the user canceled the backup job after the backup was done.
Resolution
The error conditions and recommended actions associated with each Library catalog build failed alert are provided in the alert details. Re-run the library catalog build.
When resolved
The library catalog build succeeds.
Additional Information
For more information, see DPM 2007 Operations Guide in DPM Help.
Back to top
DPM Alert - Data corruption detected (3128)
This alert is generated in Data Protection Manager (DPM) when data inconsistency on the replica volume for this data source is identified. Attempts to fix this may not have been successful. Some older recovery points may not be completely recoverable.
Cause
Hardware issues on the protected computer or DPM server.
Resolution
To resolve this alert, do the following:
- Review the system event log of protected computers and DPM server for any hardware-related errors and rectify them.
- Perform test recoveries of the last recovery point on the volume and a few older recovery points of interest.
- Create new recovery points manually for the data sources indicated in the error.
- Run integrity check more frequently.
Back to top
DPM Alert - Data corruption detected during read (3129)
This alert is generated in Data Protection Manager (DPM) when there is a data inconsistency during the backup of this data source.
Cause
Possible causes include:
- Input/output (I/O) errors on a protected computer.
- Hardware issues on a protected computer
Resolution
To resolve this alert, do the following:
- Review the system event log of the protected computer for any hardware-related errors, and rectify them. Run hardware diagnostic tools to verify the health of the hardware.
- Run application-specific integrity checks to ensure logical consistency of data. In case of failure, recover the data from the last recovery point and perform an application-specific integrity check.
- Repeat the process with previous recovery points till a logical consistent recovery point is recovered. Create new recovery points manually for the data source indicated in the error. Run integrity checks more frequently.
Back to top
DPM Alert - Failed to stop protection (3116)
This alert is generated in Data Protection Manager (DPM) when the protected data source is removed from its protection group, however DPM fails to stop protecting the data source.
Cause
When the data source is removed from the protection group, DPM must delete the volume bitmaps associated with the data source. These volume bitmaps track changes on respective volumes for the data source where protection is being stopped. In this case, the volume bitmaps were not deleted and the protection agent was not updated because of the loss of a network connection between the DPM server and the protected server. As a result, the protection agent continues to track changes for the specified volume.
Resolution
The error conditions and recommended actions associated with each Failed to stop protection alert are provided in the alert details. Follow the recommended action in the alert to retry the job.
To stop protecting all data sources on the protected server, and if you no longer want to protect any data sources on the protected server, then you can locally uninstall the protection agent from the protected server. For more information, see How to Uninstall a Protection Agent in DPM Help.
To retry the job, do the following:
- In the DPM Administrator Console, locate the critical Failed to stop protection alert.
- In the Display pane, select the Failed to stop protection alert.
- In the Details pane, click Stop protecting the volume. A new, internal stop protection job is scheduled to run immediately. The job is internal; DPM does not display it in the user interface.
- The Stop protecting the volume link disappears from the Details pane after one attempt to retry the job. If the job fails again, the volume is still protected and DPM displays a new alert for the failed stop protection.
When resolved
When the stop protection task succeeds.
Back to top
DPM Alert - Manual replica pending (3118)
This alert is generated in Data Protection Manager (DPM) when the replica for a specific data source on a specified server is not created. You have chosen to create the replica manually. All subsequent protection activities for this data on the specified server will fail until the replica is created and synchronized with a consistency check.
Cause
In the Data Protection Wizard or in the command-line interface (DPM Management Shell), you chose to manually copy the data you want protected to the DPM computer.
Resolution
The error conditions and recommended actions associated with each Manual replica creation pending alert are provided in the alert details. Manually copy data to the specified replica path. After you copy the data, click the link below to synchronize with consistency check. You must synchronize with a consistency check.
When resolved
When a verification task starts and a Replica inconsistent, verification in progress alert is raised.
Additional Information
Back to top
DPM Alert - Recovery failure (3111)
This alert is generated in Data Protection Manager (DPM) when a recovery job fails completely.
Cause
See the Alert Details pane for more information on the cause of this alert. For more information, see How to display Alert Details in DPM Help. Possible causes include:
- DPM could not copy data to the specified recovery destination.
- The default recovery destination no longer exists or could not be accessed.
- When the original protected computer is in active protection (that is, it is being protected by a primary computer), then recovery will fail to recover from a secondary computer to its original protected computer.
For Exchange Server and SQL Server, some possible causes include:
- Recovery failed while mounting the database.
To resolve the issue, look at the event logs on the computer running Exchange Server. You can try mounting the database manually.
- Recovery failed while applying the logs.
To resolve the issue, look at the event logs on Exchange Server. You can try manually applying the logs using Eseutil.exe and mounting the database after that.
- The database was deleted.
- The Exchange or SQL Server service is not running.
- For SQL Server, the SQL writer service has been turned off.
- There are disk issues on the application server.
- There are Volume Shadow Copy Service (VSS) writer issues.
For Exchange Server, some possible causes include:
- The Eseutil.exe utility failed to apply the logs on the Exchange Server database files to bring the database to a clean shutdown state.
- The Exchange database is not allowed to be overwritten by a recovery job.
- The name of the storage group or database is different from what it was during backup.
- The Exchange writer may be in a bad state. You need to restart the Exchange Information Store Service.
- The storage group is deleted.
For Windows SharePoint Services, apart from all the SQL Server causes, the SharePoint writer (or Search writer) may not be running or may be in a bad state.
Restart the writer. Possible causes for site and document backup failure include:
- The corresponding content database could not be attached to the specified SQL Server instance.
- The corresponding content database could not be made a part of the specified recovery Windows SharePoint Services farm.
- A Web application by the name DPMRecoveryWebApplication has not been created on the recovery farm.
- The export or import operation for the recovery item has failed.
Note
Please check if the WSSCmdLets.exe DCOM component on both the recovery farm as well as the production farm has been given farm administrator privileges. This is part of the prerequisites before protecting a farm.
Resolution
The error conditions and recommended actions associated with each Recovery failure alert are provided in the alert details. To resolve this alert, do the following:
- On the Jobs tab in the Monitoring tasks area, group jobs by type to view details of the recovery jobs.
- Go to the Alerts view and re-run the recovery jobs from the link provided.
- Start a new recovery job for the data that DPM failed to recover.
- Before you recover from a secondary DPM server, make sure that no jobs are running on the primary protected computer (This is only necessary for data recovery).
Note
You can run the job again by clicking the recommended action on the alert. This alert automatically becomes inactive in DPM seven days after the recovery collection job has failed.
For more information, see How to Display Alert Details in DPM Help.
For more information, see How to Display Job Details in DPM Help.
When resolved
When job completes successfully.
Additional Information
For more information, see DPM 2007 Operations Guide in DPM Help.
Back to top
DPM Alert - Recovery partial success (3110)
This alert is generated in Data Protection Manger (DPM) when one or more files could not be recovered successfully.
Cause
See the Alert Details pane for more information on the cause of this alert. This alert is raised only for recovery of data on protected computers. The error conditions and recommended actions associated with each Recovery failure alert are provided in the alert details on the DPM server. Possible causes include:
- DPM was unable to copy data to the specified recovery destination.
- The default recovery destination no longer exists or cannot be accessed.
Resolution
The error conditions and recommended actions associated with each Recovery partially successful alert are provided in the alert details. To resolve this alert, do the following:
- On the DPM server that is protecting the protected computer, review the alert and job details in the Monitoring task area of DPM Administrator Console, and perform the recommended action.
- From the alerts details, make sure that the file is not already present and in use on the destination server, and that there is sufficient disk space for the files.
- Start a new recovery job for the data that DPM failed to recover.
When resolved
When job completes successfully. DPM automatically marks the alert as inactive seven days after the recovery job has completed.
Additional Information
For more information, see DPM 2007 Operations Guide in DPM Help.
Back to top
DPM Alert - Recovery point creation failed (3114)
This alert is generated when Data Protection Manager (DPM) fails to create a recovery point for a data source. When the next recovery point creation fails, the count of the recovery point creation failure is updated. DPM creates points in time (recovery points) of the backup data source, from which you can recover data.
Cause
See the Alert Details pane for more information on the cause of this alert. This alert indicates that some recovery points for the specified server have not been created. The number of missing recovery points is indicated in the DPM user interface. For more information, see How to Create a Recovery Point in DPM Help.
Some possible causes are:
- For File Servers:
- The protected file server unexpectedly shuts down.
- The protected file server is offline, unavailable, or in a restoring state.
- For Exchange Server and SQL Server:
- The Exchange Server or the SQL Server database unexpectedly shuts down.
- The Exchange Server or the SQL Server database is offline, unavailable, or in a restoring state.
- The disk that contains the SQL Server or Exchange Server database logs is unreachable.
- The Exchange Server or the SQL Server database is unavailable.
- The Exchange Server or the SQL Server database is offline.
- The Exchange Server storage group or SQL Server database was deleted.
- The SQL Server database is in a restoring state.
- There is a problem with the Volume Shadow Copy Service (VSS) writer.
- A new database has been added to the application server.
- For SQL Server and Exchange data protection, DPM causes synchronization to fail to prevent recovery points from being deleted.
- For Exchange Server only:
- DPM has detected a new Exchange Server database on the protection server. This means that DPM needs to re-run a full backup. This may be run during the daytime and may cause a performance hit on the server. The replica will be marked as inconsistent and the synchronization will fail.
- The Eseutil.exe utility failed to verify the dataset data on the replica.
- For Windows SharePoint Services Server and SQL Server:
- DPM has detected that a new component has been added to the protected Windows SharePoint Services farm after the last backup, so the replica is marked invalid.
- The WSSCmdLets.exe DCOM component on the production farm has not been given farm administrator credentials.
- For Virtual Server:
- Virtual Machine additions were uninstalled from Virtual Machine.
- A non-NTFS, iSCSI, SAN, or remote volume was attached to Virtual Machine.
Resolution
The error conditions and recommended actions associated with each Recovery point creation failed alert are provided in the alert details. Follow the recommended action in the alert to retry the job. You establish the recovery point schedule when you create a protection group or when you modify the protection options for an existing protection group. You can access the recovery points on the DPM server to recover previous versions of data.
You can manually create a recovery point from either the Protection task area or the Recovery task area. Manually create a recovery point. For more information, see How to Create a Recovery Point in DPM Help.
When resolved
A recovery point creation task succeeds.
- To resolve failures related to a protected file server being offline or unavailable, ensure that the protected file server is online and available.
- To resolve Exchange Server and SQL Server failures related to a failed synchronization, a full data recovery not complete, or when an Exchange Server storage group or SQL Server database is deleted, increase space on the disk or delete old shadow copies.
- To resolve failures when the SQL service or Exchange service is down, do the following:
- Inform the administrator that the service is down and ask him or her to manually restart the service.
- After fixing the issue, click on the recommended link in the alert, which re-runs the synchronization job.
- To resolve failures when the disk that contains the SQL Server or Exchange Server database logs is unreachable, do the following:
- Inform the administrator that the service is down and ask him or her to manually restart the service.
- After fixing the issue, click on the recommended link in the alert which re-runs the synchronization job.
- To resolve Exchange Server failures when a new Exchange database is detected or when Eseutil.exe fails to verify dataset data, do the following:
- Run a full backup so that the overall storage group protection is not affected.
- Reject the full backup for now if it is okay for the storage group to remain unprotected until the next full backup. The failure will automatically resolve after the next full backup.
- To resolve Windows SharePoint Services Server failures, do the following:
- Run a consistency check.
- The WSSCmdLets.exe DCOM component on the production farm has been given farm administrator credentials. (This is part of the prerequisites before protecting a farm.)
Note
For this issue, you need to run C:\Program Files\Microsoft DPM\bin\ConfigureSharepoint.exe. This executable asks you for the account and password details and performs the required changes.
- For resolver Virtual server failures, do the following:
- Make sure the Virtual Machine addition is installed on Virtual Machine.
- Do not attach non NTFS, iSCSI, SAN, or a remote volume to the Virtual Machine.
Back to top
DPM Alert - Replica is inconsistent (3106)
This alert is generated in Data Protection Manager (DPM) when the replica of the specified volume on the specified server is inconsistent with the data source. All protection activities for the data source will fail until the replica is made consistent with the data source by performing synchronization with consistency check. Although the replica is marked inconsistent, older recovery points are still recoverable. Validate and fix the replica as soon as possible.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- For an inconsistent replica:
- A replica creation job did not complete successfully for any of a number of reasons; for example, a connection failed or the job was canceled.
- There were issues with the change journal which marked the replica as invalid.
- There were volume filter bitmap errors.
- DPM determined that the file server shut down unexpectedly.
- The replica was valid but the administrator opted to run a consistency check; therefore, DPM marked the replica as invalid.
- For SQL Server and Exchange Server:
- DPM ran out of bitmap space on the protected server.
- Possible owner nodes have been added for a protected cluster resource.
- The propagation of DPM configuration information (such as volume filter information) about clustered resources failed to detect all possible owner nodes.
- For Exchange Server:
- The Eseutil.exe utility check failed on a replica.
- The path of the database or log files has changed.
- DPM detected a new Exchange Server database on the application server. The replica is marked as inconsistent and the synchronization fails.
- DPM has detected an unplanned cluster failover.
- For Windows SharePoint Services Server:
- All of the SQL causes apply, as well as a component has been added to the farm.
- For Virtual Server:
- A new disk was added to the Virtual Machine.
- Paths to virtual hard drives may have changed.
Resolution
The error conditions and recommended actions associated with each Replica inconsistent alert are provided in the alert details. Follow the recommended action in the alert to retry the job.
- To remove the inconsistencies with the data source, do the following:
- A consistency check must be performed on the specified replica.
- If a daily consistency check is scheduled for the protection group, DPM will automatically perform the consistency check at the next scheduled time. For more information, see How to Modify Protection Options in DPM Help.
- If the consistency check fails, the database on the protected server is corrupt and it needs to be manually corrected. Otherwise, you need to manually perform a consistency check on the replica. For more information, see How to Synchronize a Replica in DPM Help.
- For Exchange Server:
- Ensure that the version of the Exchange Server Database Utilities (Eseutil.exe and Ese.dll) that are installed on the computer running the most recent edition of Exchange Server must be the same versions that are installed on the DPM server.
- You use the Microsoft Exchange Server 2007 management tools to maintain up-to-date copies of Eseutil.exe and Ese.dll. If the remote computer is running a 32-bit operating system, you must download the Microsoft Exchange Server 2007 32-bit management tools.
When resolved
When DPM verifies the replica. When the verification task starts, this alert changes to the Verification in progress alert.
Additional Information
Back to top
DPM Alert - Replica inconsistent, verification in progress (3104)
This alert is generated when the specified replica on the Data Protection Manager (DPM) server is currently being synchronized with consistency check. A consistency check can be started automatically or manually.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- A consistency check job needs to run after the initial replication when you manually create a replica for a data source.
- DPM has not completed synchronizing and verifying the replica.
Resolution
No actions required to resolve this alert.
When resolved
When consistency check is complete.
Additional Information
Back to top
DPM Alert - Synchronization failures (3115)
This alert is generated in Data Protection Manager (DPM) when synchronization jobs have been failing on protected servers since the specified time. To help you determine whether the issue is critical, the alert specifies the number of synchronization jobs that have failed. DPM automatically reports this alert as inactive after the next successful synchronization job.
Note
For application servers, every synchronization is a recovery point creation. If application server synchronization fails, the alert Recovery point creation failed appears.
Cause
See the Alert Details pane for more information on the cause of this alert. DPM will only display this alert for synchronization failures of protected computers.
There are multiple causes for synchronization failures. The alert details in DPM list the error conditions and recommended action associated with the most recent synchronization failure. For more information about alert details, see How to Display Alert Details in DPM Help. Possible causes include:
- The DPM server cannot communicate with a protected file or application server.
- The replica has run out of disk space in the DPM storage pool.
- A recovery job was started while a synchronization job was running. Recovery jobs take priority over other DPM jobs, so the synchronization job was canceled.
- An express full backup was not complete when a scheduled synchronization job started.
- The Volume Shadow Copy Service (VSS) writer did not work correctly.
- Creation of a recovery point volume on the protection server fails.
Resolution
The error conditions and recommended actions associated with each Synchronization failures alert are provided in the alert details. See the Properties tab for details on the cause of the alert. To resolve the issue, do the following:
- To resolve synchronization failure due to network issue, re-run the synchronization job. For more information, see Agent not reachable in DPM Help.
- To resolve failures related to Update Sequence Number (USN), change journal errors. Use the New Protection Group Wizard to increase the change journal to more than 300 MB, which is the default.
- To resolve failures related to inadequate disk space for the replica, do the following:
- Compare the disk space used to the disk space allocated for the associated replica. You can use the data in the Disk Utilization Report to help you with the comparison. For more information, see Disk Utilization Report in DPM Help.
- If the Disk Used size is nearly as large as the Disk Allocated size, you should increase the disk space allocated for the replica. For more information, see How to Modify Disk Allocation in DPM Help.
- To resolve failures when the VSS writer is in a bad state or when a recovery point on a protected server fails, do the following:
- Check the event logs for any VSS writer errors.
- Run a consistency check on the replica.
When resolved
When a synchronization task succeeds.
Additional Information
Back to top
DPM Alert - Volume missing (3101)
This alert is generated in Data Protection Manager (DPM) when the recovery data on a specified server in a protection group resides on a volume that DPM cannot detect. All subsequent protection activities relating to this volume will fail until the volume is brought back online or until the replica is re-created.
Cause
See the Alert Details pane for more information on the cause of this alert. DPM is not able to detect the volume or disk where the replicas are stored. This happens when the volume is offline.
Resolution
Verify that the disk containing the replica volume and the recovery point volume is shown in Disk Management. If you are unable to locate the volumes in Disk Management, then in the Protection task area of DPM Administrator Console, stop protection of the data source using the Delete replica option, and then add the data source to a protection group again. For more information about how to check the status of the replica, see Working with Replicas in DPM Help.
To reallocate the replica, stop protection, delete the replica, and restart protection. For more information, see Working with Protection Groups in DPM Help. When volume comes up again or replica is re-allocated, the state of replica is changed from missing to active and DPM can protect and recover data from that volume.
When resolved
When DPM detects a volume or when the replica is reallocated.
Additional Information
For more information, see Protecting Data in DPM Help.
Back to top
DPM Alert - Unable to configure protection (3170)
This alert is generated when Data Protection Manager (DPM) could not start a recovery, consistency check, or initial replica creation job for the DPM database on the designated server.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- Protection agent issue, including a bad version, or not reachable (network issue).
- Any Microsoft Volume Shadow Copy Service (VSS) issues, such as problems with backing up data.
- In a cluster scenario, after initialization of one node, if any of the other nodes in the cluster is down, unreachable and so on, this alert is raised.
Note
The job initialization failure also generates a Replica inconsistent alert. DPM will not perform the initial replica creation until all of the nodes in the cluster initialize successfully.
Resolution
The error conditions and recommended actions associated with the alert appear in the alert details.
Back to top
DPM Alert - Recovery Point Volume threshold exceeded (3169)
This alert is generated in Data Protection Manager (DPM) when the disk space used for the specified shadow copies on the DPM server has exceeded the recommended threshold of 90 percent. To avoid compromising data protection, you must allocate more disk space for shadow copies in the storage pool. If you do not allocate more disk space, synchronization jobs may fail due to insufficient disk space.
Causes
See the Alert Details pane for more information on the cause of this alert. Some possible causes for this alert include:
- The size of the protected data on the source volume may have increased significantly since the protection group was created.
- The data change rate for the data source may be high, causing the shadow copies to use more space than expected.
Resolution
On the DPM server, allocate more disk space in the storage pool for the replica. For more information, see How to Modify Disk Allocation in DPM Help.
If no additional disk space is available in the storage pool, you may need to add a physical disk drive to the DPM server and then add the disk to the storage pool. For more information, see Adding Disks to the Storage Pool in the DPM 2007 Deployment Guide.
Additional Information
For more information, see Planning a Deployment chapter in the DPM 2007 Planning Guide.
Back to top
DPM Alert - Replica disk threshold exceeded (3100)
This alert is generated in Data Protection Manager (DPM) when the disk space used for the specified replica on the DPM server has exceeded the recommended threshold of 90 percent. To avoid compromising data protection, you should allocate more disk space for the replica in the storage pool. If you do not allocate more disk space, synchronization or recovery point creation jobs may fail due to insufficient disk space.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes for the replica disk threshold exceeded alert include:
- The data change rate for the data source may be higher than expected, causing the replica to run out of space.
- Enough disk space in the storage pool might not have been allocated for the replica. Check that the minimum disk space is at least 1.5 times the size of the used space on the protected volume or the total size of the protected volume whichever is smaller, or 1.5 GB.
- The size of the protected data on the source volume may have increased significantly since the protection group was created; this might have resulted in using more tapes than expected.
- DPM determined that there is no free disk space in the storage pool.
Resolution
The error conditions and recommended actions associated with each Replica disk threshold exceeded alert are provided in the alert details.
Follow the recommended action in the alert to retry the job. On the DPM server, allocate more disk space in the storage pool for the replica. For more information, see How to Modify Disk Allocation in DPM Help.
If no additional disk space is available in the storage pool, you may need to add a physical disk drive to the DPM server and then add the disk to the storage pool. For more information, see Adding Disks to the Storage Pool in DPM 2007 Deployment Guide.
When resolved
When allocated disk space is changed or when more disk space is added.
Additional Information
For more information, see DPM 2007 Deployment Guide in DPM Help.
Back to top
DPM Alert - Consolidation of recovery points of the replica failed (3178)
This alert is generated in Data Protection Manager (DPM) when the consolidation of recovery points for the replica fails before one of the following operations is performed:
- Express full backup.
- Consistency check.
- Recovery.
Cause
See the Alert Details pane for more information on the cause of this alert. Some possible causes for this alert include:
- Volume Shadow Copy Service (VSS) issues.
- Not enough space in volume.
- Agent-related issues - unreachable (network issues) or bad version.
Resolution
Check the Alerts pane to locate the specific alert for the express full backup, consistency check, or recovery job. Follow the recommended action for the alert. Click the link to dismiss the alert.
When resolved
The recovery point consolidation succeeds.
Back to top
DPM Alert - Tape copy failed (3310)
This alert is generated in Data Protection Manager (DPM) when the tape data copy job on the specific tape failed.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in the DPM Administrator Console, determine why the tape data copy failed, and take the appropriate action. Possible causes include:
- The tape drive is not operating correctly.
- The tape drive is not online.
- There is no free tape.
- There is no expected tape to copy from.
- The tape may have read or write errors on it.
Resolution
The error conditions and recommended actions associated with each Tape data copy failed alert are provided in the alert details. Re-run the tape data copy job when the tape drive operates correctly and is online, a free tape exists in the tape library, or the tape does not have errors.
When resolved
When tape data copy job succeeds.
Additional Information
Back to top
DPM Alert - Tape detailed inventory failed (3316)
This alert is generated in Data Protection Manager (DPM) when the detailed inventory for a specified tape in a specified tape library fails.
Cause
See the Alert Details pane for more information on the cause of this alert. The detailed inventory of tapes fails for the following reasons:
- The tape was bad.
- The library or drive failed.
Resolution
The error conditions and recommended actions associated with each Detailed inventory of tape failed alert are provided in the alert details. Re-run tape inventory. For more information, see How to Inventory the Tape Library in DPM Help.
When resolved
The detailed inventory for the specified tape in the specified library succeeds.
Additional Information
For more information about how to manage tape libraries in DPM and how to run a tape inventory, see Managing Tape Libraries chapter in the DPM 2007 Operations Guide in DPM Help.
Back to top
DPM Alert - Free tape threshold reached (3305)
This alert is generated in Data Protection Manager (DPM) when the free tape count for the specified library is less than the threshold value. You must add the tape to the library and mark it as free, or future backup jobs will fail.
Cause
See the Alert Details pane for more information on the cause of this alert. This alert is usually caused because the free tape pool is low.
Resolution
The error conditions and recommended actions associated with each Free tape threshold reached alert are provided in the alert details. Follow the recommended action in the alert and retry the job. Add a tape to the library and mark it as free.
When resolved
If no protection group is associated with the library, when the record is removed, or when a tape is added to the library.
Additional Information
Back to top
DPM Alert - Library not available (3301)
This alert is generated in Data Protection Manger (DPM) when the specified tape library could not be contacted.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape library is not available, and take the appropriate action. Possible causes include:
- The tape library is offline.
- The tape library is not working correctly.
- The library door is open or the library is not ready.
- The tape is stuck in the changer. If this happens, the entire library is disabled and all jobs will fail.
- A changer input-output-control (IOCTL) failure. If this happens, the entire library is disabled and all jobs will fail.
Resolution
The error conditions and recommended actions associated with each Library not available alert are provided in the alert details. To resolve this alert, do the following:
- Ensure that the tape library is online and working correctly.
- Check for loose connections on data in SCSI or power channel.
- Make sure the library is visible in Windows Device Manager (Click Start, Settings, and then Control Panel to open the Control Panel. Next, click System, and then click the Hardware tab. Click Device Manager to display a list of devices recognized by Windows.)
- Close the door on the library.
- If the tape is stuck in the changer, remove the tape. If the tape cannot be removed, call a repair technician.
- When fixed, click the link in the alert to re-run the jobs.
When resolved
This alert is resolved if one of the following occurs:
- If no protection group is associated with the library when the record is removed.
- When the library is visible in Windows Device Manager or when the library door is closed.
Back to top
DPM Alert - Library not functioning efficiently (3302)
This alert is generated in Data Protection Manager (DPM) when the specified library is not functioning efficiently because the drive information for the library is incorrect and needs to be refreshed.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape library is not working efficiently, and take the appropriate action. The possible cause for the Library not working efficiently alert is that the number of drives reported for this library is different from the number of drives detected by DPM.
Resolution
The error conditions and recommended actions associated with each Library not working efficiently alert are provided in the alert details. If any drives are out of library for servicing, ignore this alert.
When resolved
When the library information shows up correctly.
Back to top
DPM Alert - Tape erase failed (3308)
This alert is generated in Data Protection Manager (DPM) when the tape erase job on the specific tape fails.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape erase failed, and take the appropriate action. Possible causes include:
- The tape drive is not operating correctly.
- The tape drive is not online.
- The tape may have read or write errors on it.
Resolution
The error conditions and recommended actions associated with each Tape erase failed alert are provided in the alert details. Follow the recommended action in the alert and retry the job. Re-run tape erase job.
When resolved
The tape drive operates correctly, is online, or the tape erase job succeeds on retry.
Additional Information
Back to top
DPM Alert - Cannot verify tape data (3309)
This alert is generated in Data Protection Manager (DPM) when the tape verification did not start due to tape or library issues. This could cause data loss during recovery.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape verification failed, and take the appropriate action. Possible causes include:
- The tape has read/write errors.
- There is a network failure at the DPM or protected server side.
- Permissions or passwords have changed and DPM cannot access the folder to back up or recover data.
- Two tapes have the same barcode but different On-Media Identifier (OMID).
- Two tapes have the same OMID but different barcodes.
- Two tapes have the same OMID, one with a barcode and the other without a barcode.
- A tape that had been in use by one DPM installation was moved and written by a different DPM installation and then put back in the original DPM installation.
- Data is corrupt on the tape.
Resolution
The error conditions and recommended actions associated with each Cannot verify tape data alert are provided in the alert details. Follow the recommended action in the alert and retry the job. To resolve this alert, do the following:
- If the tape has read/write errors, then run a recovery job, look for duplicate tape or an older point in time copy of the same data.
- Fix the network failure and re-run the job.
- Ensure that permissions and passwords are correct so that DPM can access the tape.
- If there are two tapes with the same barcode but different OMID, then contact the administrator to ensure that each tape has a unique barcode.
- If there are two tapes with the same OMID but different barcodes, then the administrator could have switched the barcode on the tape causing one of the tapes to be offline. In this case, the two tapes can be labeled the same.
- If both the tapes have the same OMID, one with the barcode and the other without the barcode, then the administrator must provide a unique barcode for both the tapes.
- If the tape has been overwritten, then it cannot be used.
When resolved
When the job is re-run, DPM is able to access the tape; two tapes have unique barcodes.
Additional Information
For more information, see Managing Tape Libraries chapter in the DPM 2007 Operations Guide in DPM Help.
Back to top
DPM Alert - Tape data integrity issues found (3317)
This alert is generated in Data Protection Manager (DPM) when data verification of the data on a tape found integrity issues.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine the reason for data corruption and take appropriate action.
Resolution
Re-do the backup.
Back to top
DPM Alert - Library drive is not functioning (3303)
This alert is generated in Data Protection Manager (DPM) when the drive for the tape library is not functioning. Library jobs may fail until the drive is repaired. This is a important issue and may cause degradation of backup or any other library-related job performance and, in some cases, job failure.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape drive is not available, and take the appropriate action. Possible causes include:
- The tape library drive is not switched on.
- The tape library drive is not operating correctly and needs servicing.
- Drive cleaning failed.
- The drive experienced an error such as tape error, device input/output (I/O) error, or an I/O control (IOCTL) error.
Resolution
The error conditions and recommended actions associated with each Library drive not functioning alert are provided in the alert details. Follow the recommendation in the alert and retry the job. To resolve this alert, do the following:
- Ensure that the tape library drive is turned on.
- The drive mapping for the library drive may have changed. Re-map the drive manually.
- Change the cleaner tape and retry cleaning.
- Review drive allocations for different protection groups to see if these values need to change because one of the drives in no longer available.
- If the library drive needs servicing, call the repair technician.
When resolved
When tape drive is detected and functions properly. This alert is resolved if one of the following occurs:
- When the record is removed.
- When the tape library drive is turned on.
- When the cleaner tape is changed and cleaning is retried.
- When drive allocations are valid; or when the library drive is serviced.
Back to top
DPM Alert - Job waiting for tape (3315)
This alert is generated in Data Protection Manager (DPM) when the specified task is paused because the required tape is not available in the specified tape drive.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- For recovery or data copy operations, the required tape is not in the drive.
- For backup jobs, a free tape is not available.
- The library door is unlocked.
Resolution
The error conditions and recommended actions associated with each Job waiting for tape alert are provided in the alert details. To resolve this alert, do the following:
- Insert the tape with the specified label into the library through the IE port or by unlocking the library door.
- Click Continue Job in the details section of this alert if Insert tape into IE Port or Unlock Door were not invoked from Library Management.
- There is a timeout of 60 minutes to continue the job. If you do not click Continue Job within 60 minutes, the task fails.
When resolved
There is a free tape available for backup jobs, the required tape is in the drive, or the library door is locked.
Back to top
DPM Alert - Database size threshold exceeded (3168)
This alert is generated in Data Protection Manager (DPM) when the disk space used for the catalog information database on the DPM database exceeds the user-set threshold. The DPM tape catalog keeps information of the recoverable items on tapes that are protected for short-term and long-term.
Cause
See the Alert Details pane for more information on the cause of this alert. Review the alert details in DPM Administrator Console, determine why the tape catalog database threshold has been exceeded, and take the appropriate action.
The alert is raised because the size of the catalog information database on the DPM server may have increased significantly since the protection group was created.
Resolution
Prune the catalog information database to reduce the size below the threshold value or increase the threshold value.
To increase the threshold value on the DPM server, allocate more disk space for the database. For more information, see How to Modify Disk Allocation in DPM Help. If no additional disk space is available, you may need to add a physical disk drive to the DPM server; see your computer’s operating manual.
When resolved
To check if the issue is resolved, verify the following:
- Additional disk space is allocated for the database.
- The library catalog is pruned.
- An additional disk drive is added to the DPM server.
Back to top
DPM Alert - Server processor usage
This alert is generated in Data Protection Manager (DPM) when the processor usage on the protected computer is more than 80 percent in two consecutive samples across 30 minutes.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- There are too many processes running on the protected computer.
- One of the processes running on the protected computer is taking up too many CPU cycles.
Resolution
Select Task Manager on the protected computer and see if you can either close unnecessary processes or stop the process that is consuming CPU cycles.
Back to top
DPM Alert - Server memory usage
This alert is generated in Data Protection Manager (DPM) when the memory availability on the DPM server falls below 100 MB in two consecutive samples across 30 minutes.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- There are too many programs running on the DPM Server.
- The memory on the server is too little.
Resolution
To resolve this alert, either close any unnecessary programs or add more memory to the server.
Back to top
DPM Alert - Tape encryption certificate expiration (24059)
This alert is generated in Data Protection Manager (DPM) when a certificate used for encrypting data on tape is expected to expire soon. All backup-to-tape jobs that require data encryption will fail after this time.
Cause
All certificates are set to expire after a period of time. New certificates must be obtained.
Resolution
If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
Additional Information
For more information, see How to Encrypt Data in a Protection Group in DPM Help.
Back to top
DPM Alert - No agent on cluster node (369)
This alert is generated in Data Protection Manager (DPM) when a protection agent is not installed on one or more of the cluster nodes. You cannot start protection until agents are installed on all nodes.
Cause
The agent has not been installed on the node.
Resolution
Install the protection agent on each node of the server cluster.
Back to top
DPM Alert - Server not available
This alert is generated in Data Protection Manager (DPM) when a MSDPM service on the DPM server is not running. A script is run to check the status of MSDPM service on the DPM server.
Cause
Possible causes include:
- The MSDPM service is down.
- The SQL server instance or database is not reachable.
- A network outage has occurred on the DPM or Operations Manager.
Resolution
To resolve this alert, do the following:
- Start the MSDPM service.
- Start the SQL server instance if it is not running.
- Check the network on DPM or Operations Manager.
Back to top
DPM Alert - Agent operation failed (370)
This alert is generated when Data Protection Manager (DPM) cannot install, upgrade, or uninstall a protection agent on a specified protection group.
Cause
See the Alert Details pane for more information on the cause of this alert. Possible causes include:
- DPM could not reach the protected computer.
- The firewall on the protected computer is blocking requests from DPM.
- The Remote Procedure Call (RPC) service is down on the protected computer.
- Internet Protocol Security (IPSec) is turned on for only one server, either on the protected computer or DPM.
Resolution
The error conditions and recommended actions associated with each Agent operation failure alert are provided in the alert details. Re-install the protection agent on the specified protection group. For more information about installing the protection agent, see How to Install a Protection Agent in DPM Help.
If you do not want to install a protection agent on the specified protection group, click the link in the alert to mark it as inactive. For more information about updating a protection agent, see How to Update a Protection Agent in DPM Help.
When resolved
DPM automatically changes this alert’s status to inactive after 3 days.
Additional Information
For more information, see The DPM 2007 Deployment Guide in DPM Help.
Back to top