Do you know how to create a thin provision LUN in SNM2??
In which Storage (Model) do you want to create a Thin LUN..
What storage do you use? (Assuming you have HUS Box)
You need to create a Thin provisioning pool to start with.
Following is the procedure to create a DP Pool -
1. Login to storage
2. Browse through the GROUPS
3. Click on Volumes - The right side window shows 3 tabs viz- 1. volumes 2. RAID Groups 3. DP Pools
4. In the bottom you will see an option called CREATE POOL, click on it
5. In the next window you will find 2 tabs viz Basic and Advanced
6. There will be options provided for creating a DP Pool
>> Enter the DP Pool number (For HUS110 the range is 0-49 and HUS130/150 the range is 0-63)
>> If you have encryption license Enable/Disable this option
>> Enter the DP RAID Group number (For HUS110 the range is 0-49 , HUS130 the range is 0-199 and HUS150 the range is 0-63)
>> Select the DRIVE TYPE/RAID LEVEL/DISK COMBINATION
>> You have an option to select the drives manually (leave the automatic option, let the system decides what drives to use for)
>> After adding all the details - there will be a ADD button in the center of the screen, click on it and click on OK
Note - in the advanced settings tab you can set the threshold and over-subscription limits.
DP Raid group will be created.
Procedure to create a Thin LUN -
4. Goto Volumes tab
5. Click Create VOL
>> In the Basic tab Select DP POOL option in the Model
>> Select the DP Pool number
>> Enter the volume numer (let this be auto)
>> Specify the required capacity
>> Click OK
This will display a confirmation window - where you can assign the created volume to the Host group or you can create more volumes.
I am not sure if that is a correct procedure. I can easily create a pool that I can expand later on, but when I go to create a volume I have no option to thin provision it in SNM2. I can expand it at a later time but does not have the option to assign 10 GB from the 200 GB volume and flag it that when reaches 90% automatically add another 10 GB to it until it gets to 200 GB. Do you know how to do this?
Saeid Yazdan, P. Eng. | Data Protection Consultant
OnX Enterprise Solutions / Momentum Advanced Solutions | 155 Commerce Valley Drive E. | Thornhill, ON L3T 7T2 CANADA
Toll-Free: 800.663.6699 | Local: 416-738-2246 | email@example.com<mailto:firstname.lastname@example.org>
A volume from a DP pool is automatically "thin". When the volume is first presented to a host, it will report 200GB of total capacity even though no actual capacity has been used at that point. As the host writes data to the volume, the array automatically allocates additional capacity (up to 200GB) from the pool to hold the new data. You don't have to micro-manage the array.
But maybe I don’t want all my hosts to consume the storage at the same priority. Thin provisioning is so that you can decide who gets what from the pool. In this case all hosts have the same priority over the storage???
Hi Saeid Yazdan,
I am inclined to disagree with your understanding of thin provisioning as "you can decide who gets what from the pool". Rather, it is so "you get from the pool exactly what you need and only when you need it". It is about improving storage utilization and ease of storage management; there is nothing there about client prioritization. If you like your clients to have different levels of access to storage resources, have them use different storage pools.
Please let us know if this helps clarify what we discussed here and answers your questions.
[Moved from Software to Storage Management]
I agree with Michael Ratner. We do the same in our environment. And we provide different over provisioning percentages for different pools, based on requirement.
I am only comparing the implementation of this design to the original definition of Thin Provisioning as it is implemented by other storage vendors. All other vendors allows the user to set the target LUN size as it is introduced to the host, initial size as it is consumed by the storage, Extend size to which the LUN can grow in increments and finally the amount that can grown beyond the final size.
None of those option exists in this scenario. we simply have a general definition of Thin Provisioning where all LUNS are treated exactly the same by consuming 48 MB chuck size to their final allocated size. I am not sure if I can call this a Thin Provisioning. I might call it one form of specialized Thin Provisioning, but not certainly the usual Thin Provisioning.
Retrieving data ...