Hi guys, posting to get some input from some DPM experts here with regards to my rebuild and migration plan
Our current set up is as follows:
- Primary, Physical host, DAS, DPM 2016, Windows Server 2012R2
- Secondary, Physical host, DAS, DPM 2016, Windows Server 2012R2
We are looking to replace this set up with a new physical host running DPM 2019 on Windows Server 2019 as our primary and utilise Azure Backup getting rid of the secondary.
Question: As it is not possible to bring over the existing storage pool to the new host, is there any benefit in retaining and upgrading the existing DPM database as opposed to starting with a fresh new one? I am not worried about having to reconfigure protection groups.
The plan is to build the new primary and have it ready. Then migrate protection of selected protected servers over to the new DPM and into Azure by way of the following steps:
- Stop protection in existing DPM (keeping replica on disk)
- SetDPMServer.exe -dpmservername $newdpmserver on protected server
- Attach-ProductionServer.ps1 on new DPM console
- Upgrade agent on protected server from new DPM console
- Wait for replica rebuild on new storage pool
- Wait for full sync to Azure Backup
Our internet bandwidth is limited to 500mbps (realistically can only probably use 200) and it would take days to seed our 20TB up to Azure. My thought process is that keeping both environments live and staggering the migration will minimise the risk of not having a off site back up.
Keen to get any input - thanks.
