Solved: Size of VSM destination created by PM - Page 2

MIP_GMT01 · ‎2013-05-29

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?

adaikkap · ‎2013-05-30

Hi Muhammad,

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.

Regards

adai

View solution in original post