Make sure that volume %VolumeName; can be accessed, and then click the recommended action link below. If a new volume %VolumeName; ...

Make sure that volume %VolumeName; can be accessed, and then click the recommended action link below.
If a new volume %VolumeName; was created to replace a previously protected volume with the same name, and you want to protect the new volume, you must remove the original volume from its protection group, and then add the new volume to the protection group. You can retain the replica for future recoveries.
If you no longer want to protect any data sources on the computer, you can uninstall the protection agent from the computer. If the volume has been permanently removed or deleted, remove the volume from its protection group (optionally choosing to retain the replica for future recoveries) and inactivate the alert by clicking "Inactive alert" Otherwise, click the recommended action link below.

Make sure that the user name and password you have provided has administrator privileges on the target computer or 2) DpmDRTrustedMachines ... Make sure that the user name and password you have provided has administrator privileges on the target computer or 2) DpmDRTrustedMachines ... Make sure that the user name and password you have provided has administrator privileges on the target computer or 2) DpmDRTrustedMachines ... Make sure that the Volume Shadow Copy service is enabled on the DPM server. 2) Check recent records from the VolSnap source ... Make sure that volume %VolumeName; can be accessed, and then click the recommended action link below. If a new volume %VolumeName; ... Make sure that volume %VolumeName; can be accessed, and then click the recommended action link below. If a new volume %VolumeName; ... Make sure that volume %VolumeName; can be accessed, and then click the recommended action link below. If a new volume %VolumeName; ... Make sure that you have specified a valid SQL server instance associated with DPM and you are logged on as a user with administrator ... Make sure that: 1) You have administrator access to %MachineName;. 2) Check the computer name provided and make sure the ...