Unsolved
This post is more than 5 years old
17 Posts
0
669
how to calculate the required drive count for a ISilon
Hi All,
Business required high performance NAS to replace current Windows File Servers(2003) in five sites and setup Production/DR NAS Solution.
This NAS need solid data storage and full redundancy with no point of failure also easily scale up and seamlessly work in windows environment. (Multi AD integrated)
Current Storage : User Data/ App/Archve = 5 TB ( Server Local Storage)
SQL Data = 2 TB ( Server Local Storage)
Required Storage : 15-20 TB
So how many Nodes and drive configuration required to achieve Production/ DR Solution.
Thanks,
As
cadiletta
106 Posts
0
August 6th, 2014 07:00
Aussupport,
Thank you for your interest in an Isilon solution! Sizing the right solution for the environment is a big task that our field sales teams work hard to perfect. Your account team will gather data about both current workflow and needs as well as growth rates over time. I encourage you to work with your account team to get the best sizing and quote for your organization.
Now, that said, 15-20 TB is easily accomplished with the minimal 3-node cluster of basic hardware. That would give you plenty of headroom to grow, and Isilon has a great scale-out story, and integrates well in a multiple Active Directory environment. However, getting the SQL data stored and secured as well as a solid DR solution add some complexity here. This is where you really want to work with your account team to get a good understanding of your needs, budget, and the variety of EMC solutions available.
Jeffey1
2 Intern
2 Intern
•
2.8K Posts
0
August 11th, 2014 23:00
Hi Aussupport,
Here is the general accepted formula used when sizing:
1) Find total raw TB
2) Multiply that result by (1000^4/1024^4) to get base 2 TB
3) Subtract 1 GB per drive for the OS partitions
4) Subtract 0.0083% of that result to account for the file system format
5) Subtract the protection overhead from that result
As for the protection overhead that you are planning to use, look to the "OneFS Administration Guide" on support.emc.com. Skip to the section: "OneFS data protection" where it will talk about N+M data protection, protection schemes such as N+1, N+2:1 (default), 2x, etc and the associated cost/parity overhead. Also, you will see a very good matrix listing the percent overhead which begins by reminding us: "The parity overhead for each protection level depends on the file size and the number of nodes in the cluster."You can also refer chart below for capacity calculation..
Number of +1 overhead +2:1 overhead +2 overhead +3:1 overhead +3 overhead +4 overhead
nodes
3 nodes 2+1 (33%) 4+2 (33%) 3x 3+3 (50%) 3x 3x
4 nodes 3+1 (25%) 6+2 (25%) 2+2 (50%) 9+3 (25%) 4x 4x
5 nodes 4+1 (20%) 8+2 (20%) 3+2 (40%) 12+3 (20%) 4x 5x
6 nodes 5+1 (17%) 10+2 (17%) 4+2 (34%) 15+3 (17%) 3+3 (50%) 5x
7 nodes 6+1 (14%) 12+2 (14%) 5+2 (28%) 16+3 (15%) 4+3 (43%) 5x
8 nodes 7+1 (12.5%) 14+2 (12.5%) 6+2 (25%) 16+3 (15%) 5+3 (38%) 4+4 (50%)
9 nodes 8+1 (11%) 16+2 (11%) 7+2 (22%) 16+3 (15%) 6+3 (33%) 5+4 (44%)
10 nodes 10+1 (10%) 16+2 (11%) 8+2 (20%) 16+3 (15%) 7+3 (30%) 6+4 (40%)
12 nodes 11+1 (9%) 16+2 (11%) 10+2 (17%) 16+3 (15%) 9+3 (25%) 8+4 (33%)
14 nodes 13+1 (8%) 16+2 (11%) 12+2 (15%) 16+3 (15%) 11+3 (21%) 10+4 (29%)
16 nodes 15+1 (6%) 16+2 (11%) 14+2 (13%) 16+3 (15%) 13+3 (19%) 12+4 (25%)
18 nodes 16+1 (5%) 16+2 (11%) 16+2 (11%) 16+3 (15%) 15+3 (17%) 14+4 (22%)
20 nodes 16+1 (5%) 16+2 (11%) 16+2 (11%) 16+3 (15%) 16+3 (15%) 16+4 (20%)
30 nodes 16+1 (5%) 16+2 (11%) 16+2 (11%) 16+3 (15%) 16+3 (15%) 16+4 (20%)