Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. This volume creation or grow was not allowed because the occupancy of the LDM database would have been %CurrentLdmOccupancy;%% after this operation which is above the DPM limit of %LdmErrorThreshold;%%.
During recovery, backup data from the {0} needs to be temporarily downloaded to a local staging area before it is recovered ...
Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The current occupancy of ...
Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The LDM database is currently ...
Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The LDM database will be ...
Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. This volume creation or ...
Either because this replica was restored from a backup that was not created using the DpmBackup tool, or because the GUID ...
Either run a synchronization, or wait for the next scheduled synchronization to occur. If the problem persists, check your ...
Either stop protecting this data source from this DPM server or take over ownership of the data source for this DPM server. ...
Either stop the DPM protection agent service on %ServerName; and make sure that the QoS Packet Scheduler is enabled, or disable ...