An error occurred while saving the commentMartinB commented
I was interested in Azure Backup, but I wanted to be able to do host level Hyper-V VM backups, and I wanted to manage local disk backups in the same place - so I started doing a lot of research into DPM. I found this feedback page, and the link AlbertoL posted at the bottom of this thread. I ended up very disappointed.
I did note Microsoft's recommendation in their DPM documentation to use tiered storage with a small SSD element. I do understand the advantages, and I also read the Azure Team comment on 1st September chiming in with that just below.
However, a lot of people are talking about ReFS performance which can be good after storage is freshly configured, but then deteriorates over ~3 months, and has to be reformatted.
For me to trust them, and to invest further time in testing/research + potentially storage hardware, I need Microsoft to explain clearly how the use of e.g. 4% SSD storage would ACTUALLY PREVENT DEGREDATION OVER TIME specifically, as opposed to provide a general performance uplift. I'm not yet sure about that.
More detail on precisely how to avoid ReFS problems, including various storage configuration examples would be welcome. This can be complicated - when you include virtualisation (say Hyper-V), and you take the potential use of storage pools, JBOD, RAID, potential pass through etc etc - there are quite a few ways to skin the cat as you take the physical disks up through the stack from host disk controller, Host OS, to Guest DPM server OS, and I'm not quite clear precisely what ReFS needs the admin to AVOID configuring - if indeed avoiding anything particular will definitely help.