Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.5 Administrator Guide > Configure your arrays > EMC XtremIO and Pure Storage capacity savings technologies

EMC XtremIO and Pure Storage capacity savings technologies

Table of contents
No headers
Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 15 Votes: 0 Revisions: 1

EMC XtremIO and Pure Storage arrays use capacity-savings technologies including:

  • De-duplication - removing redundant data.
  • Compression - making the object smaller using standard compression algorithms.
  • Thin provisioning - using virtualization to give the appearance of having more physical resources than are actually available.

As an example, let us look at the LUN creation process for these arrays. Suppose we were to provision a logical object (LUN) on an EMC XtremIO or Pure Storage array, and wanted to make it 100 GB.

After creating the LUN, we can inspect the LUN Details view to see that the Total Size property shows 100 GB, the size of the LUN required.

 We can investigate the Consumed Capacity value. Immediately after the LUN is created this value will be a very small fraction of the 100 GB. It will, of course, grow as the user adds data to the LUN. The value displayed should be exactly the net amount of data which has been sent to the LUN. Since this is a logical value, as seen by the host computer operating system, it cannot be greater than the Total Size.

If we then look at the Storage Pool Details view we should see the Total Subscribed Capacity has increased by 100 GB.

Depending on the array total capacity and the Total Subscribed capacity, the Oversubscribed Capacity can stay at 0, or grow to a value between 0 and 100 GB. This value shows how much the sum of the LUNs Total Size values for the pool is bigger than the Total Usable Capacity.

Over the lifetime of the LUN, Total Capacity of the LUN and its share in the Total Subscribed Capacity for the array will not change, unless the storage administrator expands or shrinks the LUN.

In most cases the Consumed Capacity of the LUN will not decrease, with the exception for LUNs owned by certain operating systems. For example, if VMware is used, VAAI is able to communicate to the array a list of unused blocks of data - these blocks will be removed, decreasing the Consumed Capacity.

The influence of adding the 100 GB LUN on the Usable Capacity for the array cannot be predicted with 100% certainty. Because of global de-duplication, adding the data can leave the free usable capacity unchanged in extreme situations. Therefore, any prediction for run-out time is statistically valid at the whole array level.

Last modified
08:55, 14 Mar 2017