I have a customer who is trying to add a volume to a dataset that uses QSM for backups, but when he adds it to the dataset, the conformance check indicates that it will create a new volume for this relationship on another aggregate in the dataset instead of putting it in the same volume as the other source volume in the dataset. Here is some config info:
Dataset:
SourceVol1=2GB, 495GB used, 0GB snapreserve
Resource pool has 7 aggregates
SourceVol1's aggregate has 3.6TB of space available
SourceVol2, the volume to be added, is 2GB, 450GB used, 0GB snapreserve
When I try to add SourceVol2 it wants to provision a new 2.64TB volume on another aggregate in the resource pool.
Why is it doing this? I want it to put it into the same volume as SourceVol1's backup. Dynamic secondary resize is enabled. dpMaxFanInRatio is 100.
I have enough space in that aggregate. And yes, I'm adding it as a qtree, /vol/SourceVol2/-, not a volume.
So, we manually increased the destination volume of SourceVol1 and it behaves like we want, putting the backup into the same volume as SourceVol1.
It looks as if dpDynamicSecondarySizing is not working for some reason.
