So I'm setting up DPM for a remote data center (no, I don't have the option to choose any other products, just in case that comes up). Server is plenty hardy for the job and the DPM install went off without a hitch, as did connecting the box to Azure. However, I'm a little flummoxed by the logic utilized by setting up Protection Groups.
The box containing all the file shares is....the folder equivalent of a bee's hive. Shares are kind of all over the place, no rhyme or reason to where specific folders were placed or the workloads represented by those files. Drive D:'s first folder contains SQL DB backup target location while the second folder contains 9 shares for that country's HR staff.
To wit, I want to create two protection groups (this is an example)
d:\SQL Backup Target
d:\HR Data
But....once I create a PG for #1, I'm excluded from creating a PG for #2 with the message
"Other items on this data source are members of another protection group"
#&@#^$
The only reasoning I can think of is that I might create policies that would cause the DPM Agent to backup different folders on the same volume simultaneously, creating an IO bottleneck.