1618Tb SDDS storage BE-CO-IN

Proposal Upgrade operational LHC_DATA to 1.1 Tbytes with the same operational level : – New faster technology (SAS disks instead of SATA) – RAID-1 New service of ~16Tb of READ-ONLY data containing ALL SDDS data : – Copied daily from LHC_DATA – No backup (but RAID6 to secure the data) – Structured per year/month/day (TBD) 2nd June 20092LHC Beam Commissioning WG - P.Charrue

Proposal 2nd June 20093LHC Beam Commissioning WG - P.Charrue

Status Both operational and read-only fileservers are now available On the operational side, nothing changes, except CASTOR transfer which is now done from the new fileserver NFS99 NFS99 has been loaded with ALL data from 2006, 2007, 2008 and Tb (out of 18) are currently used. See \\cs-ccr-nfs99\data or /nfs/cs-ccr-nfs99/data or \\cs-ccr-samba1\slops\data\LHC_DATA\OP_DATA or \\cs-ccr-samba1\slops\data\SPS_DATA\OP_DATA 2nd June 20094LHC Beam Commissioning WG - P.Charrue

Data flows 1.Operational applications write SDDS files on cs-ccr-nfs4 2.Every night after 0h00 newly created files are copied from cs-ccr-nfs4 to cs-ccr-nfs99 3.Once per month, new files are compressed on cs-ccr-nfs99 and sent to CASTOR 4.When needed, old files are deleted from cs- ccr-nfs4 to liberate some free space 2nd June 20095LHC Beam Commissioning WG - P.Charrue

Data Security cs-ccr-nfs4 is RAID-1: all files are copied 2 times on 2 different disks cs-ccr-nfs99 is RAID-6 and exported READ-ONLY. The server can cope with one disk failure And finally all files are stored on CASTOR tapes In case of major major catastrophe : – If all cs-ccr-nfs4 disks are corrupted, we can recover from the files copied on nfs99 (but we may lose the production of the current day) – If all cs-ccr-nfs99 disks are corrupted, we can recover from CASTOR tapes, but this will need about 3 weeks 2nd June 20096LHC Beam Commissioning WG - P.Charrue