The synchronization job for one protection group on my DPM 2019 (with MBS) fails and I get the following two warnings:
The used disk space on the computer running DPM for the replica of Volume XXX has exceeded the threshold value of 90%, or there is not enough disk space to accommodate the changed data. If you do not allocate more disk space, synchronization jobs may fail. (ID 3100)
The SC 2019 DPM AC recommends to Allocate more disk space for replica....
Synchronization jobs for XXX on YYY have failed. The total number of jobs = 1. The last job failed for the following reason: (ID 3115) DPM is out of disk space for the replica. (ID 58 Details: There is not enough space on the disk (0x80070070))
The SC 2019 DPM AC recommends to Modify Disk Allocation ....
Both recommended actions from the warnings always result in one of the following errors:
DPM could not execute a WMI query. The query either returned an error or an empty result. (ID: 33507)
An unexpected internal error occurred in the StorageManager. ID: 40001
Using the Edit-DPMDiskAllocation
cmdlet to increase the replica size:
$pg = Get-DPMProtectionGroup -DpmServerName <DPM_NAME>
$ds = Get-DPMDatasource -ProtectionGroup $pg[0] # display $pg and select the desired PG
Edit-DPMDiskAllocation -Datasource $ds -ReplicaSize ($ds.ReplicaSize + 5TB)
always results in the following error:
Edit-DPMDiskAllocation : DPM could not execute a WMI query. The query either returned an error or an empty result. (ID: 33507)
Retry the operation.
At line:3 char:1
+ Edit-DPMDiskAllocation -Datasource $ds -ReplicaSize ($ds.ReplicaS ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Edit-DPMDiskAllocation], NonFatalWmiException
+ FullyQualifiedErrorId : WMIFailedToExecuteQuery,Microsoft.Internal.EnterpriseStorage.Dls.UI.Cmdlet.ProtectionCmdLets.ModifyDPMDiskAllocation
Using the Set-DPMDatasourceDiskAllocation
cmdlet to increase the replica size:
$pg = Get-DPMProtectionGroup -DpmServerName <DPM_NAME>
$mpg = Get-DPMModifiableProtectionGroup -ProtectionGroup $pg[0] # display $pg and select the desired PG
$ds = Get-DPMDatasource -ProtectionGroup $mpg
Mount-DPMRecoveryPoint -Datasource $ds
Set-DPMDatasourceDiskAllocation -Datasource $ds -ProtectionGroup $mpg -Manual -ReplicaArea ($ds.ReplicaSize + 5TB)
Set-DPMProtectionGroup -ProtectionGroup $mpg
Dismount-DPMRecoveryPoint -Datasource $ds
results in the following error:
Set-DPMProtectionGroup : DPM could not execute a WMI query. The query either returned an error or an empty result. (ID: 33507)
Retry the operation.
At line:6 char:1
+ Set-DPMProtectionGroup -ProtectionGroup $mpg
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-DPMProtectionGroup], DlsException
+ FullyQualifiedErrorId : WMIFailedToExecuteQuery,Microsoft.Internal.EnterpriseStorage.Dls.UI.Cmdlet.ProtectionCmdLets.CommitProtectionGroup
Using another approach to increase the replica size in PowerShell (found in this comment):
$DPM = Connect-DPMServer -DpmServerName <DPM_NAME>
$pg = Get-DPMProtectionGroup -DpmServerName <DPM_NAME>
$ds = Get-DPMDatasource -ProtectionGroup $pg[0] # display $pg and select the desired PG
$DPM.Proxy.ResizeReplica($ds.DatasourceId, ($ds.ReplicaSize + 5TB))
results in this error:
Exception calling "ResizeReplica" with "2" argument(s): "Invoke method on Object <SOME_WMI_STRING> failed with return value SizeNotSupported"
At line:4 char:1
+ $DPM.Proxy.ResizeReplica($ds.DatasourceId, ($ds.ReplicaSize + 5TB ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : NonFatalWmiException
No matter which method I use to try to allocate more replica space, I observe the following:
winmgmt -VerifyRepository
returns WMI Repository is consistent
HKLM:\SYSTEM\CurrentControlSet\Services\TmFilter\Parameters
. Not even the key TmFilter
exists on Windows Server 2019 / SC 2019 DPM. I created it, added the value BypassDPMfilter
(DWORD (32 Bit)) with data 1
, rebooted, but the errors remained1 (reference)1 Actually, the error from the disk space allocation via GUI changed from 1.
(WMI error) to 2.
(StorageManager). The error from disk space allocation via PowerShell remained the same (WMI error).
How can I successfully allocate more replica disk space on MBS?
User contributions licensed under CC BY-SA 3.0