Contents of this Article
In System Center 2016 Data Protection Manager, the DPM team announced a new backup storage technology called Modern Backup Storage (MBS). MBS helps to achieve 50% storage savings using ReFS technology, and 3 times faster backup using ReFS block cloning, which uses Allocate-on-write, as opposed to copy-on-write used by Volume Snapshot in DPM 2012 R2. Modern Backup Storage (MBS) helps also achieving much more efficient storage utilization using Workload Aware Storage (WAS). Workload Aware Storage enables you to configure DPM to store backups on a high or low performant volume based on the workloads. DPM 2016 uses by default Modern Backup Storage.
In an earlier blog post, I covered the latest DPM 2016 features including a step by step installation guide, you can read all about it here.
You can install DPM in different ways. Please refer to the below articles where I described in details how to install System Center 2016 Data Protection Manager, you can choose the installation method that suits your needs:
- How to install SCDPM 2016 on Windows Server 2016 and SQL Server 2016
- How to Automate the installation of SCDPM 2016 on Windows Server 2016
- How to Deploy SCDPM 2016 using SCVMM 2016 on Windows Server 2016
Backup Storage Migration
One of the most requested feedback for Microsoft was the ability to move back up data from one volume to another volume. The DPM team is listening to us, and now, with the release of SCDPM 2016 Update Rollup 4, you can move your backup data from one volume to another (i.e. storage upgrade from Low Performant volume to High Performant volume). You can also move your datasources to other volumes when an existing volume is getting full and cannot be extended. I want to be clear here, this feature is only supported from Modern Backup Storage to Modern Backup Storage volumes. In other words, DPM Classic Storage to Modern Backup Storage is not supported, and DPM Classic Storage to DPM Classic Storage is not supported either. DPM Classic Storage is what we had in DPM 2012 R2 and earlier versions.
How to do it…
Make sure you have installed SCDPM 2016 Update Rollup 4 and rebooted the DPM server. Now take the following steps:
- Open System Center 2016 DPM Administrator Console, go to Protection workspace, and then select the desired Protection Group.
- Under the Protection Group, select the workload that you wish to move, Right-Click, and select Move disk storage…
- A new window will open, showing the Current disk storage the datasource is on, and the available volume(s) it can be migrated to. Select the target disk storage that you wish to migrate to, and then click OK.
- While the migration is in progress, you can open another DPM console to continue monitoring the progress for any ongoing jobs.
- Depending on the size of the data, the migrating will be completed in some time.
How it works…
What DPM does while migrating the storage?
Once you start moving the disk backup storage, DPM begins copying (Reading) the data from the source to the target storage (Writing).
After the migration is completed, the backup and the source are deleted, and any new recovery points will hence be created on the target storage. This is a lot like a modification of a protection group, hence you cannot revert any ad-hoc jobs while the migration is in progress. Also when migration completes, any jobs that are running for that particular protection group will be preempted.
You can achieve the same results using PowerShell using the Set-DPMDataSourceDiskAllocation cmdlet. Here is an example of how to do it with PowerShell:
- First, you need to create a modifiable Protection Group for the PG where the datasource is in:
$PG = Get-DPMProtectionGroup $MPG = Get-DPMModifiableProtectionGroup $PG
- Second, get the datasource you wish to migrate, and all the volumes you wish to migrate it to:
$DS = Get-DPMDatasource $MPG $Vol = Get-DPMDiskStorage -Volumes
- Last but not least, modify the disk allocation for the datasource, and specify the target storage. The final command is to save the changes to the Protection Group:
Set-DPMDatasourceDiskAllocation -ProtectionGroup $MPG -Datasource $DS ` -TargetStorage $Vol -MigrateDatasourceDataFromDPM -Verbose Set-ProtectionGroup $MPG -Verbose
What I have also noticed in DPM 2016 UR4 is the backup and UI performance improvement. This is a big one. Thank you to the DPM team for continuous improvement.
For more information about the additional enhancements in UR4, please read the announcement here.
Hope this helps!