Hello Adai,
Thanks for your reply.
I have opened case 2004149517 regarding this issue.
Dror, the escalation engineer has replied:
As we saw, we are hitting bug 677951 which causes DSS to provision Volume SnapMirror volumes in a wrong size.
This bug does not yet have a fix, you can read some more about it here - https://communities.netapp.com/message/105168#105168
While we work on a fix in next version, we have tried implementing a workaround to get backups working in your environment.
We have created the VSM volume manually from Data OnTap, and then told Protection Manager to use the volume we created for the backup.
and
So what we have here is a bug in OnCommand 5.1 that is causing OSSV Mirror part to choose wrong size for the destination, which later on fails as the volume was created too small.
What I did to workaround is to create the SnapMirror destination volume manually, with 16tb (space reservation is off so only occupied space will really be allocated).
Then I changed the resource pool config in the mirror node of the backup (on the dataset edit window) to the physical volume that I created.
Then I conform the Dataset so it will create the Volume SnapMirror relationship.
For now the issue has been solved for the customer.
Does your bug # also link to the same problem ?
Thank you,
Jean-Christophe