This alert is generated when DPM fails to create a recovery point for a data source. Data Protection Manager (DPM) creates recovery points for each data source from which you can recover data.

Causes

This alert indicates that some recovery points for the specified computer have not been created. The number of missing recovery points is indicated in DPM Administrator Console.

For information about how to manually create a recovery point, see How to Create a Recovery Point.

For File Servers and Workstations:

Possible causes for the alert include the following:

  • The protected computer unexpectedly shuts down.

  • The protected computer is offline, unavailable, or in a restoring state.

For Exchange Server and SQL Server:

Possible causes for the alert include the following:

  • 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 Exchange Server or 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:

Possible causes for the alert include the following:

  • DPM has detected a new Exchange Server database on the protected server, which means that DPM needs to rerun a full backup. This may be run during the daytime and might cause a performance hit on the server. The replica will be marked as inconsistent and the synchronization will fail.

  • The Eseutil utility failed to verify the data on the replica.

For Windows SharePoint Services:

Possible causes for the alert include all of the SQL Server causes, as well as the following:

  • DPM has detected that a new component has been added to the protected Windows SharePoint Services farm since the last backup, so the replica is marked as inconsistent.

  • The WSSCmdLets.exe DCOM component on the protected farm has not been given farm administrator credentials.

For Virtual Server:

Possible causes for the alert include the following:

  • Virtual Machine Additions were uninstalled from the virtual machine.

  • A non-NTFS, iSCSI SAN, or remote volume was attached to the virtual machine.

Resolutions

The error conditions and recommended actions associated with each “Recovery point creation failed” alert are provided in the alert details for the DPM alert.

Follow the recommended action in the alert, and retry the job.

You can access the recovery points on the DPM server to recover previous versions of data.

You can manually create a recovery point in the Protection task area. For information about how to create a recovery point, see How to Create a Recovery Point.

When the next recovery point creation fails, the count of the recovery point creation failure is updated.

For Exchange Server and SQL Server:

To resolve failures related to a failed synchronization, when a full data recovery is not complete, or when an Exchange Server storage group or SQL Server database is deleted, do one of the following:

  • Increase space on the disk.

  • Delete old recovery points.

To resolve failures when the SQL Server service or Exchange service is down, do the following:

  1. Inform the administrator that the service is down, and ask the administrator to manually restart it.

  2. After fixing the issue, click the recommended link in the alert, which reruns the recovery point creation job.

To resolve failures when the disk that contains the SQL Server or Exchange Server database logs is unreachable, do the following:

  1. Inform the administrator that the service is down, and ask the administrator to manually restart it.

  2. After fixing the issue, click the recommended link in the alert, which reruns the synchronization job.

Exchange Server only:

To resolve failures when a new Exchange database is detected or when Eseutil fails to verify data, do one of the following:

  • Run a full backup so that the overall storage group protection is not affected.

  • Reject the full backup for now if the storage group can remain unprotected until the next full backup.

The failure will automatically resolve after the next full backup.

For Windows SharePoint Services:

  • Run a consistency check.

  • Verify that the WSSCmdLets.exe DCOM component on the protected farm has been given farm administrator credentials. (This is one of the prerequisites for protecting a farm.)

    Note
    For this issue, you need to run C:\Program Files\Microsoft Data Protection Manager\DPM\bin\ConfigureSharepoint.exe. When you run it, ConfigureSharepoint.exe asks you for the account and password details and performs the required changes.

Virtual Server only:

  • Make sure Virtual Machine Additions is installed on the virtual machine.

  • Do not attach a non-NTFS, iSCSI SAN, or a remote volume to the virtual machine.

Resolved when: The next recovery point creation succeeds.

See Also