2013-05-29 08:07 AM
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?
Solved! SEE THE SOLUTION
2013-05-29 10:06 AM
Upgrade to UM 5.1 or 5.2RC1 where it uses DSS (Dynamic Secondary Sizing) for VSM volumes.
This will prevent it from attempting to create it to the size of the containing aggregate.
2013-05-29 11:03 PM
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.
2013-05-30 02:08 AM
Thank you Kevin and Adi for replies. The workaround talks about setting the dfm option pmAutomaticSecondaryVolMaxSizeMb but I don't see this option. Am I missing something?
C:\>dfm option list pmAutomaticSecondaryVolMaxSizeMb
Error: There is no pmAutomaticSecondaryVolMaxSizeMb option.
2013-05-30 02:22 AM
Also I see this option. Any idea would this option be useful in this situation?
C:\>dfm option list dpDynamicSecondarySizing
2013-05-30 03:27 AM
The options is a hidden one so until you set this option you cant list it.
PS: Setting this option will prevent PM from creating a volume greater than the value of this options. Also this is global option and applies to all.
2013-05-30 03:31 AM
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%.
2013-05-30 03:52 AM
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?
Sorry for bombarding with so many questions
2013-05-30 04:01 AM
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?