DPM 2022 dpm 2022 resize replica disk size

Hi,

Is below article may help some for our situation?

Modify Replica Size with PowerShell

Regards,

Alex

Hi Alex_Nick,

Thank you for posting in the Microsoft Community Forums.

1. Evaluate and adjust DPM storage

First, you need to evaluate the DPM's storage configuration to ensure that there is enough space to accommodate the increased backup data. If there is insufficient storage space, you may want to consider several approaches:

Expanding existing storage: If the DPM is using physical or virtual disks and the storage pool in which these disks reside has sufficient capacity, you can try to expand the size of these disks. This usually involves using the DPM's management interface or PowerShell scripts to resize disks and partitions.

Adding new storage: If the existing storage is not scalable, you may need to add new physical or virtual disks to the DPM's storage pool. This can be done through the DPM's management interface or PowerShell commands.

2. Adjusting Protection Group Settings

In DPM, protection groups define which data sources need to be backed up as well as the storage location and policy for backups. If you increase the disk size of a VM, you may need to adjust the protection group settings to reflect these changes:

To modify a protection group: In the DPM Administrator Console, locate the relevant protection group and check its storage allocation. If the allocated space is insufficient to accommodate the new backup data, you can modify the protection group's settings to increase the disk space allocated to it.

Reallocate disk space: If there is excess unallocated space in the DPM's storage pool, you can consider reallocating this space to protection groups that need more space.

3. Perform consistency checks

After adjusting the storage and protection group settings, you should perform a consistency check to ensure the integrity and consistency of the backup data:

Manually trigger a consistency check: In the DPM Administrator Console, select the relevant protection group and manually trigger a consistency check. This will allow DPM to verify the consistency between the protected data source and its backup copy.

Schedule periodic consistency checks: To prevent similar issues in the future, you may consider scheduling periodic consistency checks in DPM. This can be done through the DPM's management interface and can be configured to meet your specific needs.

4. Monitoring and Troubleshooting

After performing the above steps, you should closely monitor the DPM's backup operations and storage usage to ensure that everything is in order. If you are still experiencing problems, you can review the DPM's log files for more information and troubleshoot as needed.

Best regards

Neuvi

Hi @Alex_Nick , Thank you for contacting us on Microsoft Q&A platform. Happy to help!

Ideally, the ResizeReplica.ps1 script increase the replica size on DPM server but as per you commend it seems it is not working and the size of the replica not increasing.

Sometime, the disk replica VDHX gets corrupted and does not allow you to increase the size. In those conditioned there is a workaround which you can perform on DPM server.

• Open SSMS and run below mentioned command to get the replica path for the data source. Just replace the VM name with the VM you are facing the issue.

select ag.ServerName, ds.DataSourceName,rp.StorageId,sv.Path as

Volume,sv.Label as "Volume label",sv.AccessPath, lr.PhysicalReplicaId as "ReplicaID-SubFolder" --

,lr.DataSourceId

from tbl_IM_DataSource as ds

join tbl_PRM_LogicalReplica as lr

on ds.DataSourceId=lr.DataSourceId

join tbl_AM_Server as ag

on ds.ServerId=ag.ServerId

join tbl_PRM_ReplicaVolume as rp

on lr.PhysicalReplicaId=rp.ReplicaId

join tbl_STM_Volume as sv

on rp.StorageId = sv.StorageId

and ds.DataSourceName like '%VM-NAME%' -- uncomment to filter on VM-NAME

order by ag.NetbiosName

• From the above query you will get the replicaID-SUBFOLDER which will be a quid for example cc7fb2fd-1c45-47ec-ab4d-27ef904594dd.
• The you need to download PSEXEC tool on DPM server and open a command prompt using the system permission.
• Then you need point it to DPM Storage Drive and CD to the Replica VHDX path which will be like DriveLetter\FQDN of DPM Server Name\replicaID-SUBFOLDER\replicaID-SUBFOLDER. For example E:\DPM.contoso.lab\cc7fb2fd-1c45-47ec-ab4d-27ef904594dd\cc7fb2fd-1c45-47ec-ab4d-27ef904594dd.
• Once you CD to the path you will see a Disk0.vhdx, you need to rename it to Disk0_old.vhdx.
• Close the command Prompt, open DPM console on Refresh the volume in Management tab.
• Go the protection tab and you will see volume missing for that data source on DPM console
• Open DPM PowerShell and run DPMsync -reallocatereplica. This command will create a new VHDX on the same path.
• Trigger the Consistency Check job(which would be an IR as we have deleted the old replica). This way the backup should start working for you without compromising your old Recovery Points on DPM server.

Please also let me know if the VM size is not more than 16 TB as I might have to give you different steps to perform the resize as DPM allocate the VHDX with 4K cluster size which could increase the size to 16 TB only.