1. DSS Disk Storage Update Disk Space Issues: Need additional disk storage to put data on-line Need extra disk space to prepare and operate on large data files before saving them into our archive Special projects require extra disk storage to capture the data /huron/ftp keeps getting full Good experiences with Nexsans ATABeast Databases Proposed Solutions: Add a SATABeast on CISLs SAN for on-line data storage Add a SATABoy (4TB) on CISLs SAN for DSS work storage Reorganize file systems on huron, bison once the additional storage become available Chi-Fan Shih, Nov 2006

2. High-speed Shared File System – Fall 2006 CDP (dataportal) Sun V880 DSS (huron) Sun V880 Mc Data Switch Meta Data Servers Storage device Storage device Internet DSS (bison) Sun V880 TIGGE (ultrazone) Sun V890 TERAGRID (datagrid) Sun V890 Teragrid 2007 Storage device Storage device From Rich Loft FY07 SAN Plans, Oct 3, 2006 CISLs SAN

3. SAN Load Test Performance Results From Rich Loft FY07 SAN Plans, Oct 3, 2006 Based on (200GB data + 1.8TB read) per day

4. SAN Filesystem to Physical Hardware Mapping Plan AB1 12 TB AB2 12 TB SB1 16 TB SB2 16 TB /dsstmp:12 TB/cdp1: 7.5 TB /gridbgc: 4.5 TB /tigge: 6 TB /esg-cdp: 10 TB SB3 16 TB SB4 16 TB /narccap: 16 TB/dsswork: 6 TB /TBD: 10 TB 1, Purchase two SATABeasts… 5.1 TB of dss work files 5.1 TB of dss work files 2. Transfer dss work files to SB4… /dsszone: 28 TB 3. Merge File Systems From Rich Loft FY07 SAN Plans, Oct 3, 2006 CISLs New SAN (FY07)

5. DSS Computers & Storages Huron - Local disks, T3 raid, ATABoy2, Beasts Bison - Local disks, Beasts Skunk - Local disks, A1000, tape drives (SDLT220, 8mm, DLT8000, 4mm, SDLT320) Ultra - TIGGE, SB2 Beast Haystack - Local disks, WS raid, LTO2 tape drive DogFishLake - SATA, DVD/CD RW LonePine - IDE, DVD/CD RW Beasts - part of CISLs SAN AB1 (ATABeast, 12TB usable space dsszone 12TB, ready) SB1 (SATABeast, 16TB usable space, dsszone 16TB, ready) SB2 (SATABeast, 16TB usable space, TIGGE 6TB, shared, ready) SB4 (SATABeast, 16TB usable space, dsswork 6TB, shared, to come) Chi-Fan Shih, Nov 2006

6. Huron Current Configuration: Local Disks - /huron/data (dss, 142GB) /huron/dss (dss, 6GB) /huron/http (dss, 4GB) /huron/scratch (root) /huron/tmp (dss, 142GB) /huron/ws (root) /huron/n (dattore) /huron/stats (dss, ) /huron/user (dss, 36GB) T3 Raid - /huron/ftp (1.4TB) ATABoy2 - /huron/data01 (2.9TB) Beasts - (R,W) /datazone/dsszone: 28TB /datazone/dsswork: 6TB New Configuration : Local Disks - /huron/data (dss, 142GB) /huron/dss (dss, ___GB) /huron/http (dss, ___GB) /huron/scratch (root) /huron/tmp (dss, ___GB) /huron/ws (root) /huron/n (dattore, ___GB) /huron/stats (dss, ___GB) /huron/user (dss, ___GB) T3 Raid - /huron/ftp (1.4TB) ATABoy2 - /huron/ftp/download (1TB?) /huron/DSSmeta (1TB?) /huron/ftp/rossby (0.9TB?) Beasts - no change What to keep on /huron? Where to put databases?

7. Example New Configuration of Huron Filesystems Local Disks - ____GB /huron/dss (dss, ___GB) /huron/http (dss, ___GB) /huron/scratch (root) /huron/ws (root) /huron/n (dattore, ___GB) /huron/stats (dss, ___GB) Metadata XMLdb? RDADB? T3 Raid - 1.4TB /huron/ftp Metadata XML DB? RDADB? ATABoy2 - 2.9TB /huron/ftp/download /huron/ftp/rossby Static metadata Metadata XMLdb? RDADB? Beasts - SB1+AB1 - /dsszone ERA40, NARR, R1 R2, FNL, DatasetDB (upper air) SB4 - /dsswork Move/Release /huron/{tmp,data,user} /bison/{tmp,data,user}

8. Bison Locsl Disks /bison/tmp (210GB) /bison/data (105GB) /bison/user (35GB) Hurons Filesystems /huron/{data, data01, dss, ftp, http, tmp, user} Beasts - /datazone/dsszone (R,W) /datazone/dsswork (R,W) Locsl Disks /bison/tmp (?GB) /bison/data (? GB) /bison/user (? GB) Hurons Filesystems /huron/{dss, ftp, http, user} Beasts - same

9. Skunk Local Disks – A1000 - /skunk/data (400GB) Hurons Filesystems - /huron/{data, data01, dss, ftp, http, tmp, user} Beasts - /datazone/dsszone (R only) /datazone/dsswork (R,W) Tape Drives - SDLT220 DLT8000 8mm 4mm DAT SDLT320 (JRA)

10. Haystack Local Disks - WS raid - /haystack/data (1.5TB) Hurons Filesystems - /huron/{data, data01, dss, ftp, http, tmp, user} Beasts - /datazone/dsszone (Read only) /dataozne/dsswork (R,W) Tape Drive - LTO2

11. DSS SAN Data Storage & Future Projects Upper Air - ERA40 - subset, feedback, netCDF NARR - molts, feedback, forecasts NASA Reanalysis - SB2 Beast - /datazone/tigge, 6TB SB1+AB1 Beasts - /datazone/dsszone, 28TB e4moda.an.sfc.t85.t2m.1957-2002.nc ERA40 davestep dss feedback icoads restricted tigge ua ds090.0 ds366.0 ds367.0 ds476.0 ds607.0 ds608.0 ds609.2 FNL, ADP obs, R2, Eta/NAM molts & forecasts, profiler, …… JRA - (restricted) DSS Databases - Metadata XML DB RDADB (internal) DatasetDB (internal, external) SB4 Beast - /datazone/dsswork, 6TB

12. Summary /datazone/dsswork Consolidation of DSS work spaces into one area Sufficient for the next few years Indpendent of DSS computer changes Keep it clean (scrubber?) Reallocate ftp/{download,rossby} to ATABoy2 Plenty disk space for large download Match performace with ftp speed Separated from huron local disks Do we need a scrubber? Increase of local disk space on huron for DSS services Moving static, public data to /datazone/dsszone

13. DSS SAN File Protection Questions Protection is needed in the event of: A SNFS administrator making a mistake, including making changes whose consequences are not fully understood, not deterministic, etc. A double-disk failure where two drives fail within 12 hours of one another, rendering RAID5 useless. DSG has no plan and no tool to backup the files on SAN. 1. If there is no way to recover the dsszone files within SAN (i.e. RAID5 or SNFS), could those files be brought back from MSS or other storage? 2. Since there is no interface to get the details of files stored on dsszone from metadata server. Should DSS or DSG keep the detailed file information (under dsszone) somewhere? Or is such information already stored in Hua's RDADB? Could this method be expanded to other SAN directories/files.

14. Thoughts on DSS SAN File Protection Solution Eds rls program - list basic file info, file status error, not useful to us. DSSs own: keep file info (ds#, proj name, size, date), checksum (like md5), backup/restore option in a DB. Those elements of individual files may be stored in RDADB, or in a separate DB just for tracking files on dsszone. In case of disasters, files may be verified against the file info in the DB, or be restored using the backup/restore option recorded in DB. * The file verification is done without involving individual specialist. * Restoring files may be either done with commands in DB or the specialist will be contacted. More details to come including moving files, building links, collecting file integrity info automatically using dsarch or scripts TBD.