DanPJ
2 Iron

Physical Space On XTremIO 4.01

Jump to solution

Hello,

We have a 20TB XTremIO brick with only 2TB used. I am getting excellent dedup/compression rates and have plenty of room to over subscribe the array. How much can I over subscribe? In other words, How much physical space should I leave on the array? Most arrays require some amount of overhead, usually due to snaps. I am not currently using snapshots but that may change.

Thanks.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
ykaul
1 Copper

Re: Physical Space On XTremIO 4.01

Jump to solution

Because the upper limit is determined not by the physical disk space, but by the in-memory metadata capacity, which is identical in both 10T and 20T models and different in the 40T model.

Y.

4 Replies
Avi3
3 Silver

Re: Physical Space On XTremIO 4.01

Jump to solution

You don’t need to leave any “buffer” space for the ability to use Snapshots on XtremIO. For obvious reasons, we would not recommend running the array at 100% capacity utilization – but you can go to pretty high physical capacity utilization without any issues.

As for the limit on thin provisioning – we mention that in the release notes (search for “Thin Provisioning”). For a 20TB X-Brick, that limit is 130TiB. Thin provisioning of more than 130TiB can be done through the RPQ process.

DanPJ
2 Iron

Re: Physical Space On XTremIO 4.01

Jump to solution

I noticed in the release notes that both the 10TB and 20TB bricks max out at 130TB. The 40TB brick is 360TB. How can the 10TB and 20TB bricks BOTH allow over subscription of the same amount?

0 Kudos
ykaul
1 Copper

Re: Physical Space On XTremIO 4.01

Jump to solution

Because the upper limit is determined not by the physical disk space, but by the in-memory metadata capacity, which is identical in both 10T and 20T models and different in the 40T model.

Y.

DanPJ
2 Iron

Re: Physical Space On XTremIO 4.01

Jump to solution

Thanks.

0 Kudos