Contents
All sizes are in Tera Bytes (2^40 Bytes) unless otherwise specified.
SATA based. This meant for storing data which we primarily need in case systems die etc.
Current | Future | Description |
---|---|---|
0.5 | 2.0 | Yahoo filer mirror |
1.0 | 2.0 | pointyhat archive logs etc |
3.0 | 6.0 | full system images |
4.0 | 10.0 | Total |
SAS based. This is storage intended to be actively used, not just written to for backup purposes.
Current | Future | Description |
---|---|---|
1.5 | 3.0 | FTP - master and archive |
0.5 | 1.0 | NYI /home |
0.5 | 2.0 | NYI /scratch |
2.5 | 6.0 | Total |
NetApp fiber shelf is 14 drives. NetApp SAS shelf is 24 drives. 2 TB SATA drives only supported in SAS shelf.
3 disks are needed for root as we need RAID-DP, as per NetApp's own recommendation (RAID-DP allows upgrade of drive firmware if needed without disrupting the running system).
SAS and SATA disks need to be separated, both in different RAID sets / aggregates and in separate disk shelves. We assume RAID-DP for everything, so we have min. 2 parity disks per RAID set. We assume 2 hot-spares to allow for higher resiliency and for non-disruptive upgrade of disk firmware.
This mean the following "overhead" in disks which can't be used for data:
The following is based on the information from ONTAP Available disk capacity by disk size with the 10% mentioned space deduced in "Available storage".
GB | Available blocks | "Real" available storage [1] |
---|---|---|
300 | 557,056,000 | 239 GiB |
450 | 856,064,000 | 367 GiB |
600 | 1,146,880,000 | 492 GiB |
1000 | 1,735,794,176 | 744 GiB |
2000 | 3,472,315,904 | 1490 GiB |
[1] | Sample calculation for 2TB disk: (3472315904*512*0.9)/1024/1024/1024 |
GB | Count | Available storage |
---|---|---|
600 | 13 | 6.24TB |
450 | 17 [2] | 6.09TB |
600 | 17 [2] | 8.16TB |
1000 | 14 | 10.17TB |
1000 | 18 [3] | 13.07TB |
2000 | 8 | 11.64TB |
2000 | 10 | 14.55TB |
2000 | 18 [3] | 26.19TB |
[2] | (1, 2) 17 = 24 - 2 parity - 2 hot-spare - 3 root vol |
[3] | (1, 2) 18 = 24 - 4 parity (2 RAID groups) - 2 hot-spare |
Hello,
We are trying to set up our new New York Internet (NYI) site to have a full mirror of all important data and all the main systems which run the FreeBSD project. The plan is also to have enough storage etc. to be able to run as the primary site for the FreeBSD project in case the current primary site at Yahoo! fails.
Initially I should say I'm far from an expert on NetApp products - I'm just an enthusiastic user :-), so I very much value input on best configuration etc. As don't know what the relative prices are between different NetApp components etc. my main guideline for which components to suggest has been to take the "smallest" possible system, which is still future proof as possible. To better be able to find out the right solution (hardware and software) I also tried to describe in part what we plan to use the system for.
I do not know if there is a difference in the software between the different systems (I don't think so), but if there is we would prefer systems which are based FreeBSD. This is certainly not a requirement, but if possible we would like to say that the entire setup runs entirely on FreeBSD :-).
After trying to estimate storage requirements for the new FreeBSD.org NYI site we found out that we "need" something along the lines of this (taking future use into account):
10 TB "slow" storage (IE, SATA) for backup / replication target. 6 TB fast storage (IE, SAS) for storage "online" data, such as FreeBSD FTP site.
The slow storage will, among other things, be used as a replication of the NetApp FAS 3050 (with 4TB of storage) we have located at Yahoo!. Some of the fast storage will be connected to a public facing FTP server, which of course should not have access to the backup data, so we will probably be looking at using vfiler to separate data access.
For replication from our Yahoo! filer to the new NYI filer I have been mainly looking at using SnapMirror, but perhaps SnapVault would be better - I'm not really sure. We don't need to have live replication from Yahoo! to NYI, but of course the smaller the delay the better. We also have a number of systems with local storage (IE, important data is not on a filer etc) which needs to be backed up to NYI. I was mainly planning on using a simple rsync based system where a server at NYI NFS mounts the new filer, and we then snapshot this volume. Perhaps Open Systems SnapVault might be better, but among other things I do not know if the client software runs on FreeBSD.
I have been trying to look at different configurations which would accommodate this, and be as flexible as possible for future expansion. To find out how much available space we would get for each drive I used the "Available disk capacity by disk size" from "Data ONTAP 8.0 7-Mode Storage Management Guide" and subtracted 10% extra for ONTAP reserve based on the same documentation.
This could e.g. by done by 20 600GB SAS drives (3 root, 2 hot-spare, 2 RAID-DP parity, 13 data). For the SATA part this could be handled by 12 2TB drives (2 hot-spare, 2 RAID-DP parity, 8 data).
I have mainly been looking mainly at FAS 2040 and FAS 3140 due to their support for ONTAP 8 and for "larger" deduplication volumes. In the end I think the one which fits best is FAS 3140 as it is more flexible with regard to future expansion.
So, the main configuration I came up with was the following:
For SAS drives I filled the shelf as it was mostly full, and for SATA I added 2 extra drives as they give us some extra margin to run on, and I don't think it makes much difference with regard to total cost.
For the system we would also like the following licenses:
-- Simon L. Nielsen FreeBSD.org admins team
Does not include dumpster. All sizes in Giga Bytes.
Host | Capacity | Used |
---|---|---|
builder.freebsd.org | 258 | 25 |
cerberus.freebsd.org | 30 | 1 |
foundation.freebsd.org | 34 | 7 |
freefall.freebsd.org | 127 | 68 |
ftp-master.freebsd.org | 1074 | 742 |
hub.freebsd.org | 528 | 116 |
ipv6gw.freebsd.org | 30 | 5 |
kerberos.freebsd.org | 30 | 1 |
mx1.freebsd.org | 124 | 5 |
mx2.freebsd.org | 28 | 11 |
ncvsup.freebsd.org | 30 | 20 |
netboot.freebsd.org | 130 | 12 |
ns0.freebsd.org | 30 | 4 |
ns1.freebsd.org | 30 | 6 |
ns2.freebsd.org | 30 | 4 |
pointyhat.freebsd.org | 1107 | 889 |
magd.freebsd.org | 387 | 45 |
ref6-amd64.freebsd.org | 124 | 48 |
ref6-i386.freebsd.org | 124 | 14 |
ref7-amd64.freebsd.org | 124 | 97 |
ref7-i386.freebsd.org | 124 | 37 |
ref8-amd64.freebsd.org | 387 | 95 |
ref8-i386.freebsd.org | 124 | 62 |
repoman.freebsd.org | 252 | 188 |
skunkworks.freebsd.org | 536 | 245 |
sky.freebsd.org | 127 | 87 |
spit.freebsd.org | 63 | 22 |
svn.freebsd.org | 511 | 83 |
torrents.freebsd.org | 525 | 197 |
www.freebsd.org | 61 | 33 |
zoo.freebsd.org | 1211 | 546 |
Total | 8319 | 3731 |