General Data Protection Issues

Backup of data sources fail with agent upgrade error.

The protection agent on some members of the cluster has not been upgraded.

Upgrade the protection agent on all members of the cluster.

DPM is no longer able to communicate with its protected computers.

The DPM computer may have been temporarily disjoined from the Active Directory domain to which it previously belonged. For example, the DPM computer could have been disjoined because of a broken workstation-domain trust relationship. When the DPM computer is restarted, it is rejoined to the domain with the same name but is assigned a new Security Identifier (SID). All servers that are being protected by this DPM computer have an agent registry DCOM security setting that contains the obsolete SID. Therefore, the servers are unable to either launch the DPM protection agent or resume communication with the DPM computer.

To restore communication and resume data protection activities, do the following:

1. Locally uninstall the protection agent from the protected computer.
   
   
2. On the DPM server, in DPM Administrator Console, in the Management task area, on the Agents tab, select the protected computer. In the Actions pane, click Refresh information.
   
   The agent status changes to Error.
   
   
3. In the Details section, click Remove the record of the server from this DPM computer.
   
   

Reinstall the protection agent on the computer. For instructions, in the Operations Guide, see Managing DPM Servers (https://go.microsoft.com/fwlink/?LinkId=91853).

The recovery point time is not consistent with synchronization time.

When a recovery point is created, it reflects the time of the most recent change to the protected volume.

For example, if a recovery point is scheduled to be created at 11:00 A.M. and the most recent change to the protected volume occurred at 8:30 A.M., the recovery point that was created at 11:00 A.M. will display a time stamp of 8:30 A.M.

No action is required.

Auto discovery does not discover changes to shares.

If a share on a computer is protected and the computer also contains an unsupported share, then auto discovery will fail to discover changes to shares on that computer, such as new shares, removed shares, and share remappings.

No “pending members” will be discovered by auto discovery for a computer with a protected share if the computer also contains a share that points to a destination in the following list of unsupported shares:

• FAT volume.
  
  
• CD-ROM drive.
  
  
• USB drive.
  
  
• Mount point located inside another mount point.
  
  
• Special folders: System Volume Information folder, RECYCLER folder.
  
  
• Unsupported reparse point (that is, any reparse point other than a mount point).
  
  
• On a case-sensitive system, a folder that has the same name as another folder inside that folder’s parent, differing only in case (for example, “F:\MarketingDocs” and “F:\marketingdocs”).
  
  
• On a computer containing a share from the list of unsupported shares, we recommend that you protect only volumes and folders for auto discovery to work correctly.
  
  

Your long-term tape backup fails because your full tape backup is not available.

- Or -

Your long-term backup does not leverage the latest tape backup that was most recently created.

If you are using tape for both short-term and long-term protection, DPM creates copies of the latest short-term tape full backup to generate your long-term tape backup.

To resolve this issue, when you create your protection group, we recommend that you schedule your short-term protection full backup to run a day prior to your long-term protection. This enables your long-term tape backup to leverage the short-term tape backup that was most recently created.

If you schedule the long-term tape backup to run prior to the short-term tape backup, the long-term backup will use the short-term full backup of the previous week.

Creating or modifying a protection group fails.

If the number of recovery points exceeds the number that DPM has provisioned, creating or modifying a protection group will fail. In addition, you cannot view the number of recovery points in DPM Administrator Console.

To view the number of existing recovery points, do the following:

From the DPM Management Shell prompt, type $dpm = Connect-DPMServer dpmoffice02
$dpm.CurrentShadowCopyProvision.

Creating a protection group fails when protecting several nodes in a cluster, and the following error is displayed:

"This item cannot be protected because some prerequisite software is missing. Ensure that all prerequisite software is installed and then protect this item."

The software prerequisites may not be present on all nodes in the cluster.

You must install the software prerequisites on all nodes on the cluster that you are protecting. For information about DPM prerequisite software and the servers it protects, see Protected Computer Requirements (https://go.microsoft.com/fwlink/?LinkId=100473).