I have a PM policy "Backup (SV) and then VSM". When I add a volume to the dataset with this policy PM creates a volume for Backup node (of the size of aggregate) and also tries to make a volume for the VSM destination of the same size as aggregate but fails because size of aggr is 53TB and maximum volume size allowed for system (FAS3240) is 50TB. Any idea what can I do to solve this problem?
As kevin said, the solution is to upgrade to OCUM 5.1 or 5.2 as we have made Dynamic Secondary Sizing for Volume SnapMirror as well.
But until you complete all your certification or if you are waiting for a GA Release you can follow the workaround in the known issue that you are hitting. I suggest you open a case and add your case to this bug 670808.
Here is the link to the bug detail that gives the workaround.
Is there a specific reason why this options is disabled ? Ideally the value for this option should be enabled. That way you get the benefits of DSS for SV and QSM destination volumes, instead of creating aggr sized none guaranteed volumes PM will create destination volumes, 1.32x the total size of source volume if used space on source is <60% and 2.2x the used size of source volume if used space on source is >60%.
I guess this is disabled by default as we upgraded from previous version of DFM. If we enable this option now what impact it could have on the existing SV and QSM relationships? After setting this option enable will this only work on the newly created relationships? Does this option work only on SV and QSM not on VSM? What will happen if SV\QSM destination volume become full with dpDynamicSecondarySizing option enabled. Would destination volumes gets increased automatically?
Now it makes sense why it wasn't showing... If we set this now what impact it would have on the existing secondary volumes? After setting this option will all new volumes will be provisioned of maximum of this size and will be thin provisioned? How do you specify value for this option in KB\MB\GB\TB?
This option would be disabled if your server was upgraded from a version prior to DFM 3.8.
Enabling it will only affect newly created volumes, not any existing volumes.
And it will not affect VSM destinations until 5.1, where that support was added - in all previous versions of DFM/UM it only affects SV and QSM secondaries.
In versions prior to 5.1 (or 5.1 and later with DSS disabled), VSM destinations are created to the size of the containing aggregate with no guarantee, then reduced in size and expanded as needed. The main problem with this behavior is the limit of how large a volume can be versus the aggregate size, which is the issue you are running into.
Probably you owe me a BEER............ for all my response.
If we set this now what impact it would have on the existing secondary volumes?
No impact on the existing volumes.
After setting this option will all new volumes will be provisioned of maximum of this size and will be thin provisioned?
If DSS is disabled and this option set, then all new volumes provisioned will be to of the size of this option. By default irrespective of DSS or this option all secondary volumes are thinly provisioned.
How do you specify value for this option in KB\MB\GB\TB?
As it suggests in the option name the value should be set in MB. If you want to set it to 50GB then you would run the following cli
C:\>dfm options set pmAutomaticSecondaryVolMaxSizeMb=51200
Changed auto-provisioned secondary volume max size, in megabytes to 51200.
BTW if you want to reset or turn off this option you would do the following.
C:\>dfm options set pmAutomaticSecondaryVolMaxSizeMb=0
Changed auto-provisioned secondary volume max size, in megabytes to 0.